PakBus: MCP server, CLI and agent surfaces
Yes: PakBus runs a public MCP server at pakbus.app that listed 6 tools to a client with no credentials on 4 November 2026. Examples: list_cities, find_places, plan_journey. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool.
Fact sheet
| Company | PakBus |
|---|---|
| Domain | pakbus.app |
| Category | Uncategorised (assigned by this directory from the registry description) |
| MCP server | Verified (No authentication) |
| Ora score | none: Ora returned no cached score for pakbus.app when asked on 5 November 2026 |
| Company found through | the GitHub MCP Registry; the official MCP Registry |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://pakbus.app/mcp |
|---|---|
| How it was found | listed in the GitHub MCP Registry; the official MCP Registry |
| Transport | streamable-http |
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server | pakbus 1.0.0 |
| Capabilities | tools, resources |
| Tools | 6 |
| Resources | 1 |
| Prompts | 0 |
| Connected | 4 November 2026, 20:03 UTC |
| Handshake time | 170 ms over 1 attempt |
Tools listed
6 tools
- list_cities
- find_places
- plan_journey
- place_departures
- service_notices
- route_details
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:58:47Z https://pakbus.app/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 396 ms
- 20:03:57Z https://pakbus.app/mcp sent initialize, notifications/initialized, tools/list, resources/list result verified (HTTP 200) 170 ms
Authentication
| Auth type | No authentication |
|---|
The sign-in route, step by step
- Send the handshake to
https://pakbus.app/mcpover streamable-http. Servers on the 2026-07-28 revision answerserver/discover; older servers answerinitialize. - Send
tools/list, thenresources/listandprompts/listif the capabilities name them. - Send no token. The connector sent none and the server answered, so any MCP client can read this list.
- Calling a tool is a separate step this directory never takes.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for PakBus. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | No OpenAPI file at the root paths checked. |
| WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. |
| MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. |
| A2A agent card | Not checked: the domain is not in the shared crawl for this edition. |
| A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. |
| agents.json | Not checked: the domain is not in the shared crawl for this edition. |
| OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | Yes: app.pakbus/pakbus |
| GitHub MCP Registry | Yes |
| awesome-remote-mcp-servers | No |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |