{"name":"io.github.vbhjckfd/timetable-api-node","slug":"vbhjckfd-timetable-api-node","title":"Lviv Public Transport","description":"Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.","url":"https://mcp.market/server/vbhjckfd-timetable-api-node","rating":null,"grade":"A","score":91,"certified":false,"status":"active","category":"other","tags":[],"presence":{"score":29,"stars":3,"forks":3,"downloads_week":null,"last_push_at":"2026-09-18T18:59:57.000Z","license":"WTFPL"},"claimed":false,"transport":"remote","callable_via_gateway":true,"default_price_micros":0,"repository":"https://github.com/vbhjckfd/timetable-api-node","website":"https://lad.lviv.ua","version":"1.4.1","remotes":[{"type":"streamable-http","url":"https://api.lad.lviv.ua/mcp"}],"packages":[],"tools":[{"name":"get_nearby_vehicles","description":"Returns live positions for all transit vehicles within 1 km of given coordinates. Use when the user asks 'what transport is near me?' or wants a live map of all vehicles around a location without knowing the route. Prefer `get_route_realtime` when a specific route is already known. Requires decimal latitude and longitude (WGS84); use `get_stops_around_location` first if you only have a stop name.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"latitude":{"type":"number","minimum":-90,"maximum":90,"description":"Decimal latitude of the centre point, WGS84 (e.g. 49.842)."},"longitude":{"type":"number","minimum":-180,"maximum":180,"description":"Decimal longitude of the centre point, WGS84 (e.g. 24.031)."}},"required":["latitude","longitude"],"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"get_route_realtime","description":"Returns live positions for all vehicles currently running on a route, optimised for map rendering. Use when the user asks \"where is my tram/bus right now?\" or wants to see all active vehicles on a specific route on a map. Prefer `get_stop_realtime` when the user is at a stop and wants to know arrival times rather than vehicle positions. Prefer `get_route_static` when only the route shape or stop list is needed without live data. Requires a route short name (e.g. \"T30\", \"32A\") or numeric external ID.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"route_name":{"type":"string","minLength":1,"description":"Route short name (e.g. \"T30\", \"32A\") or numeric external ID."}},"required":["route_name"],"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"get_route_static","description":"Returns static route metadata: short and long name, vehicle type, brand colour, ordered stop lists for both directions, and route polylines (shapes) for map rendering. Use when the user asks which stops a route serves, what a route looks like on a map, or what the scheduled departure times are (workday and weekend schedules are included in each stop's `schedule` field). Do NOT use this when live vehicle positions are needed — use `get_route_realtime` instead. Requires a route short name (e.g. \"T30\", \"32A\") or numeric external ID; call `get_stops_around_location` first if you only know a location and need to discover which routes serve it.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"route_name":{"type":"string","minLength":1,"description":"Route short name (e.g. \"T30\", \"32A\") or numeric external ID."}},"required":["route_name"],"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"get_stop_geometry","description":"Returns static map context for a stop: its marker and polylines for every route that serves it. No live data is fetched. Use this when you need to enrich an existing map with route shapes (e.g. overlay polylines alongside a `get_stop_realtime` map block) or when the user asks to visualise which routes pass a stop without needing live arrivals. Do NOT use this when live arrival times or vehicle positions are needed — use `get_stop_realtime` instead. Requires a numeric stop ID; call `get_stops_around_location` first if you only have coordinates.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"stop_id":{"type":"integer","exclusiveMinimum":0,"maximum":9007199254740991,"description":"Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string."}},"required":["stop_id"],"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"get_stop_realtime","description":"Returns live arrivals and vehicle positions for a stop, producing both a map UI block and a structured arrival list. Use this as the **default tool** when the user asks about arrivals, departures, or vehicles at a specific stop. Prefer `get_stop_geometry` when only static route polylines are needed and live data is irrelevant. Requires a numeric stop ID (shown on stop signage); use `get_stops_around_location` first if you only have an address or coordinates.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"stop_id":{"type":"integer","exclusiveMinimum":0,"maximum":9007199254740991,"description":"Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string."}},"required":["stop_id"],"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"get_stops_around_location","description":"Discovers transit stops near a geographic point, returning each stop's numeric code, name, coordinates, and walking distance. Also emits a map UI block with multiple markers for map-capable clients (e.g. ChatGPT). Use this as the **first step** whenever the user provides an address, place name, or coordinates and you need stop IDs before calling `get_stop_realtime` or `get_stop_geometry`. Do NOT use this to fetch arrivals or live vehicle data — it returns stop metadata only. Default radius is 1 000 m; narrow it (e.g. 300 m) for dense urban areas or widen it (up to 3 000 m) for rural locations.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"latitude":{"type":"number","minimum":-90,"maximum":90,"description":"Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv)."},"longitude":{"type":"number","minimum":-180,"maximum":180,"description":"Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv)."},"radius_meters":{"description":"Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas.","type":"integer","minimum":50,"maximum":3000}},"required":["latitude","longitude"],"$schema":"http://json-schema.org/draft-07/schema#"}},{"name":"get_vehicle_info","description":"Returns full details for a specific transit vehicle by its ID: current position, bearing, route, license plate, direction, and upcoming stop arrivals. Use when the user wants to track a particular vehicle (e.g. after seeing it on a `get_route_realtime` map). Vehicle IDs come from `get_route_realtime`, `get_nearby_vehicles`, or `get_stop_realtime` results. Do NOT use this to get all vehicles on a route — use `get_route_realtime` instead.","write_action":false,"price_micros":0,"input_schema":{"type":"object","properties":{"vehicle_id":{"type":"string","minLength":1,"description":"Vehicle ID as returned by get_route_realtime, get_nearby_vehicles, or get_stop_realtime."}},"required":["vehicle_id"],"$schema":"http://json-schema.org/draft-07/schema#"}}],"scan":{"score":91,"grade":"A","scanned_at":"2026-09-19T04:44:31.293Z","report":{"scannerVersion":"0.1.3","scannedAt":"2026-09-19T04:44:31.211Z","components":{"code":{"score":-1,"max":25,"notes":["remote-only server, no package to scan"]},"reliability":{"score":20,"max":20,"notes":["remote reachable in 1006ms"]},"poisoning":{"score":15,"max":15,"notes":["7 tool descriptions checked"]},"auth":{"score":10,"max":15,"notes":["open endpoint, read-only tools"]},"maintenance":{"score":15,"max":15,"notes":["last push 0 days ago"]},"identity":{"score":8,"max":10,"notes":["registry namespace matches repository owner","GitHub account older than a year"]}},"findings":[],"inputs":{"probes":[{"url":"https://api.lad.lviv.ua/mcp","reachable":true,"authRequired":false,"latencyMs":1006,"serverInfo":{"name":"com.lad.lviv/timetable-api","version":"1.4.1"}}],"packages":[],"repo":{"found":true,"owner":"vbhjckfd","repo":"timetable-api-node","archived":false,"pushedAt":"2026-09-18T18:59:57Z","stars":3,"forks":3,"openIssues":1,"ownerType":"User","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/2711729?v=4","ownerCreatedAt":"2012-11-02T22:49:18Z","license":"WTFPL"},"icon":{"url":"https://raw.githubusercontent.com/vbhjckfd/timetable-api-node/master/mcp/mcp-icon.svg","source":"registry"},"presence":{"stars":3,"forks":3,"downloadsWeek":null,"license":"WTFPL","lastPushAt":"2026-09-18T18:59:57.000Z","score":29}}}},"grade_history":[],"reviews":[]}