Transport for London
Transport for London (TfL) MCP server providing real-time London transport data through three core tools: line status monitoring, detailed disruption information, and journey planning between any London locations or UK postcodes. Built by anoopt using the official TfL Unified API, it handles location disambiguation intelligently by presenting users with specific station options when multiple matches are found, and supports both basic status checks and comprehensive journey planning with walking directions, platform information, and disruption alerts. The server automatically injects TFL_API_KEY from environment variables and supports multiple transport modes including tube, bus, rail, and walking, making it valuable for commuters, travelers, and applications needing accurate London transport information.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- monitoring
- Source
- PulseMCP
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Transport for London from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp --scope user for --scope project to commit it to .mcp.json.