Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Lviv Public Transport is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Lviv public transport MCP: stops, timetables, routes, and live vehicle positions. No API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http lviv-public-transport-mcp https://api.lad.lviv.ua/mcp
# 2 — ask your agent for something these tools do
# get_stop_realtime, search_stops, find_routes_between and 5 more
Lviv Public Transport costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VBAll 1 server
vbhjckfd1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http lviv-public-transport-mcp https://api.lad.lviv.ua/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stop_id | integer | yes | Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Stop name or part of it, e.g. "Ринок", "opera", "Стрийська". |
| limit | integer | no | Maximum stops to return (1–25, default 10). |
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_sto
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_stop_id | integer | yes | Stop ID where the trip starts. |
| to_stop_id | integer | yes | Stop ID where the trip ends. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_name | string | yes | Route short name (e.g. "T30", "32A") or numeric external ID. |
| include_shapes | boolean | no | Include route polylines ([lat, lng] points per direction) for map drawing. Default false. |
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 e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| route_name | string | yes | Route short name (e.g. "T30", "32A") or numeric external ID. |
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 de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| latitude | number | yes | Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv). |
| longitude | number | yes | Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv). |
| radius_meters | integer | no | Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas. |
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 (WGS8
| Parameter | Type | Required | Notes |
|---|---|---|---|
| latitude | number | yes | Decimal latitude of the centre point, WGS84 (e.g. 49.842 for central Lviv). |
| longitude | number | yes | Decimal longitude of the centre point, WGS84 (e.g. 24.031 for central Lviv). |
| radius_meters | integer | no | Search radius in metres (100–1000, default 500). |
| route | string | no | Only vehicles on this route, by short name (e.g. "Т30", "А1"). Omit for all routes. |
| limit | integer | no | Maximum vehicles to return, nearest first (1–50, default 15). total reports how many were in range. |
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 vehicl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vehicle_id | string | yes | Vehicle ID as returned by get_route_realtime, get_nearby_vehicles, or get_stop_realtime. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Lviv Public Transport or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.7.7.
1.7.7
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Lviv Public Transport can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.