tfl-ts
NPM · TFL-TS
Read-only Transport for London data: line status, arrivals, journeys, stop lookup.
Available components
Last scanned (16 hours ago)
Scores higher than 38% 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
- 0 of 21 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 779 tokens (~111/item across 7 items; 7 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 Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
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.
- 16 Oct 26 68
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 18 Oct 2026 · Analysed npm/tfl-ts@2.15.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 21 packages
| Packages resolved | 21 |
|---|---|
| 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 →
docs ~215
Read tfl-ts bundled agent docs offline (same catalogue as `tfl docs`). No TfL API call, no credentials. Prefer list → find → read; use grep to locate symbols across docs. Large files are paginated by line.
| Name | Type | Req | Description |
|---|---|---|---|
| caseInsensitive | boolean | – | For operation=grep only. |
| id | string | – | Doc id or path for operation=read (e.g. "CLAUDE.md", "docs/mcp.md"). |
| limit | integer | – | For read: max lines (default 80). For grep: max matches (default 50). |
| offset | integer | – | For read: 0-based line offset. For grep: 0-based match offset. |
| operation | string | – | list catalogue | read one doc | find by id/title/audience/body | grep content |
| pattern | string | – | For operation=grep: literal substring (not regex), same as CLI. |
| query | string | – | For operation=find: keyword against id, title, audience, or body. |
No output schema declared.
No examples provided.
get_arrivals ~86
Get compact live arrivals for one stop ID: line, towards, minutes, platform. Optional lineIds filter. Cached 15s.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| lineIds | array | – | Optional filter, for example ["central", "victoria"]. |
| stopPointId | string | yes | Canonical stop ID, for example "940GZZLUOXC". |
No output schema declared.
No examples provided.
get_line_status ~102
Get compact live line status (id, name, status, optional reason). Provide lineIds or modes (at least one). Set issuesOnly=true to hide Good Service lines. Cached 60s.
| Name | Type | Req | Description |
|---|---|---|---|
| issuesOnly | boolean | – | If true, return only lines that are not Good Service. |
| lineIds | array | – | Canonical lowercase line IDs, for example ["central"]. |
| modes | array | – | Transport modes, for example ["tube"]. |
No output schema declared.
No examples provided.
get_supported_modes ~28
List transport modes bundled with tfl-ts. Static metadata only — no TfL API call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_journey ~86
Plan a journey and return a compact summary (duration, fare, natural-language legs). Cached 2 minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Origin stop ID, postcode, or latitude/longitude. |
| modes | array | – | Optional modes, for example ["tube", "bus", "walking"]. |
| to | string | yes | Destination stop ID, postcode, or latitude/longitude. |
No output schema declared.
No examples provided.
resolve_line_id ~79
Resolve a line name to canonical lowercase TfL line IDs. Exact matches rank first. Static metadata only — no TfL API call. Prefer this before get_line_status.
| Name | Type | Req | Description |
|---|---|---|---|
| modes | array | – | Optional mode filter, for example ["tube"]. |
| query | string | yes | Line name or ID, for example "Central" or "central". |
No output schema declared.
No examples provided.
resolve_stop_id ~113
Search TfL for a stop name or NaPTAN / SMS code and return compact stop matches. Cached 24h. For modes: ["bus"] this expands 490G… hubs so a street name returns boarding stops, not two raw search hits. Use the returned id with get_arrivals.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| modes | array | – | Optional mode filter, for example ["tube"] or ["bus"]. |
| query | string | yes | Stop name or 5-digit bus stop code. |
No output schema declared.
No examples provided.
How do I install the tfl-ts MCP server?
tfl-ts runs locally as an npm package, launched with npx -y tfl-ts. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tfl-ts
claude mcp add ghcpuman902-tfl-ts -- npx -y tfl-ts
What is the tfl-ts MCP server?
tfl-ts is an MCP server listed in the public MCP registry as io.github.ghcpuman902/tfl-ts. Read-only Transport for London data: line status, arrivals, journeys, stop lookup. This page covers its npm package (tfl-ts).
Is the tfl-ts MCP server safe to use?
tfl-ts scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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-ts MCP server expose?
tfl-ts exposes 7 tools: get_supported_modes, resolve_line_id, docs, resolve_stop_id, get_line_status, and 2 more. Their descriptions and schemas cost roughly 709 tokens of context every time the server is loaded.
Is the tfl-ts MCP server still maintained?
tfl-ts is still listed as active in the MCP registry. We last reached this channel on 18 October 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-ts MCP server under?
tfl-ts declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.