Tfl
NPM · @PIPEWORX/MCP-TFL · 2 COMPONENTS
Transport for London (TfL) Unified API MCP — keyless.
Available components
Last scanned (6 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-tfl). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 635 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 82
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-tfl@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-tfl |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-tfl/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560435077 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:765617a96506d8a91bcfd50dcaa61d99eb53d685c2f4bf1c6efa72d17ca53fbd6db987e415de0ae8496f117d6a6bfdcc91641ce65128aaed5066a7885 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
arrivals ~70
Real-time predicted arrivals at a stop. Pass the naptanId from stop_search (e.g. "940GZZLUOXC"). Results are sorted by timeToStation (seconds away), nearest first.
| Name | Type | Req | Description |
|---|---|---|---|
| naptanId | string | yes | Stop NaPTAN id, obtained from stop_search. |
No output schema declared.
No examples provided.
bike_points ~97
London Santander Cycle hire scheme — live pushbike and empty-dock counts at each London cycle-hire docking point (bikes available, spaces free, total capacity in additionalProperties). London public bicycle rental only. Pass an optional area filter, e.g. "Clerkenwell"; omit for all London cycle docks.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional name/area filter, e.g. "Clerkenwell". Omit for all docks. |
No output schema declared.
No examples provided.
disruptions ~58
Current disruptions for the given transport modes, with description and affected lines.
| Name | Type | Req | Description |
|---|---|---|---|
| modes | string | – | Comma-separated transport modes: tube, dlr, overground, elizabeth-line, bus, tram, national-rail. Defaults to "tube". |
No output schema declared.
No examples provided.
line_status ~143
Current service status for London transport lines. Pass either a comma-separated list of modes (e.g. "tube,dlr") OR a specific lineId (e.g. "victoria", "central"). Returns each line with lineStatuses + statusSeverityDescription (e.g. "Good Service", "Minor Delays").
| Name | Type | Req | Description |
|---|---|---|---|
| lineId | string | – | Specific line id, e.g. "victoria", "central", "elizabeth". Takes precedence over modes. |
| modes | string | – | Comma-separated transport modes: tube, dlr, overground, elizabeth-line, bus, tram, national-rail. Used when lineId is not given. |
No output schema declared.
No examples provided.
plan_journey ~112
Plan a journey across London transport. from/to may be stop names, postcodes, or "lat,lon" coordinates. Returns journey options (legs, durations, modes). If a location is ambiguous, the API returns disambiguation options instead of journeys — refine the input or use a naptanId/coords.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Origin: stop name, postcode, or "lat,lon". |
| to | string | yes | Destination: stop name, postcode, or "lat,lon". |
No output schema declared.
No examples provided.
stop_search ~103
Search for stops/stations by name. Returns matches with a naptanId (the "id" field) used by the arrivals tool, plus modes, zone, and lat/lon.
| Name | Type | Req | Description |
|---|---|---|---|
| modes | string | – | Optional filter. Comma-separated transport modes: tube, dlr, overground, elizabeth-line, bus, tram, national-rail. |
| query | string | yes | Stop/station name to search for, e.g. "Oxford Circus". |
No output schema declared.
No examples provided.
How do I install the Tfl MCP server?
Tfl runs locally as an npm package, launched with npx -y @pipeworx/mcp-tfl. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-tfl
claude mcp add pipeworx-io-tfl -- npx -y @pipeworx/mcp-tfl
What is the Tfl MCP server?
Tfl is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tfl. Transport for London (TfL) Unified API MCP, keyless. This page covers its npm package (@pipeworx/mcp-tfl).
Is the Tfl MCP server safe to use?
Tfl scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tfl MCP server expose?
Tfl exposes 6 tools: line_status, stop_search, arrivals, plan_journey, bike_points, disruptions. Their descriptions and schemas cost roughly 583 tokens of context every time the server is loaded.
Is the Tfl MCP server still maintained?
Tfl is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tfl MCP server under?
Tfl declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Tfl MCP server?
VerifyMCP ran 15 checks on Tfl, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Tfl: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.