TransitRadar — UK trains and buses

uk.co.transitradar由 transitradar.co.uk 发布官方发布者v1.4.0更新于 Oct 24, 2026

Live UK rail boards, journey planning, train history, units, lifts, disruptions, punctuality.

已验证Streamable HTTP可网页运行位置与生活数据与分析

概览

AI 生成的概览

远程 MCP 服务器,为助手提供英国铁路与公交的实时数据:行程规划、出发看板、晚点、中断、车站信息与准点率。

可以做什么
规划行程:纯铁路或门到门(结合火车、公交与步行),以及从某站出发无需换乘可直达的目的地。查询列车:搜索时刻表、获取完整停靠站详情、近期实际运行记录,以及某编号车组当前担当的班次。查看实时看板:车站出发与到达信息、某公交站的下一班车、当前晚点或取消的列车。了解中断情况:当前及计划的铁路事件与工程作业,以及公交改道、封闭站点与道路施工。查看准点率与车站:每日准点数据、公交准点估算、车站设施、无障碍通道与电梯状态。
适用场景
适合用户询问英国火车或公交出行时使用:规划路线、确认列车是否晚点、查找下一班出发,或了解某次中断的原因。也适合查询车站设施、无障碍情况和近期准点率。
运行要求
通过 streamable HTTP 连接 transitradar.co.uk 的远程端点;未声明任何软件包、账户、API 密钥或环境变量。需要能访问该端点的网络。
安装前请注意
多为只读的时刻表与实时运行数据,但部分工具会返回晚点赔偿(Delay Repay)申请链接,任何申请或付款步骤请自行核实。基于时刻表的方案并非实时运行状态,公交准点数据为抽样城市区域的估算值。数据来自 National Rail、Bus Open Data Service 等第三方来源。

安装

在 SourceWeft 中

  1. 打开 控制台中的 TransitRadar — UK trains and buses,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/uk.co.transitradar%2Ftransitradar/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "transitradar-uk-trains-and-buses": {
      "type": "http",
      "url": "https://transitradar.co.uk/mcp"
    }
  }
}

工具

16

plan_journey

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.

输入参数to必填datefrom必填timeresults

bus_performance

How buses are running today

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.

输入参数limit

late_trains

Trains late or cancelled now

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.

输入参数limitminLateoperatorName

disruptions

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.

输入参数textlimitoperatorName

train_history

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.

输入参数daysplanningId必填

get_train

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.

输入参数dateplanningId必填

bus_stop_departures

Next buses from a stop

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.

输入参数tostop必填

station_info

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

输入参数station必填

station_departures

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

输入参数torowstypestation必填includeNonPassenger

daily_performance

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.

输入参数date必填operators

bus_disruptions

Bus disruptions

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.

输入参数limitqueryoperatorCode

find_train

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 results for one headcode can be different trains, told apart by origin and destination. Returns planning IDs to pass to get_train.

输入参数datequery必填

plan_door_to_door

Plan a journey by train and bus

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.

输入参数to必填datefrom必填timeresults

direct_destinations

Where can I go without changing

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.

输入参数datefrom必填timelimitmaxMinutes

find_unit

Where is a train unit

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.

输入参数datenumber必填

search_stations

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. The CRS code is what the other station tools accept.

输入参数query必填includeJunctions

版本历史

4
  1. v1.4.0最新Oct 22, 2026
  2. v1.3.0Oct 15, 2026
  3. v1.1.0Oct 4, 2026
  4. v1.0.0Sep 27, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。