# tfl-ts (npm · tfl-ts)

Read-only Transport for London data: line status, arrivals, journeys, stop lookup.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- npm · `tfl-ts`: 68/100 (this document), [markdown](https://verifymcp.io/servers/ghcpuman902-tfl-ts/tfl-ts.md), [page](https://verifymcp.io/servers/ghcpuman902-tfl-ts/tfl-ts)

## Channel facts

- Registry: `npm`
- Package: `tfl-ts`
- Version: `2.15.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 21 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 779 tokens (~111/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add ghcpuman902-tfl-ts -- npx -y tfl-ts
```

### Cursor

```json
{
  "mcpServers": {
    "ghcpuman902-tfl-ts": {
      "command": "npx",
      "args": [
        "-y",
        "tfl-ts"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ghcpuman902-tfl-ts": {
      "command": "npx",
      "args": [
        "-y",
        "tfl-ts"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ghcpuman902-tfl-ts -- npx -y tfl-ts
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ghcpuman902-tfl-ts": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tfl-ts"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ghcpuman902-tfl-ts --command npx --arg -y --arg tfl-ts
```

### Hermes

```yaml
mcp_servers:
  ghcpuman902-tfl-ts:
    command: "npx"
    args: ["-y", "tfl-ts"]
```

### Netclaw

```json
{
  "McpServers": {
    "ghcpuman902-tfl-ts": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tfl-ts"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ghcpuman902-tfl-ts -t stdio -c npx -a -y tfl-ts
```

### Other

```json
{
  "mcpServers": {
    "ghcpuman902-tfl-ts": {
      "command": "npx",
      "args": [
        "-y",
        "tfl-ts"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 68)

First indexed and scored.

## MCP tools (7)

### `get_supported_modes` (~28 tokens)

List transport modes bundled with tfl-ts. Static metadata only — no TfL API call.

### `resolve_line_id` (~79 tokens)

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.

Input parameters:

- `modes` (array): Optional mode filter, for example ["tube"].
- `query` (string, required): Line name or ID, for example "Central" or "central".

### `docs` (~215 tokens)

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.

Input parameters:

- `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.

### `resolve_stop_id` (~113 tokens)

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.

Input parameters:

- `limit` (integer)
- `modes` (array): Optional mode filter, for example ["tube"] or ["bus"].
- `query` (string, required): Stop name or 5-digit bus stop code.

### `get_line_status` (~102 tokens)

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.

Input parameters:

- `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"].

### `get_arrivals` (~86 tokens)

Get compact live arrivals for one stop ID: line, towards, minutes, platform. Optional lineIds filter. Cached 15s.

Input parameters:

- `limit` (integer)
- `lineIds` (array): Optional filter, for example ["central", "victoria"].
- `stopPointId` (string, required): Canonical stop ID, for example "940GZZLUOXC".

### `plan_journey` (~86 tokens)

Plan a journey and return a compact summary (duration, fare, natural-language legs). Cached 2 minutes.

Input parameters:

- `from` (string, required): Origin stop ID, postcode, or latitude/longitude.
- `modes` (array): Optional modes, for example ["tube", "bus", "walking"].
- `to` (string, required): Destination stop ID, postcode, or latitude/longitude.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ghcpuman902-tfl-ts/tfl-ts#diagnostics

## Score history

- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 68

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/tfl-ts
- Socket report: https://socket.dev/npm/package/tfl-ts
- Repository: https://github.com/ghcpuman902/tfl-ts
- Changelog RSS feed: https://verifymcp.io/servers/ghcpuman902-tfl-ts/tfl-ts.xml
- Changelog JSON feed: https://verifymcp.io/servers/ghcpuman902-tfl-ts/tfl-ts.json
- HTML version of this page: https://verifymcp.io/servers/ghcpuman902-tfl-ts/tfl-ts