Skip to content
External endpointresponds

onebusaway-mcp-server

Real-time transit stops, routes, arrivals, vehicle positions, and schedules via OneBusAway APIs.

Endpoint URL
https://onebusaway.caseyjhand.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:06 AM UTC
Check
MCP initialize · 8s limit
Latency
417 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.cyanheads/onebusaway-mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
onebusaway-mcp-server
Version
0.1.13
Capability keys
logging, resources, tools, prompts
Tool names
onebusaway_list_agencies, onebusaway_find_stops, onebusaway_find_routes, onebusaway_search_stops, onebusaway_search_routes, onebusaway_get_stop, onebusaway_get_route, onebusaway_list_routes_for_agency, onebusaway_get_arrivals, onebusaway_get_alert, onebusaway_get_trip, onebusaway_get_block, onebusaway_get_vehicles, onebusaway_get_schedule_for_stop, onebusaway_get_schedule_for_route
Instructions excerpt

OneBusAway MCP server — real-time transit data for Puget Sound (King County Metro, Sound Transit, Pierce Transit, Community Transit, and more) and other OneBusAway instances. - Stop IDs use agency-prefixed format: {agencyId}_{localId} (e.g. "1_75403" for Metro Transit stop 75403) - To get arrivals: use onebusaway_find_stops or onebusaway_search_stops to resolve a location/name to a stopId, then call onebusaway_get_arrivals - For "where is the 44?": use onebusaway_search_routes to get routeId, then onebusaway_get_vehicles - For service alert details: get a situationId from onebusaway_get_arrivals (situations[].id), then call onebusaway_get_alert - For a vehicle's full day schedule: get a tripId from onebusaway_get_arrivals, call onebusaway_get_trip to find the blockId, then call onebusaway_get_block - OneBusAway does not include trip planning — direct users to Google Maps or Transit app for routing

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 232ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 328ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 257ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 417ms
Back to MCP directory