Pubfi MCP server
{
"mcpServers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}{
"servers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}{
"mcpServers": {
"pubfi": {
"type": "http",
"url": "https://mcp.pubfi.ai"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.2.59
What it does
PubFi's MCP server exposes crypto data API routes from PubFi's agent-native data layer, discoverable via MCP 2026-07-28 discovery or 2025-11-25 initialize. It targets AI agents and MCP clients that need to list and execute crypto data routes, with authentication via API key or OAuth, and an optional accountless payment path via an x402 endpoint.
- List available PubFi crypto data routes and capabilities from an MCP client using tools/list.
- Execute a specific PubFi data route from an agent using MCP tool calls with an API key or OAuth token.
- Access crypto data routes without credentials by paying per request through the x402 endpoint on Base mainnet or Base Sepolia testnet.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.