TransitRadar — UK trains and buses
REMOTE · TRANSITRADAR.CO.UK
Live UK rail boards, journey planning, train history, units, lifts, disruptions, punctuality.
Available components
Last scanned (3 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2998 tokens (~187/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- Tool “plan_journey” rewrote its description, which is the text the model reads security
- “plan_journey” added an optional parameter “via” cosmetic
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Probed https://transitradar.co.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=transitradar.co.uk | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 551bbdc8aa8f90320e96eb0396513a4e |
| SANs: transitradar.co.uk, *.transitradar.co.uk | ||||||
| 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 transitradar.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| co.uk. | DS published | 11810 | 8 | Verified |
| transitradar.co.uk. | No DS | 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://transitradar.co.uk/mcp | Verified | 200 | |
| http (plaintext) | http://transitradar.co.uk/mcp | HTTPS enforced | 301 | https://transitradar.co.uk/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 →
bus_disruptions Bus disruptions ~162
Current and planned bus disruptions in Great Britain from the Bus Open Data Service (SIRI-SX): diversions, closed stops, roadworks and events, each with the operators and lines affected and the stops named. Filter by operator code (NOC) or by a word matched against the text, e.g. a town, road or line. Rail incidents are the separate 'disruptions' tool.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return, 1-30. |
| operatorCode | string|null | – | Operator NOC code, e.g. 'FLDS' for First Leeds. |
| query | string|null | – | Words to match in the disruption, e.g. 'Leeds', 'A61', 'line 36'. |
No output schema declared.
No examples provided.
bus_performance How buses are running today ~135
Today's bus punctuality estimate for Great Britain, nationally and by operator: journeys counted, the share on time, early and late, and the average delay. Each bus journey is counted once, judged on arrival near its last stop, and only in the roughly 25 urban areas we sample, so it is an ESTIMATE of how buses are running, not an official figure. 'On time' follows the GB bus standard: up to 1 minute early or 5 minutes 59 late; running early counts against it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many operators to return, 1-30, most journeys first. |
No output schema declared.
No examples provided.
bus_stop_departures Next buses from a stop ~274
Next buses from a bus stop anywhere in Great Britain. Takes a stop name with its town or area; many stops share a name across the country, so 'Trafalgar Square' alone can land in Greater Manchester while 'Trafalgar Square London' finds Charing Cross. A stop letter can follow, e.g. 'Trafalgar Square London stop X'. A stop's ATCO/NaPTAN code also works. Live predictions in London (TfL); elsewhere the timetable, so a 'scheduled' time is not a live estimate. With 'to', only buses that go on to that stop are listed, each with its scheduled time there: the answer to 'next bus from Trafalgar Square to Brixton Station'. Those boards always come from the timetable, with the live bus and its delay where it can be identified. Other matching stops are returned alongside.
| Name | Type | Req | Description |
|---|---|---|---|
| stop | string | yes | Stop name with town, optionally a stop letter, or a stop code: e.g. 'Trafalgar Square London stop X', '490015196OF'. |
| to | string|null | – | Optional stop the bus must go on to, with its town: e.g. 'Brixton Station London'. Every stop of that name there counts unless a stop letter is given. |
No output schema declared.
No examples provided.
daily_performance How the railway did on a day ~166
TransitRadar's own record of one completed day on GB passenger rail: how many trains ran, how many were cancelled, the share of recorded arrivals within five minutes at their destination, the same share counting each cancellation as a failure, per-operator figures, and the commonest delay and cancellation reasons. Measured at the destination, so it is stricter than, and not comparable with, the industry's published PPM. Available from 2026-08-06 up to yesterday; where fewer than half of arrivals were recorded, no punctuality figure is given.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Completed date, yyyy-MM-dd, e.g. '2026-09-26'. |
| operators | integer | – | How many operators to include, largest first, 1-40. |
No output schema declared.
No examples provided.
direct_destinations Where can I go without changing ~215
Every station reachable from a GB railway station WITHOUT CHANGING TRAINS on a date, after a time, each with the train that gets there soonest (a later but faster train beats an earlier slow one), sorted by arrival. Includes places reached by staying aboard a train that divides or joins another en route: those rows carry an 'association' naming where, and the passenger must be in the right portion. Timetabled times, not live. Use plan_journey when a change of train is acceptable or a destination is already known.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Date, yyyy-MM-dd. Defaults to today (UK time). |
| from | string | yes | Station to travel from: name or CRS code. |
| limit | integer | – | How many destinations to return, 1-50, soonest arrival first. |
| maxMinutes | integer|null | – | Only destinations reached within this many minutes of departure. |
| time | string|null | – | Leave after this time, HH:mm UK time. Defaults to now. |
No output schema declared.
No examples provided.
disruptions Rail disruptions ~130
Current GB rail incidents and planned engineering work from National Rail's KnowledgeBase: what is affected, the operators, the dates and a link to National Rail's notice. Optionally filter by operator (name or two-letter code) or by any text, such as a station, line or reason.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum notices to return, 1-30. |
| operatorName | string|null | – | Operator name or code, e.g. 'Northern' or 'NT'. |
| text | string|null | – | Text to match in the notice, e.g. 'Whitehaven', 'signalling'. |
No output schema declared.
No examples provided.
find_train Find a train ~206
Search the GB rail timetable for specific trains. The query combines terms: an operator and a headcode ('LNER 1S09', 'EMR 1H26'), a time and a station ('12:19 from Corby' — matched within about ten minutes either side), two stations ('Corby to St Pancras', which also finds trains calling at both), or a planning ID / UID ('C12345', or its first few characters). A headcode alone is not unique: the same four characters run in several parts of the country at once, so results for one headcode can be different trains, told apart by origin and destination. Returns planning IDs to pass to get_train.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Date to search, yyyy-MM-dd. Defaults to today (UK time). |
| query | string | yes | Search text, e.g. 'GWR 1A20', '09:45 from Bath Spa', 'York to Leeds'. |
No output schema declared.
No examples provided.
find_unit Where is a train unit ~149
Look up a GB passenger train unit or carriage by the five- or six-digit number painted on it (e.g. '360107'): which service it is working now, the other services it is booked to work today, and the last calling point it was reported at. This comes from the operator's rolling-stock allocation, which is a plan and may be wrong during disruption. The position is the last calling point reported, not a live GPS fix — the train is somewhere beyond it.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Date, yyyy-MM-dd. Defaults to today (UK time). |
| number | string | yes | Five- or six-digit unit or vehicle number, e.g. '360107'. |
No output schema declared.
No examples provided.
get_train Train details and live running ~172
Full details of one train by its planning ID (UID, e.g. 'C04207'): every public calling point with booked, expected and actual times, platforms and per-stop cancellations, plus — for today's trains — where it was last reported and how late. A cancellation can apply to only some stops. 'lastReport' is the last place signalling or movement data placed the train, not a GPS position. Reasons are National Rail's own words.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Date the train runs, yyyy-MM-dd. Defaults to today (UK time). Past dates return recorded times where the archive holds them (about 14 days of per-stop detail). |
| planningId | string | yes | Planning ID / UID, e.g. 'C04207'. Get one from find_train or station_departures. |
No output schema declared.
No examples provided.
late_trains Trains late or cancelled now ~163
GB passenger trains running late right now, and trains booked to be running now that are cancelled (wholly or part of the way). Each train has its route, how late it is, where it last reported, where it calls next, the reason Darwin gives, and a Delay Repay link once a claim is worth making. Optionally filter by operator (name or two-letter code) or set the lateness threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum trains to return, 1-50, cancellations first, then the latest. |
| minLate | integer | – | Minutes late to count as late, 1-120. Default 5. |
| operatorName | string|null | – | Operator name or code, e.g. 'Northern' or 'NT'. |
No output schema declared.
No examples provided.
plan_door_to_door Plan a journey by train and bus ~231
Plan a GB journey that may combine trains, buses and short walks, between railway stations, bus stops or coordinates, from the timetables. Each place can be a station name or CRS code, a bus stop with its town (e.g. 'Briggate Leeds'), a stop code, or 'lat,lon'. Returns the next few ways after a time with every leg: mode, line or train, where to board and alight, and times. Timetabled, not live. For rail only, plan_journey is simpler.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Date, yyyy-MM-dd. Defaults to today (UK time). |
| from | string | yes | Where from: station, bus stop with town, stop code, or 'lat,lon'. |
| results | integer | – | How many journeys to return, 1-5. |
| time | string|null | – | Leave after this time, HH:mm UK time. Defaults to now. |
| to | string | yes | Where to: station, bus stop with town, stop code, or 'lat,lon'. |
No output schema declared.
No examples provided.
plan_journey Plan a rail journey ~262
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. 'via' forces the route through up to 3 stations in order ('Darwen to Penrith via Bolton'), staying aboard where one train does it. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string|null | – | Date, yyyy-MM-dd. Defaults to today (UK time). |
| from | string | yes | Station to travel from: name or CRS code. |
| results | integer | – | How many journeys to return, 1-5. |
| time | string|null | – | Leave after this time, HH:mm UK time. Defaults to now. |
| to | string | yes | Station to travel to: name or CRS code. |
| via | string|null | – | Optional stations the journey must go through, in order: up to 3 names or CRS codes, comma-separated, e.g. 'Bolton' or 'Preston,Lancaster'. |
No output schema declared.
No examples provided.
search_stations Search stations ~104
Find GB railway stations by name or code. Returns each station's three-letter CRS code (e.g. KGX), its TIPLOC and whether it has step-free access. The CRS code is what the other station tools accept.
| Name | Type | Req | Description |
|---|---|---|---|
| includeJunctions | boolean | – | Also return junctions, yards and other non-station timing points. |
| query | string | yes | Station name or code, e.g. 'kings cross', 'Leeds', 'MAN'. |
No output schema declared.
No examples provided.
station_departures Live departures or arrivals ~250
Live departure or arrival board for a GB railway station, from National Rail's Darwin feed: booked time, expected time, actual time once reported, platform, 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 means no revision has been published, which usually means running to plan. A missing expected time is not a statement that the train is on time. Reasons are National Rail's own wording.
| Name | Type | Req | Description |
|---|---|---|---|
| includeNonPassenger | boolean | – | Include empty stock, freight and staff trains. |
| rows | integer | – | How many trains to return, 1-30. |
| station | string | yes | Station name, CRS code (KGX) or TIPLOC. |
| to | string|null | – | Optional second station (name or CRS): only trains that call there after this one on departures, or before it on arrivals. |
| type | string | – | 'departures' (default) or 'arrivals'. |
No output schema declared.
No examples provided.
station_info Station details and lift status ~138
Details of a GB railway station: address, managing operator, facilities, step-free access, industry codes (CRS, TIPLOC, STANOX, NLC) and, where Network Rail publishes it, the live status of each public lift. Lift status is 'In service', 'Out of service' or 'Data not available'; the last means the status is not known, and Network Rail's wording for it advises checking before travel. A station with no lifts listed is not necessarily a station without lifts; it may not report live status yet.
| Name | Type | Req | Description |
|---|---|---|---|
| station | string | yes | Station name, CRS code (KGX) or TIPLOC. |
No output schema declared.
No examples provided.
train_history How a train has run recently ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many days back to look, 1-60. |
| planningId | string | yes | Planning ID / UID, e.g. 'P24061'. |
No output schema declared.
No examples provided.
How do I install the TransitRadar — UK trains and buses MCP server?
TransitRadar — UK trains and buses is a hosted endpoint at https://transitradar.co.uk/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 · transitradar.co.uk
claude mcp add --transport http uk-co-transitradar-transitradar 'https://transitradar.co.uk/mcp'
What is the TransitRadar — UK trains and buses MCP server?
TransitRadar — UK trains and buses is an MCP server listed in the public MCP registry as uk.co.transitradar/transitradar. Live UK rail boards, journey planning, train history, units, lifts, disruptions, punctuality. This page covers its hosted endpoint (https://transitradar.co.uk/mcp).
Is the TransitRadar — UK trains and buses MCP server safe to use?
TransitRadar — UK trains and buses scores 84 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 TransitRadar — UK trains and buses MCP server expose?
TransitRadar — UK trains and buses exposes 16 tools: plan_journey, bus_performance, late_trains, disruptions, train_history, and 11 more. Their descriptions and schemas cost roughly 2,902 tokens of context every time the server is loaded.
Does the TransitRadar — UK trains and buses MCP server require authentication?
No. We connected to TransitRadar — UK trains and buses without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TransitRadar — UK trains and buses MCP server still maintained?
TransitRadar — UK trains and buses is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TransitRadar — UK trains and buses MCP server?
VerifyMCP ran 13 checks on TransitRadar — UK trains and buses, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.