Skip to main content
Glama

Server Details

Live Polish rail data: boards for every station, delays, PLK disruptions, train punctuality.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.9/5.0

Scored across 7 tools

Disambiguation4/5

The three punctuality tools (poland_punctuality, poland_route_punctuality, poland_train_punctuality) share a concept but are cleanly scoped to carrier, route, and named-train respectively, with descriptions that state boundaries explicitly. poland_delays_now (live snapshot) vs poland_disruptions (official notices) could be momentarily confused but the descriptions separate 'delay statistics' from 'planned works notices' well. find_station and station_departures are clearly complementary.

Naming Consistency3/5

A recognizable poland_* geographic prefix dominates, but the noun/verb patterns are mixed: find_station is verb_noun, station_departures is noun-only, poland_delays_now carries an adverbial suffix, and poland_punctuality is a bare noun while its siblings use poland_<scope>_punctuality. Readable and mostly themable, but not a single predictable convention.

Tool Count5/5

Seven tools is well-scoped for a Poland-specific rail data service: one lookup, one live board, two status feeds, and three punctuality granularities. Each tool covers a distinguishable slice and none feels redundant padding.

Completeness4/5

The surface covers station discovery, live departures, current delays, disruptions, and punctuality at carrier/route/train level — a coherent lifecycle for rail status data. The notable gap is that there is no connection/timetable search between two stations (route punctuality gives stats, not schedules) and no way to enumerate carriers or coverage lists, though agents can partly work around this via station departures.

Available Tools

7 tools
find_stationFind a stationA
Read-only
Inspect

Find railway stations by name in Poland – every passenger station, Polish letters optional. Returns the station name and the matching trainradar24.eu page.

Inputs: query (required).

poland_delays_nowCurrent train delays in PolandA
Read-only
Inspect

Snapshot of current train delays and cancellations across Poland: totals, the most delayed trains and cancelled trains. Refreshed several times a day.

Inputs: no named parameters.

poland_disruptionsRail disruptions in PolandA
Read-only
Inspect

Official PKP PLK disruption notices in Poland (closed sections, replacement buses, timetable changes), filtered by date and optionally by station or place name.

Inputs: date, limit, station.

poland_punctualityTrain punctuality ranking in PolandA
Read-only
Inspect

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.

Inputs: carrier.

poland_route_punctualityPunctuality of trains on a route in PolandA
Read-only
Inspect

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.

Inputs: to (required), from (required).

poland_train_punctualityPunctuality of a named train in PolandA
Read-only
Inspect

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.

Inputs: train (required).

station_departuresStation departure boardA
Read-only
Inspect

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.

Inputs: station (required), board, limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search Polish public transport timetables — trains, PKS/regional buses, and optionally urban transit in ~20 cities — by planning journeys with transfers, checking departures with platforms, and tracking live delays, cancellations and full trip details, all from open GTFS data without an API key. Station lookup tolerates typos and missing Polish diacritics, and endpoints can be a stop, a whole city, or coordinates.
      6
      117 npm
      34
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      An MCP server that provides access to the Koleo API for Polish train timetables, including station information, departures, and arrivals. It allows users to search for connections, view train routes, and access real-time timetable data and seat occupancy statistics.
      14
      7
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying live departure and arrival boards, delays, platforms, cancellations, crowding, stop-by-stop progress, and journey planning with up to one change for Lombardy's regional rail network, using public open data without an API key.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources