ai.pubfi/mcp · v0.2.84 · other
PubFi MCP is healthy: it completed an MCP handshake in 1917 ms and exposes 4 tools. It scores 63/100.
Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes.
Endpoint: https://mcp.pubfi.ai (streamable-http)
Repository · Website · JSON · Add to my inventory
| health | 18.3 / 25 |
| authEase | 15 / 15 |
| toolQuality | 15 / 15 |
| maintenance | 7 / 15 |
| adoption | 0 / 10 |
| usage | 0 / 10 |
| security | 8 / 10 |
Scoring v0.3, computed 2026-10-14T20:21:24.341Z.
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T12:15:34.654Z | Healthy | 1917 |
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. |
pubfi.capabilities.get | Return the full typed request, response, metering, and readiness contract for one exact capability id from the installed Registry generation. |
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. |
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 |