Remote MCP · Endpoint

Mobility Database MCP server

No. Mobility Database answered an MCP handshake 12 hours ago.

UpLast checked 12 hours ago

Server URL

https://gateway.pipeworx.io/mobility-database/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/mobility-database
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
44 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
MobilityData's open catalogue of public-transport feeds — ~4,500 GTFS schedule feeds and ~1,900…
Listing
From the official MCP registry (active).
Recent checks of Mobility Database
CheckedResultHandshake
12 hours agoHandshake completed68 ms
2 days agoHandshake completed339 ms
4 days agoHandshake completed67 ms
6 days agoHandshake completed87 ms
8 days agoHandshake completed69 ms
9 days agoHandshake completed221 ms
10 days agoHandshake completed58 ms
13 days agoHandshake completed53 ms
14 days agoHandshake completed54 ms
16 days agoHandshake completed831 ms
17 days agoHandshake completed1.27 s
19 days agoHandshake completed901 ms
20 days agoHandshake completed65 ms
21 days agoHandshake completed45 ms
21 days agoHandshake completed46 ms

The last 15 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 Mobility Database and makes no claim about it beyond what these checks measured.