Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes.
Listed on
First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.
1
Directories
Collected by InvokeRank
4
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
0
GitHub stars
From MCP Toplist
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 |
| Directory | Listing | Tier | First seen |
|---|---|---|---|
| Official MCP Registry | PubFi MCP | - | 2 Oct 2026 |
| Listing | Publisher | Why it is grouped here |
|---|---|---|
| pubfi-mcp | helixbox | Same repository |