Home / MCP registry index / uk.co.transitradar/transitradar

TransitRadar — UK trains and buses

uk.co.transitradar/transitradar in the official MCP registry. Endpoint https://transitradar.co.uk/mcp.

The registry describes it as: Live UK rail boards, journey planning, train history, units, lifts, disruptions, punctuality.

We read its 15 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

plan_journey bus_performance disruptions train_history get_train bus_stop_departures station_info station_departures daily_performance bus_disruptions find_train plan_door_to_door direct_destinations find_unit search_stations

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/uk-co-transitradar-transitradar/badge.svg)](https://lazaretto.dev/mcp-registry/uk-co-transitradar-transitradar)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.