# Lviv Public Transport (remote · api.lad.lviv.ua)

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

- Trust score: 66/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.lad.lviv.ua`: 66/100 (this document), [markdown](https://verifymcp.io/servers/vbhjckfd-timetable-api-node/api.md), [page](https://verifymcp.io/servers/vbhjckfd-timetable-api-node/api)

## Channel facts

- Endpoint: `https://api.lad.lviv.ua/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1818 tokens (~181/item across 10 items; 7 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 14/100
  - Stability check failed: schema churn in the 8 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.vbhjckfd-timetable-api-node]
url = "https://api.lad.lviv.ua/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vbhjckfd-timetable-api-node": {
      "type": "remote",
      "url": "https://api.lad.lviv.ua/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vbhjckfd-timetable-api-node --url https://api.lad.lviv.ua/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vbhjckfd-timetable-api-node:
    url: "https://api.lad.lviv.ua/mcp"
```

### Other

```json
{
  "mcpServers": {
    "vbhjckfd-timetable-api-node": {
      "type": "http",
      "url": "https://api.lad.lviv.ua/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 11 to 14.

### 2026-08-01 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 4 to 8.

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 64, −1)

- [security regression] Stability: 0.03 → fail

### 2026-07-27 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (7)

### `get_stop_realtime` (~138 tokens)

Get Stop Realtime

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.

Input parameters:

- `stop_id` (required): Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string.

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

### `get_route_static` (~183 tokens)

Get Route Static

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.

Input parameters:

- `route_name` (string, required): Route short name (e.g. "T30", "32A") or numeric external ID.

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

### `get_route_realtime` (~152 tokens)

Get Route Realtime

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.

Input parameters:

- `route_name` (string, required): Route short name (e.g. "T30", "32A") or numeric external ID.

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

### `get_stop_geometry` (~162 tokens)

Get Stop Geometry

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.

Input parameters:

- `stop_id` (required): Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string.

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

### `get_stops_around_location` (~253 tokens)

Get Stops Around Location

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.

Input parameters:

- `latitude` (number, required): Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv).
- `longitude` (number, required): Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv).
- `radius_meters` (integer): Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas.

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

### `get_nearby_vehicles` (~148 tokens)

Get Nearby Vehicles

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.

Input parameters:

- `latitude` (number, required): Decimal latitude of the centre point, WGS84 (e.g. 49.842).
- `longitude` (number, required): Decimal longitude of the centre point, WGS84 (e.g. 24.031).

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

### `get_vehicle_info` (~143 tokens)

Get Vehicle Info

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.

Input parameters:

- `vehicle_id` (string, required): Vehicle ID as returned by get_route_realtime, get_nearby_vehicles, or get_stop_realtime.

Output parameters:

- `data` (object)
- `ui_blocks` (array)
- `view` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vbhjckfd-timetable-api-node/api#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 64
- 2026-07-27: 65
- 2026-07-26: 65

## Links

- Remote endpoint: https://api.lad.lviv.ua/mcp
- Repository: https://github.com/vbhjckfd/timetable-api-node
- Website: https://lad.lviv.ua/
- Changelog RSS feed: https://verifymcp.io/servers/vbhjckfd-timetable-api-node/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/vbhjckfd-timetable-api-node/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/vbhjckfd-timetable-api-node/api