io.github.oneill9/tfl-mcp-server vs Tfl
io.github.oneill9/tfl-mcp-server is an MCP server published by oneill9. Marketplaces we read that list it: 1 (Official MCP Registry). Tfl is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.oneill9/tfl-mcp-server |  Tfl |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.2 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.oneill9/tfl-mcp-server | Tfl |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | On your machine (ghcr.io/oneill9/tfl-mcp-server:1.5.2) | Remote server (gateway.pipeworx.io/tfl/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/oneill9/tfl-mcp-server | github.com/pipeworx-io/mcp-tfl |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 21 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.oneill9/tfl-mcp-server
Community-built server providing real-time London transport data via the TfL Unified API
Tfl
Transport for London (TfL) Unified API MCP — keyless.
How to run each
io.github.oneill9/tfl-mcp-server As a local MCP server: Docker image
claude mcp add --env "TFL_APP_KEY=<YOUR_TFL_APP_KEY>" --transport stdio tfl-mcp-server -- docker run -i --rm -e TFL_APP_KEY ghcr.io/oneill9/tfl-mcp-server:1.5.2Requires: TFL_APP_KEY (secret)
Tfl As a remote MCP server
claude mcp add --transport http tfl https://gateway.pipeworx.io/tfl/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Tfl has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.oneill9/tfl-mcp-server asks for
TFL_APP_KEY (secret)
Only Tfl asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.oneill9/tfl-mcp-server · What it can do: Tfl · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.