servers / pubfi-mcp
PubFi MCP
communitystreamable_httpremotewrite capablehealthy
Route crypto data needs through PubFi capability and gateway tools.
01Tools · 6
| Tool | Risk | Side effects | Approval |
|---|---|---|---|
| pubfi.route.plan Create a dry-run PubFi route plan from an intent, objective, chains, categories, or required capabilities. This planning step is read-only and does not call upstream providers, execute routes, or spend credits. | write | true | unknown |
| pubfi.route.execute Execute a selected PubFi capability route using route-planning evidence from pubfi.route.plan. This call requires a PubFi API key, may consume account credits, may call server-side provider connectors, and rejects provider-specific route IDs outside the generic capability surface. | write | true | unknown |
| pubfi.route.explain Explain the routing decision PubFi would make for an intent. This is a read-only dry-run diagnostic that returns reason codes, filters, and selected route metadata without executing providers or spending credits. | write | true | unknown |
| pubfi.schema.get Return PubFi MCP input and output schema details for a named tool, especially pubfi.route.execute. This read-only helper is intended for agent setup and validation before planning or execution. | write | true | 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. | write | true | unknown |
| pubfi.capabilities.search Search PubFi's capability catalog for routeable crypto data needs. Provide a natural-language query or capability filters; the result is read-only catalog metadata and does not call upstream providers or spend credits. | 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-07-06 20:50Z
next_check2026-07-08 01:28Z
cadenceevery 29h
verifiedtools_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 →