Remote MCP · Endpoint

Datacommons MCP server

No. Datacommons answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://gateway.pipeworx.io/datacommons/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/datacommons
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
61 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Data Commons MCP — harmonised public statistics for places, from Google Data Commons (REST v2).
Listing
From the official MCP registry (active).
Recent checks of Datacommons
CheckedResultHandshake
33 minutes agoHandshake completed61 ms
8 days agoHandshake completed123 ms
9 days agoHandshake completed1.04 s
11 days agoHandshake completed819 ms
12 days agoHandshake completed742 ms
13 days agoHandshake completed337 ms
14 days agoHandshake completed163 ms
14 days agoHandshake completed165 ms
16 days agoHandshake completed311 ms
19 days agoHandshake completed299 ms
21 days agoHandshake completed1.06 s
24 days agoHandshake completed93 ms
26 days agoHandshake completed87 ms
28 days agoHandshake completed993 ms

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

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