Tfl Status Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

London transport line status from Transport for London. No key required.

The publisher's own server: status.live national parks

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant look up current status of London transport lines via Transport for London, with no API key required.

What you can do
This local MCP server exposes Transport for London line status data to an assistant. Based on the description, it reports the current status of London transport lines, so an assistant can answer questions about service conditions on the network. No tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Useful when you want an assistant to check or discuss current London transport line status, for example while planning a journey or monitoring disruptions. It is a narrow, single-purpose server, so it is worth adding only if London transport status is relevant to your work.
Requirements
Runs as a local process over stdio, installed from the npm package tfl-status-mcp, so Node.js and npm are needed. No authentication, environment variables, or headers are declared, and the description states no key is required. Network access to Transport for London is implied by the purpose.
Before you install
The manifest declares no credentials, environment variables, or headers, and the description says no key is required. No write, send, or delete actions are described. Because no tools are listed, review the actual tool behavior after installation before relying on it.

Installation

In SourceWeft

  1. Open Tfl Status Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Status integrations