mcp server
Live Times Transit
Read-only public transit departures, stop search, and city coverage for bus and train users.
Description as published by the maintainer. Source
- version 0.1.0
- active
- retrieval
active — Registry entry last updated 2026-07-28. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
5 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
find_stops(lat, lon, near, query, locale, country_code)- Resolve a named place with Apple Maps when needed, then find nearby stops or stations so callers can pass a stop_id to get_departures. For ambiguous names, include near or country_code. If the user asks for a train, select a RAIL result. Required: query.
get_city_summary(locale, city_id)- Return Live Bus Times and Live Train Times coverage metadata and canonical links for a supported city. Required: city_id.
get_departures(locale, stop_id, filter_by, filter_value)- Return a Live Times departure board for a known canonical stop ID. Optionally filter by route pattern or by up to 5 destinations. Required: stop_id.
plan_journey(mode, locale, origin, arrive_by, depart_at, destination, num_results, origin_near, origin_place_id, destination_near, origin_country_code, destination_place_id, destination_country_code)- Return compact step-by-step public transit directions between named places. Resolves names with Apple Maps and returns clarification candidates rather than guessing when a place is ambiguous. Required: origin, destination.
search_places(near, limit, query, locale, country_code)- Return up to 5 Apple Maps place candidates with Momego place IDs. Use this proactively when an origin or destination name is ambiguous, then pass the selected place ID to plan_journey. Required: query.
Last successful function declaration observed on . Source: https://livebustimes.org/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://livebustimes.org/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-28 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-28 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 5 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | livebustimes.org | |
| mcp endpoint status | ok | The server listed 5 functions when asked. | as of probe | livebustimes.org |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json