PakBus MCP server
app.pakbus/pakbuspakbus.appstreamable-httpv1.0.1Scanned
Bus and metro journeys, departures, routes, fares and service changes in Pakistani cities.
6 tools: 1 do something that can't be undone and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the PakBus MCP server can do
The PakBus MCP server is published by pakbus.app, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (plan_journey), but cannot delete data. 5 tools only read.
1 tool can send data out of your system (plan_journey).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Can't be undone 1Claude Code: ask
plan_journeyPlans bus and metro journeys between two places in one city network.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "plan_journey" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- title: Plan a journey
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
find_placesFinds bus stops, stations and the places around them by name, in one city or in every city.No findings
Why it is in this group
- The name "find_places" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find places
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_citiesLists the Pakistani cities with PakBus routes, the number of routes in each and the city name in Urdu.No findings
Why it is in this group
- The name "list_cities" says "list": a word for reading.
Description, as the server wrote it Lists the Pakistani cities with PakBus routes, the number of routes in each and the city name in Urdu.
Annotations the server declares
- title: List cities
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
place_departuresLists 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…No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Next departures
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
route_detailsLists 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 po…No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Route details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
service_noticesLists 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.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Service changes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pakbus.app/mcp: tools/list returned 6 tools to an anonymous client, including plan_journey (irreversible)
Findings
Matches of fixed checks, with the text they matched.
- Warnplan_journey
The server marks "plan_journey" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:place_departuresOnly readsdescription
- Changed:plan_journeyCan't be undonedescription
- Changed:route_detailsOnly readsdescription
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http pakbus https://pakbus.app/mcpclaude mcp add --transport http pakbus https://pakbus.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pakbus__list_cities",
"mcp__pakbus__find_places",
"mcp__pakbus__place_departures",
"mcp__pakbus__service_notices",
"mcp__pakbus__route_details"
],
"ask": [
"mcp__pakbus__plan_journey"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pakbus. Review it before you use it.
Capability tags behind 1 rule
- mcp__pakbus__plan_journey outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.pakbus/pakbus/verify?hash=71d3c745eb241711368cd744e66c10e41c1605bc14e2db479f2c02bb8e6c84a4" | jq -e '.changed == false'Pinned hash 71d3c745eb24, from Nov 8, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.pakbus/pakbus/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.pakbus/pakbus)Source: MCP Registry · repository. Synced Oct 22, 2026, 23:17 UTC.
PakBus MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PakBus MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the PakBus MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PakBus MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: plan_journey.
What tools does the PakBus MCP server have?
- 6 tools: 1 irreversible, 5 read. plan_journey, list_cities, find_places, place_departures, service_notices and route_details.
Does the PakBus MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PakBus MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): plan_journey.
Has the PakBus MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.