Remote MCP · Endpoint

Data Angers MCP server

No. Data Angers answered an MCP handshake 55 minutes ago.

UpLast checked 55 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/data-angers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
67 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Angers Loire Métropole Open Data (data.angers.fr) — OpenDataSoft MCP.
Listing
From the official MCP registry (active).
Recent checks of Data Angers
CheckedResultHandshake
55 minutes agoHandshake completed67 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed56 ms
6 days agoHandshake completed64 ms
7 days agoHandshake completed83 ms
9 days agoHandshake completed92 ms
10 days agoHandshake completed195 ms
11 days agoHandshake completed50 ms
14 days agoHandshake completed50 ms
16 days agoHandshake completed47 ms
17 days agoHandshake completed251 ms
19 days agoHandshake completed43 ms
20 days agoHandshake completed36 ms
21 days agoHandshake completed47 ms
22 days agoHandshake completed42 ms
22 days agoHandshake completed48 ms

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

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