Remote MCP · Endpoint

Faceabot Transit Norway (Vy, Entur) MCP server

No. Faceabot Transit Norway (Vy, Entur) answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://faceabot.com/tools-mcp/no-transit

The last check completed an MCP handshake.

Registry name
com.faceabot/transit-norway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
720 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Norwegian trains, buses and ferries: live trips and departures (Entur). Free, no key.
Listing
From the official MCP registry (active).
Recent checks of Faceabot Transit Norway (Vy, Entur)
CheckedResultHandshake
19 minutes agoHandshake completed720 ms
9 days agoHandshake completed759 ms
9 days agoHandshake completed383 ms
11 days agoHandshake completed175 ms
12 days agoHandshake completed581 ms
13 days agoHandshake completed204 ms
14 days agoHandshake completed73 ms
15 days agoHandshake completed206 ms
16 days agoHandshake completed195 ms
19 days agoHandshake completed69 ms
21 days agoHandshake completed40 ms
24 days agoHandshake completed3.09 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 Faceabot Transit Norway (Vy, Entur) and makes no claim about it beyond what these checks measured.