Remote MCP · Endpoint

Transport & travel MCP server

No. Transport & travel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fourzerotwo.si/mcp/v/transport

The last check completed an MCP handshake.

Registry name
si.fourzerotwo/transport
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
388 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Airports, runways and frequencies worldwide, tides, UK road collisions and London transport.
Listing
From the official MCP registry (active).
Recent checks of Transport & travel
CheckedResultHandshake
1 hour agoHandshake completed388 ms
1 day agoHandshake completed232 ms
2 days agoHandshake completed205 ms
3 days agoHandshake completed214 ms
4 days agoHandshake completed204 ms
5 days agoHandshake completed232 ms
6 days agoHandshake completed210 ms
9 days agoHandshake completed196 ms
11 days agoHandshake completed207 ms
14 days agoHandshake completed293 ms
16 days agoHandshake completed222 ms
18 days agoHandshake completed203 ms
20 days agoHandshake completed334 ms
22 days agoHandshake completed177 ms
24 days agoHandshake completed204 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 Transport & travel and makes no claim about it beyond what these checks measured.