Mbta MCP Server

mbta-mcp PyPI v1.1.1

Published by cubismod — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for MBTA V3 API

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 32

Each tool and what it can reach — statically extracted from the published source.

  • mbta_get_alertsno sensitive capability
  • mbta_get_amtrak_health_statusno sensitive capability
  • mbta_get_amtrak_trainsno sensitive capability
  • mbta_get_amtrak_trains_geojsonno sensitive capability
  • mbta_get_chained_track_predictionsno sensitive capability
  • mbta_get_external_alertsno sensitive capability
  • mbta_get_facilitiesno sensitive capability
  • mbta_get_historical_assignmentsno sensitive capability
  • mbta_get_live_facilitiesno sensitive capability
  • mbta_get_nearby_stopsno sensitive capability
Show 22 more tools ↓
  • mbta_get_prediction_statsno sensitive capability
  • mbta_get_predictionsno sensitive capability
  • mbta_get_predictions_for_stopno sensitive capability
  • mbta_get_route_alternativesno sensitive capability
  • mbta_get_routesno sensitive capability
  • mbta_get_schedulesno sensitive capability
  • mbta_get_schedules_by_timeno sensitive capability
  • mbta_get_servicesno sensitive capability
  • mbta_get_shapesno sensitive capability
  • mbta_get_stopsno sensitive capability
  • mbta_get_track_predictionno sensitive capability
  • mbta_get_tripsno sensitive capability
  • mbta_get_vehicle_positionsno sensitive capability
  • mbta_get_vehiclesno sensitive capability
  • mbta_list_all_alertsno sensitive capability
  • mbta_list_all_facilitiesno sensitive capability
  • mbta_list_all_linesno sensitive capability
  • mbta_list_all_routesno sensitive capability
  • mbta_list_all_servicesno sensitive capability
  • mbta_list_all_stopsno sensitive capability
  • mbta_plan_tripno sensitive capability
  • mbta_search_stopsno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.1 latest A 99/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mbta-mcp/badge.svg)](https://mcptrustchecker.com/registry/mbta-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/mbta-mcp"><img src="https://mcptrustchecker.com/registry/mbta-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mbta-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mbta-mcp --online --registry pypi

Use the free API → How scoring works

More in Lifestyle & Local