Remote MCP · Endpoint

LocalPro — Verified US Local Service Provider Data MCP server

No. LocalPro — Verified US Local Service Provider Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.localpro.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.LocalProDev/local-services
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.39 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verified US local service providers across 10 home-services trades. Owned data, no API key.
Listing
From the official MCP registry (active).
Recent checks of LocalPro — Verified US Local Service Provider Data
CheckedResultHandshake
1 hour agoHandshake completed3.39 s
2 days agoHandshake completed222 ms
4 days agoHandshake completed226 ms
5 days agoHandshake completed209 ms
7 days agoHandshake completed163 ms
8 days agoHandshake completed429 ms
9 days agoHandshake completed172 ms
12 days agoHandshake completed231 ms
13 days agoHandshake completed161 ms
15 days agoHandshake completed134 ms
17 days agoHandshake completed213 ms
18 days agoHandshake completed125 ms
19 days agoHandshake completed194 ms
20 days agoHandshake completed115 ms
20 days agoHandshake completed159 ms
21 days agoHandshake completed126 ms
23 days agoHandshake completed139 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with LocalPro — Verified US Local Service Provider Data and makes no claim about it beyond what these checks measured.