# Vbhjckfd Timetable Api Node MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.vbhjckfd%2Ftimetable-api-node
Registry id: `mcp-registry/io.github.vbhjckfd/timetable-api-node`
Status: live (checked 2026-10-27T02:18:17.342Z)

## Verdict

Vbhjckfd Timetable Api Node MCP server answered 99.95% of Glimind's liveness checks over 30 days, better than 36% of MCP servers, with 1387 ms median handshake and 14 outages in 90 days. Its agent-readiness grade is A (99/100) across 9 tools, costing an agent about 2,791 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.95% | 36% of MCP servers |
| Median handshake latency | 1387 ms | 11% of MCP servers |
| p95 handshake latency | 3374 ms | — |
| Checks in 30 days | 4,971 | — |
| Outages, 90 days | 14 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 99/100 (A) | 93% of MCP servers |
| Tools | 9 | — |
| Tool-list size for an agent | ~2,791 tokens | 47% of MCP servers |
| Days observed | 29 | — |

## Install

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

Claude Code:

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

## Tools (9)

- `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 — bes
- `get_disruptions`: 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 susp
- `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?"
- `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. `headways` sums up eac
- `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
- `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
- `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 s
- `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 
- `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 serv

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.