All servers · Maps, location & weather
Lviv Public Transport
io.github.vbhjckfd/timetable-api-node · v1.8.0
New (7 days)Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | completions, prompts, resources, tools |
| Tool definitions | 9 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.
Connect
streamable-http · https://api.lad.lviv.ua/mcp
claude mcp add --transport http timetable-api-node https://api.lad.lviv.ua/mcp{
"mcpServers": {
"timetable-api-node": {
"url": "https://api.lad.lviv.ua/mcp"
}
}
}Tools as reported by the server
get_stop_realtimeReturns live arrivals at a stop: route, destination, vehicle type, minutes until arrival, and each vehicle's position. Use this as the **default tool** when the user asks about arrivals, departures, or the next bus/tram at a specific stop. Requires a numeric stop ID (shown on stop signage); use `seasearch_stopsFinds stops by name (Ukrainian or English transliteration, case-insensitive, partial match) and returns each stop's numeric ID, coordinates, and the routes serving it. Use this as the **first step** when the user names a stop or landmark stop (e.g. "Опера", "Rynok", "Головний вокзал") and you need afind_routes_betweenLists the routes from one place to another: which stop to board, where to get off, the direction's destination, stops in between, and the walk at each end — best first, walking counted. `options` are direct routes. `transfer_options` have exactly one interchange (never more): ride `legs[0]`, walk `tget_route_staticReturns static route data: name, long name, vehicle type, colour, the ordered stop list for both directions, and the timetable of departures from the first stop (workday, Saturday and Sunday). Use when the user asks which stops a route serves, where it goes, or its scheduled departure times. Set `inget_route_realtimeReturns every vehicle currently running on a route: position, the destination it is heading to, and its next stop with estimated arrival. Use when the user asks "where is my tram/bus right now?", how many vehicles are running, or how far the next one is. Prefer `get_stop_realtime` when the user is aget_disruptionsLists closures, detours and moved stops the city announced that are in force today: affected routes, the streets a detour uses, routes to take instead of a suspended one, reason, dates and source. The GTFS stop lists and timetables do not reflect any of this. Use when the user asks about road works,get_stops_around_locationFinds stops near a geographic point, returning each stop's numeric ID, name, coordinates, walking distance, and the routes serving it. Use this as the **first step** when the user gives an address or coordinates and you need stop IDs for `get_stop_realtime` or `find_routes_between`. Use `search_stopget_nearby_vehiclesReturns live vehicles near a point, nearest first, each with its route, destination, and distance. Use when the user asks "what transport is near me right now?" or wants a live map around a location. Narrow with `route` when the user cares about one line; prefer `get_route_realtime` for a whole routget_vehicle_infoReturns details for one vehicle by ID: position, route, destination, license plate, and its upcoming stops with names and estimated arrival times. Use when the user wants to follow a particular vehicle, e.g. "where does this tram go next?" or "when will it reach X?". Vehicle IDs come from `get_route
Tool changes
- 2026-10-24: get_stop_realtime, search_stops, find_routes_between, get_route_static, get_route_realtime, get_disruptions, get_stops_around_location, get_nearby_vehicles, get_vehicle_info
- 2026-10-16: get_stop_realtime, search_stops, find_routes_between, get_route_static, get_route_realtime, get_stops_around_location, get_nearby_vehicles, get_vehicle_info
Repository · Website · JSON · Text for agents · Registry updated 2026-10-23