Remote MCP · Endpoint

Data Grandparissud MCP server

No. Data Grandparissud answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/data-grandparissud/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/data-grandparissud
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
78 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Grand Paris Sud Open Data (data.grandparissud.fr) — OpenDataSoft MCP.
Listing
From the official MCP registry (active).
Recent checks of Data Grandparissud
CheckedResultHandshake
1 hour agoHandshake completed78 ms
3 days agoHandshake completed38 ms
12 days agoHandshake completed107 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed145 ms
15 days agoHandshake completed981 ms
17 days agoHandshake completed1.06 s
18 days agoHandshake completed1.51 s
18 days agoHandshake completed356 ms
20 days agoHandshake completed266 ms
23 days agoHandshake completed104 ms
25 days agoHandshake completed267 ms
28 days agoHandshake completed246 ms

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

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