LocalPro — Verified US Local Service Provider Data vs Vivid MCP
LocalPro — Verified US Local Service Provider Data is an MCP server published by LocalProDev. Marketplaces we read that list it: 1 (Official MCP Registry). Vivid MCP is an MCP server published by vivid-money. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  LocalPro — Verified US Local Service Provider Data |  Vivid MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 3.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | LocalPro — Verified US Local Service Provider Data | Vivid MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.localpro.dev/mcp) | Remote server (api.prime.vivid.money/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/localprodev/mcp-server | github.com/vivid-money/vivid-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded less than an hour ago | Answered with HTTP 400 (39 h ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
LocalPro — Verified US Local Service Provider Data
Verified US local service providers across 10 home-services trades. Owned data, no API key.
Vivid MCP
Open a Vivid Business account from your AI chat via MCP.
How to run each
LocalPro — Verified US Local Service Provider Data As a remote MCP server
claude mcp add --transport http local-services https://mcp.localpro.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Vivid MCP As a remote MCP server
claude mcp add --transport http vivid-mcp https://api.prime.vivid.money/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of LocalPro — Verified US Local Service Provider Data responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: LocalPro — Verified US Local Service Provider Data · What it can do: Vivid MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.