Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TransitRadar — UK trains and buses

REMOTE · TRANSITRADAR.CO.UK · SCANNED SEP 28

Live UK rail departures, trains, unit numbers, station lifts, disruptions and daily punctuality.

71 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1505 tokens (~167/item across 9 items; 9 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
Install

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

# add to Claude Code
claude mcp add --transport http uk-co-transitradar-transitradar 'https://transitradar.co.uk/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "uk-co-transitradar-transitradar": {
      "url": "https://transitradar.co.uk/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "uk-co-transitradar-transitradar": {
      "type": "http",
      "url": "https://transitradar.co.uk/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.uk-co-transitradar-transitradar]
url = "https://transitradar.co.uk/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-transitradar-transitradar": {
      "type": "remote",
      "url": "https://transitradar.co.uk/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add uk-co-transitradar-transitradar --url 'https://transitradar.co.uk/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  uk-co-transitradar-transitradar:
    url: "https://transitradar.co.uk/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "uk-co-transitradar-transitradar": {
      "Transport": "http",
      "Url": "https://transitradar.co.uk/mcp"
    }
  }
}
# add to Vellum
assistant mcp add uk-co-transitradar-transitradar -t streamable-http -u 'https://transitradar.co.uk/mcp'
// mcp.json
{
  "mcpServers": {
    "uk-co-transitradar-transitradar": {
      "type": "http",
      "url": "https://transitradar.co.uk/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 28 Sept 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
  • 27 Sept 26 71

    First indexed and scored.

Diagnostics

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 28 Sept 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. present 43876 8 Verified
co.uk. present 11810 8 Verified
transitradar.co.uk. 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://transitradar.co.uk/mcp Verified 200
http (plaintext) http://transitradar.co.uk/mcp HTTPS enforced 301 https://transitradar.co.uk/mcp
MCP tools · 9 exposed · ~1,400 tokens

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 →

Tool Tokens
bus_stop_departures ~177

Next buses from a bus stop anywhere in Great Britain. Give the stop name AND 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. Other matching stops are returned so the right one can be chosen.

NameTypeReqDescription
stopstringyesStop name with town, optionally a stop letter, or a stop code: e.g. 'Trafalgar Square London stop X', '490015196OF'.

No output schema declared.

No examples provided.

daily_performance ~168

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.

NameTypeReqDescription
datestringyesCompleted date, yyyy-MM-dd, e.g. '2026-09-26'.
operatorsinteger–How many operators to include, largest first, 1-40.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
limitinteger–Maximum notices to return, 1-30.
operatorNamestring|null–Operator name or code, e.g. 'Northern' or 'NT'.
textstring|null–Text to match in the notice, e.g. 'Whitehaven', 'signalling'.

No output schema declared.

No examples provided.

find_train ~195

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 always check origin and destination. Returns planning IDs to pass to get_train.

NameTypeReqDescription
datestring|null–Date to search, yyyy-MM-dd. Defaults to today (UK time).
querystringyesSearch text, e.g. 'GWR 1A20', '09:45 from Bath Spa', 'York to Leeds'.

No output schema declared.

No examples provided.

find_unit ~144

Look up a GB passenger train unit or carriage by the 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.

NameTypeReqDescription
datestring|null–Date, yyyy-MM-dd. Defaults to today (UK time).
numberstringyesSix-digit unit or vehicle number, e.g. '360107'.

No output schema declared.

No examples provided.

get_train ~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.

NameTypeReqDescription
datestring|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).
planningIdstringyesPlanning ID / UID, e.g. 'C04207'. Get one from find_train or station_departures.

No output schema declared.

No examples provided.

search_stations ~108

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. Use this to turn a place name into the code the other tools take.

NameTypeReqDescription
includeJunctionsboolean–Also return junctions, yards and other non-station timing points.
querystringyesStation name or code, e.g. 'kings cross', 'Leeds', 'MAN'.

No output schema declared.

No examples provided.

station_departures ~173

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. 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 words and should be quoted, not paraphrased.

NameTypeReqDescription
includeNonPassengerboolean–Include empty stock, freight and staff trains.
rowsinteger–How many trains to return, 1-30.
stationstringyesStation name, CRS code (KGX) or TIPLOC.
typestring–'departures' (default) or 'arrivals'.

No output schema declared.

No examples provided.

station_info ~133

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 the traveller should check before travelling. A station with no lifts listed is NOT a station without lifts — it may simply not report live status yet.

NameTypeReqDescription
stationstringyesStation name, CRS code (KGX) or TIPLOC.

No output schema declared.

No examples provided.

Common questions

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 departures, trains, unit numbers, station lifts, disruptions and daily 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 71 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 9 tools: disruptions, get_train, bus_stop_departures, station_info, station_departures, and 4 more. Their descriptions and schemas cost roughly 1,400 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 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.