A
licenseNot graded
qualityB
maintenanceEnables AI assistants to query live Transport for London data, including service status, arrivals, journey planning, bike points, crowding, and fares.
1
MIT
Tifa
by dazyoung
Related Servers
Alternatives to Tifa
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-
- AlicenseCqualityDmaintenanceProvides real-time access to Transport for London data, enabling users to check tube line statuses, get disruption details, and plan journeys between London locations. Uses the official TfL Unified API to deliver live transport information through AI assistants.38 npmMIT
- AlicenseBqualityDmaintenanceProvides real-time Transport for London journey data, including routes, alerts, and disruptions, allowing AI assistants to search journeys and get station information.13 npm4ISC
- 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-
transcapi-mcpofficial
AlicenseAqualityBmaintenanceConnects AI assistants to live public transport data across Great Britain, enabling searches for stops and stations, real-time bus and rail departures, live vehicle positions, service disruptions, and door-to-door journey planning. All tools are read-only and require an API key.1029 PyPIMIT
TDQS
A3.9/5.0
Scored across 7 tools
Disambiguation4/5
Each tool has a distinct scope: list_lines and causes are reference lookups, current_status is a network-wide now snapshot, line_status is a per-line deep dive, disruptions is a paged record query, and period_stats/coverage are aggregate analytics. The main risk is overlap between line_status (which includes recent disruptions and per-line counts) and period_stats (which can also produce a per-line table), plus the near-pair naming current_status vs line_status. Descriptions do enough to steer an agent, but the boundary between per-line stats and period stats requires careful reading.
Naming Consistency3/5
All names are lowercase snake_case, which is consistent, but the grammatical pattern is mixed: list_lines is verb_noun, current_status is adjective_noun, line_status is noun_noun, and disruptions/coverage/causes are bare nouns. The verb-style tools imply actions while the noun-style ones are queries, so an agent cannot infer the calling convention from the name alone. Still readable and domain-conventional.
Tool Count5/5
Seven tools is well within the ideal range for a single-domain read-only analytics server. Each one earns its place: two reference lookups, one live snapshot, one per-line detail, one raw record query, one period aggregation and one data-quality checker. No obvious redundancy or filler.
Completeness4/5
The surface covers the lifecycle of observed disruption data well: enumerating lines and causes, live status, historical records with filtering and pagination, period comparisons, and coverage/staleness checks. Minor gaps remain — there is no way to fetch a single disruption by id, no manual poll/refresh trigger, and no direct way to explore inter-line (shared track) correlation despite list_lines exposing that information.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues