Skip to content
Back to the index

tfl

pipeworx.ioInfrastructure🇬🇧

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Tfl is a Pipeworx-hosted MCP server exposing tools for London transport data. It supports line status, stop searches, real-time arrivals, journey planning, and Santander Cycles availability for developers and AI agents.

Inferred · not functionally tested

WebAPICloud-managed
tfl preview
Visit pipeworx.io

Overview

6 features

Purpose: Finding real-time London transport information and planning journeys through a machine-readable service.

Inferred · not functionally tested

Audience: developers building transport-aware applications and AI agents

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

In the API design, testing & docs space, tfl takes a focused approach. Inferred · not functionally tested: It focuses on finding real-time London transport information and planning journeys through a machine-readable service. Inferred · not functionally tested: tfl is a B2B product aimed at developers building transport-aware applications and AI agents. Basis unknown · not verified: It runs on the web and API.

Behind tfl is Pipeworx, based in the United Kingdom. Inferred · not functionally tested: Among its 6 catalogued features are line status, stop search, and live arrivals. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Line status
  • Stop search
  • Live arrivals
  • Journey planning
  • Cycle availability
  • JSON-RPC endpoint

Topics: Inferred · not functionally tested

Tags
london-transporttfl-datamcp-serverjourney-planning

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 03:02 UTC
    Tfl seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about tfl

What does tfl do?
Inferred · not functionally tested: Tfl focuses on finding real-time London transport information and planning journeys through a machine-readable service. It is catalogued under API design, testing & docs on PulseGate.
Who is tfl for?
Inferred · not functionally tested: tfl is a B2B product built for developers building transport-aware applications and AI agents.
What platforms does tfl run on?
Basis unknown · not verified: tfl runs on the web and API.
Is tfl still maintained?
Unverified. tfl has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What projects are similar to tfl?
Similar projects tracked by PulseGate include mbta, transport-nsw, and swisstransport.mbtatransport-nswswisstransport
Who develops tfl?
tfl is developed by Pipeworx, based in the United Kingdom.
Does tfl have an API or integrations?
Inferred · not functionally tested: Yes — tfl exposes an MCP server.

Similar projects

Closest matches by what these projects do

Submit to the index
Apps, agents and models — free, no signup.