# TransitRadar — UK trains and buses (remote · transitradar.co.uk)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `transitradar.co.uk`: 71/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-transitradar-transitradar/transitradar.md), [page](https://verifymcp.io/servers/uk-co-transitradar-transitradar/transitradar)

## Channel facts

- Endpoint: `https://transitradar.co.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http uk-co-transitradar-transitradar 'https://transitradar.co.uk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-transitradar-transitradar": {
      "url": "https://transitradar.co.uk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-transitradar-transitradar": {
      "type": "http",
      "url": "https://transitradar.co.uk/mcp"
    }
  }
}
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-transitradar-transitradar --url 'https://transitradar.co.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-transitradar-transitradar:
    url: "https://transitradar.co.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-transitradar-transitradar": {
      "Transport": "http",
      "Url": "https://transitradar.co.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-transitradar-transitradar -t streamable-http -u 'https://transitradar.co.uk/mcp'
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 71)

First indexed and scored.

## MCP tools (9)

### `disruptions` (~130 tokens)

Rail disruptions

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.

Input parameters:

- `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'.

### `get_train` (~172 tokens)

Train details and live running

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.

Input parameters:

- `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, required): Planning ID / UID, e.g. 'C04207'. Get one from find_train or station_departures.

### `bus_stop_departures` (~177 tokens)

Next buses from a stop

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.

Input parameters:

- `stop` (string, required): Stop name with town, optionally a stop letter, or a stop code: e.g. 'Trafalgar Square London stop X', '490015196OF'.

### `station_info` (~133 tokens)

Station details and lift status

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.

Input parameters:

- `station` (string, required): Station name, CRS code (KGX) or TIPLOC.

### `station_departures` (~173 tokens)

Live departures or arrivals

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.

Input parameters:

- `includeNonPassenger` (boolean): Include empty stock, freight and staff trains.
- `rows` (integer): How many trains to return, 1-30.
- `station` (string, required): Station name, CRS code (KGX) or TIPLOC.
- `type` (string): 'departures' (default) or 'arrivals'.

### `daily_performance` (~168 tokens)

How the railway did on a day

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.

Input parameters:

- `date` (string, required): Completed date, yyyy-MM-dd, e.g. '2026-09-26'.
- `operators` (integer): How many operators to include, largest first, 1-40.

### `find_train` (~195 tokens)

Find a train

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.

Input parameters:

- `date` (string|null): Date to search, yyyy-MM-dd. Defaults to today (UK time).
- `query` (string, required): Search text, e.g. 'GWR 1A20', '09:45 from Bath Spa', 'York to Leeds'.

### `find_unit` (~144 tokens)

Where is a train unit

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.

Input parameters:

- `date` (string|null): Date, yyyy-MM-dd. Defaults to today (UK time).
- `number` (string, required): Six-digit unit or vehicle number, e.g. '360107'.

### `search_stations` (~108 tokens)

Search stations

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.

Input parameters:

- `includeJunctions` (boolean): Also return junctions, yards and other non-station timing points.
- `query` (string, required): Station name or code, e.g. 'kings cross', 'Leeds', 'MAN'.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-transitradar-transitradar/transitradar#diagnostics

## Score history

- 2026-09-28: 71
- 2026-09-27: 71

## 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.

## Links

- Remote endpoint: https://transitradar.co.uk/mcp
- Website: https://transitradar.co.uk/assistants
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-transitradar-transitradar/transitradar.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-transitradar-transitradar/transitradar.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-transitradar-transitradar/transitradar