GTFS Scorecard

io.github.ChelseaKRPublished by GitHub account ChelseaKRv1.5.1Updated Oct 24, 2026

Read-only GTFS transit feed scorecards: grades, plain-language fixes, and history.

The publisher's own server: Scorecard

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Read-only MCP server that lets an assistant look up published GTFS transit feed scorecards, grades, fixes and grade history.

What you can do
  • Search tracked transit agencies and find their scorecards
  • Get a feed's scorecard with its grade, category scores and top plain-language fixes
  • Read a feed's grade history over time
  • Explain a specific validator finding in plain language
When to use it
Useful when you work with public transit data and want an assistant to check how a GTFS Schedule feed is graded, what to fix, or how a feed's grade has changed, without running the validator yourself.
Requirements
Runs locally over stdio, started with uvx from the PyPI package gtfs-scorecard (Python tooling required). No API key or authentication. Optional SCORECARD_BASE_URL environment variable points it at a fork or local preview instead of the public site.
Before you install
The MCP server is read-only and has no write surface, but it reads scorecards from the public gtfsscorecard.org site, so queries go to that third party. The separate command-line tool downloads and scores a feed zip with the MobilityData validator, which needs Java 17 or newer on PATH.

Installation

In SourceWeft

  1. Open GTFS Scorecard 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

gtfs-scorecard

The scoring pipeline, command-line tool, and read-only MCP server behind GTFS Scorecard, which grades public GTFS Schedule feeds and turns validator notices into plain-language fixes.

What it does

  • scorecard try <feed-url> scores one GTFS Schedule zip with the MobilityData validator (Java 17 or newer must be on PATH) and prints the grade, the category scores, and the top fixes.
  • scorecard-mcp is a read-only Model Context Protocol server over stdio. Its tools read the published scorecards on gtfsscorecard.org: search tracked agencies, get a scorecard and its fixes, read a feed's grade history, and explain a validator finding. It needs no key and has no write surface.
  • gtfs-scorecard is the same MCP server under the distribution's name, so uvx gtfs-scorecard starts it.

The Python import package is scorecard_pipeline. The distribution was named scorecard-pipeline until 1.5.1; PyPI refused that name as too similar to an existing project, and nothing was uploaded under it.

Install

uvx gtfs-scorecarduvx --from gtfs-scorecard scorecard try https://example.org/gtfs.zippip install gtfs-scorecard

The first starts the MCP server. The second runs the command-line tool, which has its own name, so uvx needs --from to find the package that provides it. Check https://pypi.org/project/gtfs-scorecard/ for the versions that exist. To run code that is not released yet, install from the repository:

uvx --from "git+https://github.com/ChelseaKR/gtfs-scorecard#subdirectory=pipeline" scorecard-mcp

Connect an assistant

An MCP client config that starts the server from PyPI:

{  "mcpServers": {    "gtfs-scorecard": {      "command": "uvx",      "args": ["gtfs-scorecard"]    }  }}

Set SCORECARD_BASE_URL to point it at a fork or a local preview.

More

Apache-2.0.

Source: pipeline/README.md at commit ec63a6e

Tools

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

Version history

1
  1. v1.5.1LatestOct 11, 2026

Score

50% 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
  • License10 pts

Other Scorecard integrations