servers / pubfi-mcp
PubFi MCP
communitystreamable_httpremotewrite capablehealthy
Route crypto data needs through PubFi capability and gateway tools.
01Tools · 9
How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| pubfi.capabilities.get Return the full typed request, response, metering, and readiness contract for one exact capability id from the installed Registry generation. | read | false | unknown |
| 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 | false | unknown |
| pubfi.capabilities.search Search the currently installed Registry v2 capability snapshot without querying PostgreSQL, the Control Plane, or upstream providers. | read | false | unknown |
| pubfi.pricing.quote Estimate PubFi credits and readiness for a capability route. This read-only quote does not create payment payloads, does not procure supplier access, and does not execute the route. | read | false | unknown |
| 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. | write | true | unknown |
| pubfi.route.explain Explain a route decision using only the currently installed Registry v2 catalog and its exact generation and manifest identity. | unknown | unknown | unknown |
| pubfi.route.plan Plan an exact Registry v2 route from the installed in-memory generation without executing an upstream request or creating usage. | unknown | unknown | unknown |
| pubfi.schema.get Return the current Registry-aware MCP input and output schema for a named tool, including the installed generation and dynamic routes. | read | false | unknown |
| 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. | read | false | unknown |
02Install & source
https://mcp.pubfi.ai
remote_url- repohttps://github.com/helixbox/pubfi-docs
- homepagehttps://mcp.pubfi.ai
- licenseNOASSERTION
- adoption0 stars · 1 forks
03Access granted
Process payments · write
The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.
05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-10-05 12:20Z
next_check2026-10-05 15:20Z
cadenceevery 3h
verifiedmetadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed
index_statusindex — 9 unique facts >= 5
06Badge
Add the “as seen on MCPExplorer” badge to your README. 
[](https://mcpexplorer.com/servers/pubfi-mcp)
Next step
This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.
Explore loadouts →