# PubFi MCP MCP server

Route crypto data needs through PubFi capability and gateway tools.

## Links
- Registry page: https://www.getdrio.com/mcp/ai-pubfi-pubfi-mcp
- Repository: https://github.com/helixbox/pubfi-docs
- Website: https://pubfi.ai/agents.md

## Install
- Endpoint: https://mcp.pubfi.ai
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: Authorization (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://mcp.pubfi.ai
- Header: Authorization

## Tools
- 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. Endpoint: https://mcp.pubfi.ai
- pubfi.capabilities.get - Return the full typed request, response, metering, and readiness contract for one exact capability id from the installed Registry generation. Endpoint: https://mcp.pubfi.ai
- pubfi.route.execute - Execute one exact GET or POST path through the same Registry v2 matcher, credential authority, and typed executor as the HTTP gateway. Use either an authenticated account lane with metering or the accountless x402 payment metadata lane. Endpoint: https://mcp.pubfi.ai

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: ai.pubfi
- Version: 0.1.1
- Runtime: Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Jul 17, 2026
- Source: https://registry.modelcontextprotocol.io