Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Added "plan_journey" and "train_history"; changed the definition of "station_departures" (9 tools before, 11 now)
⟨24 unchanged words⟩ , operator and any delay or cancellation reason. With 'to', only trains that also call at that station are listed, each with its booked, expected and actual time there: the live answer to 'next train from Bolton to Darwen'. On an arrivals board, 'to' is where the train came from. An expected time equal to the booked one ⟨32 unchanged words⟩
⟨33 unchanged words⟩ or TIPLOC.","type":"string"},"to":{"default":null,"description":"Optional second station (name or CRS): only trains that call there after this one on departures, or before it on arrivals.","type":["string","null"]},"type":{"default":"departures","description": ⟨10 unchanged words⟩
Plan a rail journey — Plan a GB rail journey between two stations from the timetable, including changes: the next few ways to get there after a time, each with departure, arrival, number of changes and every train to catch with where to board and alight. This is the timetable, not live running; for live times on a direct train use station_departures with 'to', and for one train's progress use get_train with its planning ID.
How a train has run recently — How one timetabled train has actually run over recent days, by its planning ID (from find_train, station_departures or get_train): each day's delay at its final destination, cancellations and any reason given, plus the share on time. Delay is measured where the train ends, not at any station along the way. History follows the planning ID, which changes when the timetable changes, so a newly timetabled train has little history; days the train did not run are simply absent.
Certificate recorded, valid to 2026-12-23
Authorization not required
Unknown → Live
First tool surface recorded: 9 tools (server version 1.0.0)
https://transitradar.co.uk/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 6 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed