Skip to content

Lviv Public Transport MCP server

io.github.vbhjckfd/timetable-api-nodevbhjckfdstreamable-httpv1.8.22Scanned

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

9 tools: 9 only read.

Tools: 0 delete, 0 irreversible, 0 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 9
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Lviv Public Transport MCP server can do

The Lviv Public Transport MCP server is published by the GitHub account vbhjckfd. It has 9 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

9 tools bring in text other people can write (get_stop_realtime, search_stops, find_routes_between and 6 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.8.22.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Only reads 9Show 9 read-only tools
  • find_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 cou…Reads text others writeNo findings

    Why it is in this group

    • The name "find_routes_between" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Each end is a stop ID (`from_stop_id`) or coordinates (`from_lat` + `from_lng`), e.g. an address the user gave; a point covers every stop within a 600 m walk of it. `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 one. Every option carries `schedule`: by the timetable, when to leave, when each leg boards and alights, when you arrive, and `total_minutes` door to door. Plan for now by default, or pass `depart_at` or `arrive_by` ("HH:MM" Lviv time today, or ISO 8601). When planning for now, options also carry `next_departures`: the live next departures of the first leg from its boarding stop, so no separate `get_stop_realtime` call is needed. `map_stops` holds the best trip's stops in riding order, each with a `role` (board, transfer — or transfer_alight + transfer_board when the interchange is a walk — and alight). Use when the user asks how to get from A to B, which bus/tram goes from one place to another, how long it takes, or when to leave to be somewhere on time. A stop end covers every stop within a 300 m walk of it, since a line's two directions often stop on opposite sides of a street under different names; `board_stop` says where to actually wait. Routes the city has suspended, and stops a detour skips, are left out. `walk_meters` is set when the two ends are within a 300 m walk of each other: no ride is searched then, so tell the user to walk. Otherwise both lists empty means the trip needs two or more transfers. Get stop IDs with `search_stops` or `get_stops_around_location`.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Find Routes Between Stops
  • get_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, d…Reads text others writeNo findings

    Why it is in this group

    • The name "get_disruptions" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Lists 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, closures, detours, or why a route is not running or a vehicle is off its usual path. Pass `route` and/or `stop_id` to get only the entries touching them; omit both for the whole city.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Disruptions
  • get_nearby_vehiclesReturns live vehicles near a point, nearest first, each with its route, destination, and distance.Reads text others writeNo findings

    Why it is in this group

    • The name "get_nearby_vehicles" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Nearby Vehicles
  • get_route_realtimeReturns every vehicle currently running on a route: position, the destination it is heading to, and its next stop with estimated arrival.Reads text others writeNo findings

    Why it is in this group

    • The name "get_route_realtime" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Returns every vehicle currently running on a route: position, the destination it is heading to, and its next stop with estimated arrival. `headways` sums up each direction: how many vehicles run, the live gaps between consecutive vehicles in minutes (front to back), and how often the timetable says it should run right now. Use when the user asks "where is my tram/bus right now?", how many vehicles are running, how far the next one is, or how often a route runs. Pass `direction` (0 or 1, as in `get_route_static`'s `stops`) to get only one way. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Route Realtime
  • get_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 …Reads text others writeNo findings

    Why it is in this group

    • The name "get_route_static" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Requires a route short name (e.g. "T30", "32A") or numeric external ID.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Route Static
  • get_stop_realtimeReturns live arrivals at a stop: route, destination, vehicle type, minutes until arrival, and each vehicle's position.Reads text others writeNo findings

    Why it is in this group

    • The name "get_stop_realtime" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Stop Realtime
  • get_stops_around_locationFinds stops near a geographic point, returning each stop's numeric ID, name, coordinates, walking distance, and the routes serving it.Reads text others writeNo findings

    Why it is in this group

    • The name "get_stops_around_location" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 500 m (about a 6-minute walk), enough in the city centre; widen it to 1 000–3 000 m in suburbs or rural areas where stops are sparse.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Stops Around Location
  • get_vehicle_infoReturns details for one vehicle by ID: position, route, destination, license plate, and its upcoming stops with names and estimated arrival times.Reads text others writeNo findings

    Why it is in this group

    • The name "get_vehicle_info" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Get Vehicle Info
  • search_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.Reads text others writeNo findings

    Why it is in this group

    • The name "search_stops" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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_stops_around_location` instead when you have coordinates rather than a name.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Search Stops

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write9
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.lad.lviv.ua/.well-known/oauth-protected-resource
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 changed.~1 changedView diff
  2. Tools9 changed.~9 changedView diff
  3. Tools9 changed.~9 changedView diff
  4. Tools4 changed.~4 changedView diff
  5. Tools1 added.+1 addedView diff

Install

Pinned to version 1.8.22. Values in angle brackets are yours to fill in.

claude mcp add --transport http timetable-api-node https://api.lad.lviv.ua/mcp
claude mcp add --transport http timetable-api-node https://api.lad.lviv.ua/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__timetable-api-node__get_stop_realtime",
      "mcp__timetable-api-node__search_stops",
      "mcp__timetable-api-node__find_routes_between",
      "mcp__timetable-api-node__get_route_static",
      "mcp__timetable-api-node__get_route_realtime",
      "mcp__timetable-api-node__get_disruptions",
      "mcp__timetable-api-node__get_stops_around_location",
      "mcp__timetable-api-node__get_nearby_vehicles",
      "mcp__timetable-api-node__get_vehicle_info"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as timetable-api-node. Review it before you use it.

Capability tags behind 9 rules
  • mcp__timetable-api-node__get_stop_realtime untrusted-input
  • mcp__timetable-api-node__search_stops untrusted-input
  • mcp__timetable-api-node__find_routes_between untrusted-input
  • mcp__timetable-api-node__get_route_static untrusted-input
  • mcp__timetable-api-node__get_route_realtime untrusted-input
  • mcp__timetable-api-node__get_disruptions untrusted-input
  • mcp__timetable-api-node__get_stops_around_location untrusted-input
  • mcp__timetable-api-node__get_nearby_vehicles untrusted-input
  • mcp__timetable-api-node__get_vehicle_info untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.vbhjckfd/timetable-api-node/verify?hash=181cb88424c1f3670725ebfb95359cc64a3710e9e64cb6e98aae68f5f5d37709" | jq -e '.changed == false'

Pinned hash 181cb88424c1, from Nov 18, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.vbhjckfd/timetable-api-node/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.vbhjckfd/timetable-api-node
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.vbhjckfd/timetable-api-node.svg)](https://radar.anlyon.com/servers/io.github.vbhjckfd/timetable-api-node)

Source: MCP Registry · repository. Synced Nov 18, 2026, 15:18 UTC.

Lviv Public Transport MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Lviv Public Transport MCP server safe?

No scan can promise that. What its definitions show: 9 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Lviv Public Transport MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Lviv Public Transport MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Lviv Public Transport MCP server have?

9 tools: 9 read. get_stop_realtime, search_stops, find_routes_between, get_route_static, get_route_realtime, get_disruptions, get_stops_around_location, get_nearby_vehicles and 1 more.

Does the Lviv Public Transport MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Lviv Public Transport MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Lviv Public Transport MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.