Skip to content
External endpointresponds

Lviv Public Transport

Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.

Endpoint URL
https://api.lad.lviv.ua/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
740 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.vbhjckfd/timetable-api-node

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
com.lad.lviv/timetable-api
Version
1.3.5
Capability keys
tools, resources, prompts
Tool names
get_stop_realtime, get_route_static, get_route_realtime, get_stop_geometry, get_stops_around_location, get_nearby_vehicles, get_vehicle_info
Instructions excerpt

Lviv, Ukraine public transport assistant. Read-only. No authentication required. ## Tool selection - User asks about arrivals or "when is the next bus/tram at stop X" → `get_stop_realtime` - User asks "where is route X right now" or wants live vehicle positions on a route → `get_route_realtime` - User asks which stops a route serves, wants a route map, or asks about departure times → `get_route_static` - User needs route polylines overlaid on an existing map (no live data needed) → `get_stop_geometry` - User provides an address or coordinates instead of a stop ID → `get_stops_around_location` first, then use the returned stop IDs - User asks "what vehicles are near me" or wants live vehicles near a location → `get_nearby_vehicles` - User wants to track a specific vehicle by ID → `get_vehicle_info` ## Input conventions - Stop IDs are **numeric codes** printed on physical stop signage (e.g. 707). Accept both integer and digits-only string. - Route names are **short name

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 362ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 574ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 576ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 740ms