Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PakBus

REMOTE · PAKBUS.APP

Bus and metro journeys, departures, routes, fares and service changes in Pakistani cities.

Available components

+4 this week 79 Trust /100

Last scanned (1 hour ago)

Scores higher than 79% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability80
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 924 tokens (~132/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “place_departures” rewrote its description, which is the text the model reads security
    • Tool “plan_journey” rewrote its description, which is the text the model reads security
    • Tool “route_details” rewrote its description, which is the text the model reads security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://pakbus.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pakbus.app CN=WE1,O=Google Trust Services,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA256 7144c85ad3b703a40ee2489426f0f2ed
SANs: pakbus.app, *.pakbus.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pakbus.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
pakbus.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pakbus.app/mcp Verified 200
http (plaintext) http://pakbus.app/mcp HTTPS enforced 301 https://pakbus.app/mcp
MCP tools · 6 exposed · ~757 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
find_places ~121

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.

NameTypeReqDescription
citystring–Search one city network. Leave out to search every city.
querystringyesPlace name in English letters, such as Liberty Chowk or Saddar.

No output schema declared.

No examples provided.

list_cities ~31

Lists the Pakistani cities with PakBus routes, the number of routes in each and the city name in Urdu.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

place_departures ~111

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. Routes with live bus positions give live times counted from where each bus is now.

NameTypeReqDescription
citystringyesCity network from find_places or list_cities, such as Lahore, Attock or Rawalpindi.
placestringyesplace_id from find_places.

No output schema declared.

No examples provided.

plan_journey ~248

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. When the first bus has live positions and the journey leaves within the hour, it also says when the next one reaches the boarding stop. Apps that show interactive views also get a map of the journey.

NameTypeReqDescription
citystringyesCity network from find_places or list_cities, such as Lahore, Attock or Rawalpindi.
departstring–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.
fromstringyesplace_id of the start, from find_places.
max_changesinteger–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.
tostringyesplace_id of the destination, from find_places.

No output schema declared.

No examples provided.

route_details ~132

Lists a city's routes with fares, or shows one route: its stops in order in each direction, its fare, the day’s departure times from the first stop and, for routes with live bus positions, where each bus is now. Finds a route by code such as EV5701, by name such as Orange Line, or by service such as Green Electric Bus.

NameTypeReqDescription
citystringyesCity network from find_places or list_cities, such as Lahore, Attock or Rawalpindi.
routestring–Route code, name or service. Leave out to list every route in the city.

No output schema declared.

No examples provided.

service_notices ~114

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.

NameTypeReqDescription
citystringyesCity network from find_places or list_cities, such as Lahore, Attock or Rawalpindi.
routestring–Route code, name or service. Leave out for every change in the city.

No output schema declared.

No examples provided.

Install

How do I install the PakBus MCP server?

PakBus is a hosted endpoint at https://pakbus.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pakbus.app

# add to Claude Code
claude mcp add --transport http app-pakbus-pakbus 'https://pakbus.app/mcp'
Common questions

What is the PakBus MCP server?

PakBus is an MCP server listed in the public MCP registry as app.pakbus/pakbus. Bus and metro journeys, departures, routes, fares and service changes in Pakistani cities. This page covers its hosted endpoint (https://pakbus.app/mcp).

Is the PakBus MCP server safe to use?

PakBus scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PakBus MCP server expose?

PakBus exposes 6 tools: list_cities, find_places, plan_journey, place_departures, service_notices, route_details. Their descriptions and schemas cost roughly 757 tokens of context every time the server is loaded.

Does the PakBus MCP server require authentication?

No. We connected to PakBus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PakBus MCP server still maintained?

PakBus is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.