← Top 100 / Full directory (15,056) Submit a server

lad-lviv-ua MCP handshake: auth_required — not a SAFE badgeMCP handshakeMCP handshakeauth_requiredauth_required

Dev Tools Remote 8 tools Ready surface Auth required

Lviv (Ukraine) public transport MCP server — live arrivals, vehicle positions, stop discovery, route shapes, and static timetables. No API key required.

Docs ↗

Claim this listing if you maintain it — self-service via owners.json or a one-time proof file.

How to connect

Same URL, five paste targets. Ready surface · Auth required. Not a safe-to-install badge. Handshake this URL

Paste into Settings → MCP or .cursor/mcp.json.

{ "mcpServers": { "vbhjckfd-lad-lviv-ua": { "url": "https://lad-lviv-ua--vbhjckfd.run.tools" } } }

Recipes using this server

No published recipes yet for this server.

Share a recipe using this server

Listing quality

Observable facts from our catalog and daily probe — not a safe-to-install badge.

Surface
Ready surface
Live handshake
Auth required MCP handshake: auth_required — not a SAFE badgeMCP handshakeMCP handshakeauth_requiredauth_required
Auth gate
Auth gate
Tools source
tools/list (live)

Observable catalog + probe facts — not a safe-to-install badge. How we verify.

Verification summary

Stored signals only. Not a safety score.

Verification grade
A (85)
Last verified
Status
Auth required
Response time
0 ms
Auth
Auth gate
Transport
http, HTTPS
Tools indexed
8
30-day uptime
100% of 23 samples over 23 days

Probe history

  • · auth_required · 0 ms
  • · auth_required · 0 ms
  • · auth_required · 0 ms
  • · auth_required · 0 ms
  • · auth_required · 0 ms

Tools

(8)
  • get_stop_realtime

    Returns 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 `search_stops` when you have a stop name, or `get_stops_around_location` when you have coordinates.

  • search_stops

    Finds 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 a stop ID for `get_stop_realtime` or `find_routes_between`. One name usually covers both sides of the street under different IDs; each is returned, and the `routes` list tells them apart. Use `get_stop

  • find_routes_between

    Lists 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 `transfer_walk_meters` (within a 300 m stop cluster, 0 when it is the same stop) to `legs[1].board_stop`, ride `legs[1]`. They are listed when there is no direct route or when they beat the best direct

  • get_route_static

    Returns 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 `include_shapes` only when you will draw the route on a map — the polylines are large and carry nothing a text answer needs. Do NOT use this for live vehicle positions — use `get_route_realtime` instead.

  • get_route_realtime

    Returns 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 at a stop and wants arrival times there. Requires a route short name (e.g. "T30", "32A") or numeric external ID.

  • get_stops_around_location

    Finds 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_stops` instead when the user gives a stop name. 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.

  • get_nearby_vehicles

    Returns 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 route and `get_stop_realtime` for arrival times at a stop. Requires decimal latitude and longitude (WGS84).

  • get_vehicle_info

    Returns 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_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.

Tool source: tools/list (live) · last probed 2026-11-21

Related servers