PubFi MCP

What the PubFi MCP MCP server does

PubFi MCP MCP server provides an agent-facing way to work with PubFi's crypto data layer. Its public documentation describes generic route and capability tooling for agents and MCP clients, rather than a fixed list of individually named data providers. The service is intended to help clients discover available capabilities and send requests through PubFi's gateway surfaces.

The repository is primarily a public documentation and examples project. It links to the hosted MCP service, API reference, OpenAPI schema, manifests, discovery documents, and environment-specific endpoints. The documentation does not establish that every source listed in Discovery is callable through the gateway, so provider availability should be checked against the current catalog.

How it works

A compatible MCP client connects to PubFi's hosted MCP endpoint. The authenticated MCP root accepts either a PubFi API key or an OAuth access token. For accountless payment flows, PubFi documents a separate /x402 endpoint; this is distinct from the authenticated MCP root and should not be assumed to apply to every gateway route.

PubFi also publishes Registry v2 catalog material and capability inspection examples. These surfaces can help an agent or developer examine what is currently available before making a request. The repository identifies both production and staging roots, including a staging MCP service and a Base Sepolia x402 boundary.

The PubFi MCP MCP server is therefore best treated as a hosted routing and capability layer. Current catalogs and payment challenges matter: historical examples or an old acceptance run do not prove that a production route or x402 flow remains available.

Setup and configuration

Start with the repository's MCP client setup and client-guide documentation, then select the appropriate PubFi environment. Production and staging use separate web, API, and MCP roots. The published staging MCP endpoint is https://mcp-stg.pubfi.ai; the staging x402 endpoint is https://mcp-stg.pubfi.ai/x402. Production MCP and x402 endpoints are also published in the documentation and manifests.

Authenticated examples require a PubFi API key, which must be loaded from a secret store. OAuth access tokens are another supported authentication method for the authenticated MCP root. Payment-enabled x402 clients require a buyer wallet key, also kept in a secret store. The supplied material does not specify a required environment-variable name, client command, or local package installation procedure.

Tools and capabilities

Documented capabilities include:

• Generic route and capability tools for agents and MCP clients.
• Hosted MCP access through production and staging endpoints.
• Registry v2 catalog inspection without authentication.
• API access described through an OpenAPI 3.1 schema and interactive reference.
• Accountless x402 payment flows through a separate endpoint.
• Public MCP manifests, server-card metadata, discovery pointers, and capability exports.

The repository includes a dependency-free stdio bridge example for the hosted MCP endpoint, along with curl-based catalog inspection and x402 challenge examples. These examples are references for integration and verification; they do not imply that all routes support x402.

Limitations and notes

PubFi MCP MCP server documentation supports routing and capability discovery, but it does not claim that PubFi performs supplier procurement, supplier payment, wallet custody, or live model-ranked routing by default. Discovery entries should not be treated as proof that a provider is callable through PubFi.

Staging and production are separate boundaries. A Base Sepolia staging challenge does not demonstrate production x402 availability. Before using a paid route, inspect the current catalog and unsigned challenge. Do not commit API keys, wallet keys, payment signatures, payment responses, raw account responses, wallet addresses, or production readbacks.

The repository contains separate MIT-licensed code and CC-BY-4.0 documentation notices. It is documentation-led, so implementation details not stated in the supplied material should be verified against the current PubFi references.