Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GTFS Scorecard

PYPI · GTFS-SCORECARD

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

Available components

+30 this week 65 Trust /100

Last scanned (43 minutes ago)

Scores higher than 65% of PyPI servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 16 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ChelseaKR/gtfs-scorecard). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 744 tokens (~82/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Oct 26 +15
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 13 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 12 Oct 26 35

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 19 Oct 2026 · Analysed pypi/gtfs-scorecard@1.5.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ChelseaKR/gtfs-scorecard
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ChelseaKR/gtfs-scorecard/.github/workflows/pypi-publish.yml@refs/tags/v1.5.1
Rekor log index 3213507244
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:4aeeedd704344831adfb4b3bc2fa7b30357ac8a2477d358279b7dc4e1c3b6f02

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 16 packages
Packages resolved 16
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~744 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
coverage_for ~92

Covered-set totals for one ISO country, or one subdivision inside it. A place this scorecard does not track is reported as not covered rather than as zero feeds: absence of coverage is not absence of transit data.

NameTypeReqDescription
countrystringyesISO 3166-1 alpha-2 country code, e.g. US
subdivisionstring–Optional ISO 3166-2 code or subdivision name

No output schema declared.

No examples provided.

coverage_stats ~27

Coverage-wide quality totals and portable country/subdivision rollups over the feeds this scorecard tracks.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

explain_finding ~108

The fix recipe for one validator or scorecard notice code, its authoritative rule link, and, when a producing tool is named, that tool's fix path. A code with no written recipe returns the rule link alone and says so; nothing is described beyond what is written.

NameTypeReqDescription
codestringyesNotice code, e.g. 'expired_calendar'
toolstring–Optional producing-tool key: trillium, gtfs_builder, remix, passio, repo, or archive

No output schema declared.

No examples provided.

get_evidence_packet ~61

The deterministic vendor remediation packet for one agency's latest scorecard: the producer contract, the work items with their acceptance tests, and the feed identity they were measured against.

NameTypeReqDescription
agency_idstringyesAgency slug, e.g. 'unitrans'

No output schema declared.

No examples provided.

get_history ~138

One feed's dated grade and score history, with every measurement-contract boundary marked. A point marked comparable_with_previous: false was scored under a different rubric, scoring profile, validator, reader archive profile, or measured-category set, and the difference across it is not a change in the feed. Also reports findings that appeared or cleared between the two most recent snapshots, but only when those two are comparable.

NameTypeReqDescription
agency_idstringyesAgency slug, e.g. 'unitrans'
limitinteger–Max dated points (default and ceiling 120)
sincestring–Earliest snapshot date to include, YYYY-MM-DD

No output schema declared.

No examples provided.

get_rollup ~64

One program rollup: the cohort's shared fixes, grade distribution, and the members needing attention. Shared fixes describe work many feeds share; they are not a ranking of agencies.

NameTypeReqDescription
rollup_idstringyesRollup id, e.g. 'california'

No output schema declared.

No examples provided.

get_scorecard ~61

An agency's latest scorecard: overall grade, category scores and plain-language summaries, every finding with its fix and effort, top fixes, and NTD GTFS readiness.

NameTypeReqDescription
agency_idstringyesAgency slug, e.g. 'unitrans'

No output schema declared.

No examples provided.

national_stats ~42

Legacy United States policy view: NTD GTFS readiness nationally and by state, plus the backwards-compatible covered-corpus stats member. Prefer coverage_stats for geography-neutral totals.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_agencies ~151

Search tracked transit agencies by name, id, ISO country, ISO subdivision or subdivision name, legacy state, or letter grade. Returns portable location, grade, score, expiry, and applicable readiness fields.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country code, e.g. CA
gradestring–Letter grade A-F
limitinteger–Max results (default 20)
querystring–Name fragment or exact agency id
statestring–Legacy state/province-name filter; prefer subdivision
subdivisionstring–ISO 3166-2 code or subdivision name, e.g. CA-ON or Ontario

No output schema declared.

No examples provided.

Install

How do I install the GTFS Scorecard MCP server?

GTFS Scorecard runs locally as a PyPI package, launched with uvx gtfs-scorecard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · gtfs-scorecard

# add to Claude Code
claude mcp add chelseakr-gtfs-scorecard -- uvx gtfs-scorecard
Common questions

What is the GTFS Scorecard MCP server?

GTFS Scorecard is an MCP server listed in the public MCP registry as io.github.ChelseaKR/gtfs-scorecard. Read-only GTFS transit feed scorecards: grades, plain-language fixes, and history. This page covers its PyPI package (gtfs-scorecard).

Is the GTFS Scorecard MCP server safe to use?

GTFS Scorecard scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 19 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the GTFS Scorecard MCP server expose?

GTFS Scorecard exposes 9 tools: search_agencies, get_scorecard, national_stats, coverage_stats, get_history, and 4 more. Their descriptions and schemas cost roughly 744 tokens of context every time the server is loaded.

Is the GTFS Scorecard MCP server still maintained?

GTFS Scorecard is still listed as active in the MCP registry. We last reached this channel on 19 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the GTFS Scorecard MCP server under?

GTFS Scorecard declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.