GTFS Scorecard MCP server

GTFS Scorecard

Daily, plain-language GTFS quality scorecards for small transit agencies:

see the current grade, the three things to fix, and why each one matters.

GTFS Scorecard is a daily data-quality service for small transit agencies and the program staff, maintainers, and vendors who support them. It publishes dated grades, prioritized fixes, history, program views, practitioner tools, and open data. It does not implement a competing GTFS validator. Correctness findings come from MobilityData's canonical validator.

Quickstart

Requires Python 3.12+, uv, and Java 17+ (the validator jar is downloaded automatically on first run).

cd pipeline
uv sync
uv run scorecard run --all

This fetches today's snapshot of every current configured feed, validates and scores it, and writes artifacts to data/artifacts//.json plus a latest.json and a cross-agency index.json. Retired aliases are excluded from the batch; an explicit historical rescore writes a dated record without recreating mutable current files. Re-running a day is idempotent. Checks (from the repo root; mirrors the CI gate):

make verify

Run the web app locally

The frontend reads the JSON artifacts over HTTP. Serve the repo root and open the page through http://, not by double-clicking the file:

cd ..            # repo root, so data/artifacts/ is reachable
python3 -m http.server 8000
# then open http://localhost:8000/web/index.html

Opening web/index.html as a file:// URL leaves the page stuck on "Loading scorecards…": browsers block ES module loading and fetch over file://, so the app never runs. Any static server works; the only requirement is that data/artifacts/ sits one level above web/, which the ../data/artifacts fallback in web/src/app.js expects.

Where it fits

GTFS Scorecard is the evidence and triage layer:

Transitland help identify public feeds and their sources or versions.

1. Mobility Database and

supplies canonical specification findings.

1. The MobilityData GTFS validator

feed through its existing workflow.

1. An agency, vendor, editor, or support program changes and publishes the

action to the intended feed, run a comparable recheck, and preserve the result.

1. A 90-day GTFS Scorecard pilot is testing the final handoff: link an accepted

The California GTFS Quality Dashboard inspired the project's daily scorecard and support-program framing. GTFS Scorecard is independent and is not an official compliance determination.

Shortened. The full README is on GitHub.