Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
PakBus 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.
What it does
Bus and metro journeys, departures, routes, fares and service changes in Pakistani cities.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pakbus-mcp https://pakbus.app/mcp
# 2 — ask your agent for something these tools do
# list_cities, find_places, plan_journey and 3 more
PakBus costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 pakbus-mcp https://pakbus.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
6 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.
Lists the Pakistani cities with PakBus routes, the number of routes in each and the city name in Urdu.
No parameter schema on file.
Finds bus stops, stations and the places around them by name, in one city or in every city. Accepts common English spellings of Pakistani place names, such as Faizabad or Faiz Abad. Returns the place_id and city each other tool needs. When nothing matches in a city, it lists the stops in that city served by the most routes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Place name in English letters, such as Liberty Chowk or Saddar. |
| city | string | no | Search one city network. Leave out to search every city. |
Plans bus and metro journeys between two places in one city network. Returns the first journey leaving at or after the departure time as numbered steps with boarding stops, changes, walking, times and fare, a link that opens it in PakBus, and up to two later departures on one line. Apps that show interactive views also get a map of the journey.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City network from find_places or list_cities, such as Lahore, Attock or Rawalpindi. |
| from | string | yes | place_id of the start, from find_places. |
| to | string | yes | place_id of the destination, from find_places. |
| depart | string | no | Departure date and time in Pakistan local time, as YYYY-MM-DDTHH:MM. Leave out to leave now. Search again with a later time for later journeys. |
| max_changes | integer | no | Most changes between buses, 0 for direct journeys only. Defaults to 2. When none are found within the limit, journeys with up to 5 changes are returned. |
Lists the next three departures today from a place for each route and direction that boards there, soonest first, with the minutes until each, the last bus of the day, the fare and the stops each direction serves after the place.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City network from find_places or list_cities, such as Lahore, Attock or Rawalpindi. |
| place | string | yes | place_id from find_places. |
Lists current and announced service changes in a city network, such as closed stations, skipped stops or diversions, for every route or for one route by code, name or service. plan_journey, place_departures and route_details already include the changes on the routes they use.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City network from find_places or list_cities, such as Lahore, Attock or Rawalpindi. |
| route | string | no | Route code, name or service. Leave out for every change in the city. |
Lists a city's routes with fares, or shows one route: its stops in order in each direction, its fare and the day’s departure times from the first stop. Finds a route by code such as EV5701, by name such as Orange Line, or by service such as Green Electric Bus.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| city | string | yes | City network from find_places or list_cities, such as Lahore, Attock or Rawalpindi. |
| route | string | no | Route code, name or service. Leave out to list every route in the city. |
- 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 PakBus or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_cities | no tags | |
| find_places | no tags | |
| plan_journey | no tags | |
| place_departures | no tags | |
| service_notices | no tags | |
| route_details | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.0.1.
No release note was published with this version.
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.
Any signed-in account that does not publish PakBus can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.