Remote MCP · Endpoint

France Geodata MCP server

No. France Geodata answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://gateway.pipeworx.io/france-geodata/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/france-geodata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
211 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
France Geodata MCP — point/radius questions on French public geodata.
Listing
From the official MCP registry (active).
Recent checks of France Geodata
CheckedResultHandshake
30 minutes agoHandshake completed211 ms
3 days agoHandshake completed70 ms
13 days agoHandshake completed107 ms
14 days agoHandshake completed150 ms
15 days agoHandshake completed104 ms
16 days agoHandshake completed104 ms
17 days agoHandshake completed183 ms
18 days agoHandshake completed107 ms
19 days agoHandshake completed168 ms
21 days agoHandshake completed75 ms
23 days agoHandshake completed1.10 s
25 days agoHandshake completed1.02 s

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

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