Use MCP 2026-07-28 discovery or 2025-11-25 initialize to list and execute PubFi routes.
Connect Remote server
claude mcp add --transport http mcp https://mcp.pubfi.ai --header "Authorization: Bearer <YOUR_API_KEY>"{
"mcpServers": {
"mcp": {
"url": "https://mcp.pubfi.ai",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.pubfi.ai",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://mcp.pubfi.aiReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | PubFi API key as a Bearer token. Optional for public capability list/get calls; required for route execution unless the client uses the accountless x402 lane. Example: Bearer <PubFi API key>. |
Details
| Endpoint | https://mcp.pubfi.ai (Streamable HTTP) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | ai.pubfi/mcp |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.