Official MCP RegistryListed
PubFi MCP
Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes.
First seen 2 Oct 2026. Evidence as of 9 Oct 2026.
4
Tools
From an anonymous probe
1
Source listings
Each with its own history
0
Recorded changes
Since first seen
Tools
| Tool | Description | Behaviour |
|---|---|---|
| pubfi.capabilities.get | Return the full typed request, response, metering, and readiness contract for one exact capability id from the installed Registry generation. | Read-only |
| pubfi.capabilities.list | Enumerate the complete installed Registry v2 catalog as deterministic compact pages. The server does not rank, infer intent, or choose a capability. | Read-only |
| pubfi.route.execute | Execute one exact GET or POST path through the authenticated PubFi account lane and the same Registry v2 matcher and typed executor as the HTTP gateway. Append :free only when the capability catalog publishes that exact account-scoped free variant. | Destructive |
| pubfi.substrate.runtime_upgrade.verify | Verify one reviewed Substrate System.apply_authorized_upgrade extrinsic through the authenticated account lane. Supply the expected Blake2b-256 hash of the FRAME System AuthorizedUpgrade code payload, not the active :code hash at the apply block. The server streams and discards provider runtime code, persists only a compact proof, and returns independent comparison evidence. | Destructive |
Change history
No changes since the first observation. The first snapshot is the baseline.
| Source | Listing | First seen | Last seen | Versions |
|---|---|---|---|---|
| Official MCP Registry | ai.pubfi/mcp | 2 Oct 2026 | 9 Oct 2026 | 1 |