Remote MCP · Endpoint

StatsMapped Public Data MCP server

No. StatsMapped Public Data answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.statsmapped.com/mcp

The last check completed an MCP handshake.

Registry name
com.statsmapped/public-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
376 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public statistics for Ireland and the UK: housing, crime, health, economy, welfare, with caveats.
Listing
From the official MCP registry (active).
Recent checks of StatsMapped Public Data
CheckedResultHandshake
1 hour agoHandshake completed376 ms
1 day agoHandshake completed343 ms
2 days agoHandshake completed229 ms
2 days agoHandshake completed176 ms
4 days agoHandshake completed281 ms
7 days agoHandshake completed356 ms
9 days agoHandshake completed172 ms
12 days agoHandshake completed212 ms
14 days agoHandshake completed194 ms
16 days agoHandshake completed341 ms
18 days agoHandshake completed466 ms
20 days agoHandshake completed241 ms
22 days agoHandshake completed171 ms
24 days agoHandshake completed335 ms

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

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 StatsMapped Public Data and makes no claim about it beyond what these checks measured.