Transit MCP server

• find_transitFree

  Call with no arguments (or only `coverage`) to list the regions served and what each supports. Without a coverage, a name is searched in every region. If nothing matches, suggestions lists the closest names (not matches). Resolve a coverage, agency, route, station, stop, or a currently observed train number (where vehicle data exists); inspect an exact reference or nearby coordinates. Context ranks candidates without selecting identity. Candidates come best first (exact names and well-known place names such as SFO, then stations, then rail before bus), and each stop says what it is: stopType (station, platform or street stop), modes and the lines serving it, so you can pick the one the rider means. No general address geocoding. Use plan_trip for journeys.

• get_all_stationsFree

  Get the complete list of transit stations with coordinates for one city. Large result; prefer search_stations or get_stations_by_line when looking for specific stations.

• get_bus_positionsFree

  Get real-time positions of DC Metro buses, optionally filtered by route.

• get_bus_predictionsFree

  Get real-time bus arrival predictions for a DC Metro bus stop.

• get_bus_routesFree

  Get all DC Metro bus routes with route IDs and descriptions.

• get_bus_stopsFree

  Get DC Metro bus stops. Returns all stops or filters by lat/lon/radius.

• get_departuresFree

  Find what leaves a stop next, the first service or last service in a bounded window. Pass a stopRef from find_transit, or a stop name with its coverage: a name for one place covers all its stations in that network (otherStations lists the same place in other networks, such as the LIRR at Penn Station); a name for different places returns a question to ask, with candidates. A station covers its whole complex, e.g. every line at Times Sq-42 St; a platform ref covers that platform. Pass toStop or toStopRef for the next trips from here that stop at a destination, each with its arrival time there. Returns dated trip references for get_vehicle_status. For a journey with a change use plan_trip (with routes where needed): departures alone cannot prove a connection.

• get_elevator_incidentsFree

  Get current elevator and escalator outages. DC Metro only.

• get_incidentsFree

  Get current transit incidents and service advisories for DC Metro or NYC Subway.

• get_route_infoFree

  Get detailed information about a transit route including service patterns. NYC Subway only.

• get_service_statusFree

  Check disruptions, delays, closures, elevator and escalator outages, or revalidate a chosen itinerary without replacing it. Scope by coverage, a station name with its coverage (stop), or an agency, route, stop or dated trip reference; a station covers its complex. Aggregate scopes include canonical service in the next 24 hours. equipment lists elevator/escalator outages: accessiblePath marks the step-free route, blocksStepFree marks stations step-free plan_trip avoids, and alternativeRoute is the agency's way around. Use get_vehicle_status for an observed vehicle location.

• get_station_predictionsFree

  Get real-time train arrival predictions for a transit station. Supports DC Metro and NYC Subway. Accepts a station name or an exact station ID; if a name matches several stations, the result lists the candidates to choose from.

• get_station_transfersFree

  Get transfer connections and nearby stations from a transit station. NYC Subway only.

• get_stations_by_lineFree

  Get all stations on a specific transit line. Supports DC Metro and NYC Subway.

• get_train_positionsFree

  Get real-time positions of all trains on the DC Metro system.

• get_vehicle_statusFree

  Where observed trains are right now. Pass a route ref to list its trains, a dated trip ref (from get_departures or a plan_trip leg) to find that train, or a station (stopRef, or a name with coverage) to see trains stopped at or heading to it; a station covers its whole complex. Each train reports the stop it is at or heading to (stopStatus), the stop it last served, and its destination. Coordinates are the vehicle's own when the agency sends them (DC); otherwise a stopped train is placed at its station and a moving one has none. Never pass a bare train number: use find_transit.

• plan_tripFree

  Plan an origin-to-destination journey. Returns up to three independently validated itineraries (the fastest, then other lines); departure defaults to now. Pass the rider's place names as given: a name for one place (Penn Station, SFO) plans from or to all its stations. A name meaning different places (Broadway) returns the best trip from each, each labelled in reading and explained in notice: use the one the conversation points to, or ask the rider. The search covers every line of the coverage, buses included. When no itinerary is possible (planning unavailable, a search too large, or nothing found) it returns routeHints: lines near each end and direct lines serving both. Call again with routes (the lines you would ride, from routeHints or your own knowledge) to plan along only those lines, which works wherever schedules exist. Present only returned itineraries as confirmed. The whole journey must finish within windowSeconds (default two hours): if none is found for a long trip, retry with a larger window. Each transit leg carries a tripInstanceRef; pass it to get_vehicle_status to see where that train is now. For a wheelchair user or anyone avoiding stairs, set accessibility: "step_free": journeys then board, alight and change only at platforms step-free from the street per the agency (partial stations by direction), avoiding stations cut off by a current elevator outage; in-station changes between such platforms are taken as step-free. It refuses with ACCESSIBILITY_UNAVAILABLE when no current elevator report exists and ENDPOINT_NOT_STEP_FREE when an endpoint has no step-free platform now (get_service_status lists the outages). Never present a journey pieced together from get_departures as confirmed; check it here with routes.

• search_stationsFree

  Search for transit stations by name or code. Supports DC Metro and NYC Subway.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 921ms20/20
• Tool poisoning18 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

91/100

higher than 85% of 48,255 servers

Tools

18

the typical server has 7

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote server answers 100%

Response time

343 ms

faster than 43% of 30,031 servers

GitHub stars

5

more than 83% of 28,688 servers

Transit MCP: common questions

Is Transit MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Transit MCP safety report

How do I install Transit MCP?

It runs remotely at transitmcp.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Transit MCP need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Transit MCP maintained?

The last commit was 11 days ago (2026-10-24). The latest release is v6.1.0.

Is Transit MCP up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

How does Transit MCP compare with other MCP servers?

safety score 91/100 (higher than 85% of 48,255 servers); tools 18 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.