rozklad-mcp
Registry code: 1f2464cb1c8f1d11
Polish public transport timetables (open data): all trains in Poland (PKP Intercity, Polregio, Koleje Mazowieckie, SKM, Koleje Śląskie/Dolnośląskie/Wielkopolskie/Małopolskie, ŁKA, Arriva, RegioJet, Leo Express, WKD), PKS / regional buses where carriers publish data, and optionally city transit.
Typical flow: plan_journey(from, to, date, time) answers most questions directly - station and town names are matched fuzzily (with or without Polish letters). Use departures for "what leaves X now", trip_details for a specific train (number like 3510 or a ref) incl. live delays, find_stops/nearby_stops…
- endpoint
- https://rozklad.compabase.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is rozklad-mcp live?
- Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
- Is rozklad-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does rozklad-mcp have?
- 8 tools: weather_warnings, plan_journey, departures, find_stops, nearby_stops, trip_details, data_sources, rail_disruptions.
- Is rozklad-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 8 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
data_sources open 19h ago
Which carriers/feeds are loaded, their validity dates, licences and required attribution; which feeds can be enabled.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesrail_disruptions open 19h ago
Current and upcoming disruptions on Polish railway lines from PKP PLK: track closures, replacement buses (ZKA), cancellations, diversions. Optional `query` filters by station name or text (e.g. "Kraków", "ZKA"). plan_journey, departures and trip_details already flag affected trains.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Max results (default 15)" }, "query": { "type": "string", "description": "Station name or text to filter by" } }, "additionalProperties": false }arguments 17 linesweather_warnings unknown never probed
Official IMGW-PIB meteorological warnings (storm, wind, frost, heat, snow, ice...) and flood warnings in Poland. With `place` (town, station or "lat,lon"): warnings for its county (powiat); without: national overview. plan_journey already adds warnings for the start and destination.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "place": { "type": "string", "description": "Town, station or 'lat,lon'" } }, "additionalProperties": false }arguments 11 linesplan_journey unknown never probed
Find connections between two places in Poland, including changes between trains and buses (PKS). from/to accept a station name ("Poznań Główny"), a town ("Zakopane" = all its stops) or coordinates "52.40,16.91". Returns several options with times, platforms, operators, changes and live delays (today).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "from", "to" ], "properties": { "to": { "type": "string", "description": "Destination: station, town or 'lat,lon'" }, "date": { "type": "string", "description": "Date: \"YYYY-MM-DD\", \"today\", \"tomorrow\", a weekday (\"friday\", \"piątek\") or \"DD.MM\". Default: today." }, "from": { "type": "string", "description": "Origin: station, town or 'lat,lon'" }, "live": { "type": "boolean", "description": "Include live delays (default true)." }, "time": { "type": "string", "description": "Local time \"HH:MM\" (Europe/Warsaw). Default: now (today) or 04:00 (other days)." }, "modes": { "type": "array", "items": { "enum": [ "train", "bus", "tram", "metro", "ferry", "all" ], "type": "string" }, "description": "Restrict to these modes, e.g. [\"train\"] or [\"train\",\"bus\"]. Default: all loaded." }, "results": { "type": "integer", "maximum": 10, "minimum": 1, "description": "Number of options (default 5)." }, "arrive_by": { "type": "boolean", "description": "If true, `time` is the latest arrival time instead of the earliest departure." }, "max_transfers": { "type": "integer", "maximum": 6, "minimum": 0, "description": "Maximum number of changes (default 3, 0 = direct only)." }, "min_transfer_minutes": { "type": "number", "maximum": 60, "minimum": 0, "description": "Minimum time for a change (default 4)." } }, "additionalProperties": false }arguments 68 linesdepartures unknown never probed
Departure (or arrival) board for a station or stop: time, live delay, train/bus line, platform, destination and main stops. Optionally only services going towards a given place.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "station" ], "properties": { "date": { "type": "string", "description": "Date: \"YYYY-MM-DD\", \"today\", \"tomorrow\", a weekday (\"friday\", \"piątek\") or \"DD.MM\". Default: today." }, "live": { "type": "boolean" }, "time": { "type": "string", "description": "Local time \"HH:MM\" (Europe/Warsaw). Default: now (today) or 04:00 (other days)." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Max rows (default 30)." }, "modes": { "type": "array", "items": { "enum": [ "train", "bus", "tram", "metro", "ferry", "all" ], "type": "string" }, "description": "Restrict to these modes, e.g. [\"train\"] or [\"train\",\"bus\"]. Default: all loaded." }, "station": { "type": "string", "description": "Station or stop name, e.g. 'Kraków Główny', 'Zbąszyń'" }, "arrivals": { "type": "boolean", "description": "Show arrivals instead of departures." }, "direction": { "type": "string", "description": "Only services that later call at this place, e.g. 'Poznań'." }, "duration_minutes": { "type": "integer", "maximum": 1440, "minimum": 10, "description": "Time window (default 120)." } }, "additionalProperties": false }arguments 60 linesfind_stops unknown never probed
Search stations/stops by name (fuzzy, diacritics optional). Shows modes, coordinates and source feeds.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1 }, "modes": { "type": "array", "items": { "enum": [ "train", "bus", "tram", "metro", "ferry", "all" ], "type": "string" }, "description": "Restrict to these modes, e.g. [\"train\"] or [\"train\",\"bus\"]. Default: all loaded." }, "query": { "type": "string", "description": "Name or part of it, e.g. 'warszawa centr', 'Szklarska'" } }, "additionalProperties": false }arguments 34 linesnearby_stops unknown never probed
Stations and stops within a radius of coordinates (e.g. after geocoding an address).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "lat", "lon" ], "properties": { "lat": { "type": "number", "maximum": 56, "minimum": 48 }, "lon": { "type": "number", "maximum": 25, "minimum": 13 }, "modes": { "type": "array", "items": { "enum": [ "train", "bus", "tram", "metro", "ferry", "all" ], "type": "string" }, "description": "Restrict to these modes, e.g. [\"train\"] or [\"train\",\"bus\"]. Default: all loaded." }, "radius_m": { "type": "integer", "maximum": 5000, "minimum": 50, "description": "Default 800 m" } }, "additionalProperties": false }arguments 42 linestrip_details unknown 19h ago
All stops of one train or bus run with times, platforms and live delays/cancellations. Identify it by `ref` (from plan_journey/departures) or by train number/name (e.g. '3510', 'IC 3510', 'Podhalanin') plus date.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "ref": { "type": "string", "description": "Trip ref like 'polish-trains:PLK_IC_2026_123@2026-10-20'" }, "date": { "type": "string", "description": "Date: \"YYYY-MM-DD\", \"today\", \"tomorrow\", a weekday (\"friday\", \"piątek\") or \"DD.MM\". Default: today." }, "live": { "type": "boolean" }, "train": { "type": "string", "description": "Train number or name" } }, "additionalProperties": false }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id1f2464cb1c8f1d11.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1f2464cb1c8f1d11/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1f2464cb1c8f1d11?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- compabase.com compabase