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
126 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 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 completed126 ms
1 day agoHandshake completed188 ms
2 days agoHandshake completed212 ms
3 days agoHandshake completed189 ms
4 days agoHandshake completed110 ms
5 days agoHandshake completed187 ms
6 days agoHandshake completed259 ms
9 days agoHandshake completed148 ms
11 days agoHandshake completed152 ms
14 days agoHandshake completed679 ms
16 days agoHandshake completed111 ms
18 days agoHandshake completed240 ms
20 days agoHandshake completed3.39 s
22 days agoHandshake completed222 ms
24 days agoHandshake completed226 ms
26 days agoHandshake completed209 ms
27 days agoHandshake completed163 ms
29 days agoHandshake completed429 ms

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

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.