gtfs-scorecard (ChelseaKR/gtfs-scorecard) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 9 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

gtfs-scorecard

Daily, plain-language GTFS quality scorecards for small transit agencies: the current grade, the three things to fix, and why each one matters. More than 2,600 curated feed records, mostly across the US and Canada with reviewed canaries elsewhere, rescored every day, plus a GitHub Action so an agency can catch a bad export before it ships.

→ ChelseaKR/gtfs-scorecard· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

ChelseaKR

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 8 credentials: SUBSCRIBE_SHARED_SECRET, GITHUB_TOKEN, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, SUBMIT_SHARED_SECRET, MOBILITY_FEED_API_TOKEN, GH_TOKEN, CENSUS_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configSCORECARD_BASE_URL
configALLOW_ORIGIN
🔐 secretSUBSCRIBE_SHARED_SECRET
configAWS_REGION
configSUBSCRIPTIONS_TABLE
configSES_FROMthe SES grant in infra/artifacts, and sets the repo variable.
configRATELIMIT_TABLE
configWORK_QUEUE_URL
configARTIFACTS_BUCKET
configJOBS_TABLE
configFUNCTION_NAME
configSCORECARD_ROOT
configBAKED_VALIDATOR_JAR
configRESULT_BASE_URL
configPAYMENTS_ENABLED
configGITHUB_REPO
configWORKFLOW_FILE
configWORKFLOW_REF
🔐 secretGITHUB_TOKEN
🔐 secretSTRIPE_SECRET_KEY
configSTRIPE_PRICE_IDS
configDRY_RUN
🔐 secretSTRIPE_WEBHOOK_SECRET
configBASE_BRANCH
🔐 secretSUBMIT_SHARED_SECRET
configRAW_ARCHIVE_BUCKET
🔐 secretMOBILITY_FEED_API_TOKEN
configSCORECARD_TRACEBACK
configALERTS_API_BASE
🔐 secretGH_TOKEN
🔐 secretCENSUS_API_KEY
configSCORECARD_INSTANCE_CONFIG
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

9/9 tools missing one or more hints — search_agencies (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_scorecard (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); national_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +6 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Secrets not logged

9 secret values sent to print

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/chelseakr/gtfs-scorecard)](https://m8ven.ai/mcp/chelseakr/gtfs-scorecard)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 266b6d00ae4c83980c69b6131ad5a700a188206e
code hash: b171b56426d02d3ffc5cccec2995c24537cbb946095a454ea9b9012d7529deb3
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client