Remote MCP · Endpoint

Trainradar24 MCP server

No. Trainradar24 answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://mcp.trenify.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.trenify/trainradar24
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
194 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Live Polish rail data: boards for every station, delays, PLK disruptions, train punctuality.
Listing
From the official MCP registry (active).
Recent checks of Trainradar24
CheckedResultHandshake
42 minutes agoHandshake completed194 ms
3 days agoHandshake completed484 ms
12 days agoHandshake completed171 ms
12 days agoHandshake completed168 ms
14 days agoHandshake completed143 ms
15 days agoHandshake completed175 ms
16 days agoHandshake completed185 ms
17 days agoHandshake completed155 ms
18 days agoHandshake completed150 ms
19 days agoHandshake completed173 ms
22 days agoHandshake completed156 ms
25 days agoHandshake completed126 ms
27 days agoHandshake completed383 ms

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

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

Trainradar24 MCP server - status, uptime and latency - Glide