A
licenseB
qualityD
maintenanceProvides real-time Transport for London journey data, including routes, alerts, and disruptions, allowing AI assistants to search journeys and get station information.
1
11 npm
4
ISC
TfL Journey Status MCP Server
by anoopt
Related Servers
Alternatives to TfL Journey Status MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to access real-time Transport for London data, including tube/bus arrivals, line status, journey planning, and disruptions.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to query live Transport for London data, including service status, arrivals, journey planning, bike points, crowding, and fares.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides real-time Transport for London data including line status, journey planning, and disruption information via the TfL Unified API.11 npmMIT
- FlicenseBqualityCmaintenanceEnables Claude AI to access real-time Transport for London data for line status, journey planning, arrivals, bus routes, fares, and disruptions through natural language.13-
- FlicenseNot gradedqualityCmaintenanceProvides live UK rail data including station search, departures, arrivals, service details, and pre-filled Trainline booking links.-
TDQS
C2.9/5.0
Scored across 3 tools
Disambiguation2/5
The tools 'get_line_status' and 'get_line_status_detail' have significant overlap in purpose, both retrieving line status information with only a vague distinction in detail level. This creates ambiguity for an agent trying to choose between them, as the descriptions don't clearly differentiate when to use each tool.
Naming Consistency4/5
All three tools follow a consistent verb_noun naming pattern with snake_case. 'get_line_status' and 'get_line_status_detail' share the same verb prefix, while 'plan_journey' uses a different but still clear verb. The naming is mostly consistent with only minor deviation in verb choice.
Tool Count3/5
With only 3 tools, this server feels thin for a transportation domain that typically involves multiple operations. While the core functions are present, the count is borderline low for what could be a more comprehensive TfL API surface covering additional journey planning or status features.
Completeness2/5
For a TfL journey status server, there are significant gaps in coverage. Missing are tools for station information, arrival predictions, service disruptions beyond line status, and journey planning variations (like alternatives or real-time updates). The surface provides only basic line status and journey planning, leaving many common transportation queries unaddressed.
Maintenance
ActivityInactive
ResponsivenessNo issues