Trainradar24
REMOTE · MCP.TRENIFY.EU
Live Polish rail data: boards for every station, delays, PLK disruptions, train punctuality.
Available components
Last scanned (19 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 729 tokens (~104/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://mcp.trenify.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trenify.eu | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 84f048a06475bb0b13519ba0eeb136cb |
| SANs: trenify.eu, mcp.trenify.eu, *.mcp.trenify.eu | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.trenify.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| trenify.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.trenify.eu/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.trenify.eu/mcp | HTTPS enforced | 301 | https://mcp.trenify.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_station Find a station ~63
Find railway stations by name in Poland – every passenger station, Polish letters optional. Returns the station name and the matching trainradar24.eu page.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Station or city name, e.g. "Kraków" or "Gdansk" |
No output schema declared.
No examples provided.
poland_delays_now Current train delays in Poland ~39
Snapshot of current train delays and cancellations across Poland: totals, the most delayed trains and cancelled trains. Refreshed several times a day.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
poland_disruptions Rail disruptions in Poland ~88
Official PKP PLK disruption notices in Poland (closed sections, replacement buses, timetable changes), filtered by date and optionally by station or place name.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date YYYY-MM-DD; defaults to today in Poland |
| limit | integer | – | – |
| station | string | – | Station or place name to filter by, e.g. "Kostrzyn" |
No output schema declared.
No examples provided.
poland_punctuality Train punctuality ranking in Poland ~83
Trainradar24's own 30-day punctuality ranking of Polish rail carriers and the least punctual routes, computed from official PKP PLK traffic data. On time = arrived within 5 minutes and not cancelled.
| Name | Type | Req | Description |
|---|---|---|---|
| carrier | string | – | Filter by carrier name, e.g. "Intercity" or "Koleje Śląskie" |
No output schema declared.
No examples provided.
poland_route_punctuality Punctuality of trains on a route in Poland ~124
How punctual direct trains between two Polish cities were over the last 30 days (e.g. Gdańsk – Kraków, Warszawa – Zakopane): on-time share, typical delay, cancellations, trains per day. Covers the 100 most popular routes, each direction separately; if only the opposite direction is covered, that one is returned and marked.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | City or station, e.g. "Gdańsk" |
| to | string | yes | City or station, e.g. "Kraków" |
No output schema declared.
No examples provided.
poland_train_punctuality Punctuality of a named train in Poland ~119
How often a named long-distance train in Poland (e.g. "Flisak", "Kaszub", "Podhalanin" or its number, e.g. "54102") arrived on time over the last 30 days: on-time share, typical delay, cancellations. Covers about 30 named PKP Intercity trains; for other trains use poland_route_punctuality.
| Name | Type | Req | Description |
|---|---|---|---|
| train | string | yes | Train name or number, e.g. "Flisak", "IC 54102" |
No output schema declared.
No examples provided.
station_departures Station departure board ~109
Live departure or arrival board for any passenger railway station in Poland, small stops included: time, carrier, train number, destination or origin, platform, live delay, cancellation and replacement buses. Trains that already left are hidden.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | Arrivals are available for Poland only. |
| limit | integer | – | – |
| station | string | yes | Station name, e.g. "Warszawa Centralna", "Kraków Główny", "Krobia" |
No output schema declared.
No examples provided.
How do I install the Trainradar24 MCP server?
Trainradar24 is a hosted endpoint at https://mcp.trenify.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.trenify.eu
claude mcp add --transport http eu-trenify-trainradar24 'https://mcp.trenify.eu/mcp'
What is the Trainradar24 MCP server?
Trainradar24 is an MCP server listed in the public MCP registry as eu.trenify/trainradar24. Live Polish rail data: boards for every station, delays, PLK disruptions, train punctuality. This page covers its hosted endpoint (https://mcp.trenify.eu/mcp).
Is the Trainradar24 MCP server safe to use?
Trainradar24 scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Trainradar24 MCP server expose?
Trainradar24 exposes 7 tools: find_station, station_departures, poland_delays_now, poland_disruptions, poland_punctuality, and 2 more. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Does the Trainradar24 MCP server require authentication?
No. We connected to Trainradar24 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Trainradar24 MCP server still maintained?
Trainradar24 is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.