Data · Remote MCP server
LocalPro - Verified US Local Service Provider Data
Verified US local service providers across 10 home-services trades. Owned data, no API key.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.LocalProDev/local-services- Version
- 3.1.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-26
- Updated
- 2026-09-26
- Publisher
- LocalProDev (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/LocalProDev) · how
- Repository
- github.com/LocalProDev/mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.localpro.dev/mcp | X-API-Key (secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- LocalPro 3.1.0 · protocol 2025-06-18
- Tools discovered
- 5:
list_niches,list_cities,list_service_types,search_providers,get_provider - Checked on
- 2026-10-05
How to connect LocalPro - Verified US Local Service Provider Data
LocalPro - Verified US Local Service Provider Data is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.localpro.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| LoadbayCatalog of 370+ open-source AI-agent harnesses. Search, list your own, earn USDC tips via x402. | Remote · HTTPLive check: ✓ handshake |
| Lobbywatch MCPLobbywatch.ch transparency data on parliamentarians, interests, access badges. | Local · stdio |
| Loc MCPSearch the Library of Congress collections. No key required. | Local · stdio |
| Localgym MCP ServerRead-only MCP server for UK gym search using the LocalGym Agent API. | Local · stdio |
| localseodata MCP-SERVER42 local SEO tools for AI assistants. SERP tracking, reviews, keywords, audits, and more. | Local · HTTP |
| LocusPay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits. | Remote · HTTPLive check: sign-in required |
| Lodd MCP ServerHeadless web analytics for AI agents. 42 MCP tools for traffic, events, funnels. | Local · stdio |
| Loggly MCPRead-only Loggly search and analytics with aggregation-first traffic tools and IP intelligence. | Local · stdio |