ai.pubfi/mcp (ai-pubfi-mcp)

The ai.pubfi/mcp Model Context Protocol (MCP) server routes crypto data through PubFi capability and gateway tools. Its purpose is to provide an MCP interface for forwarding or mediating crypto-related data requests via the PubFi ecosystem and associated gateway functionality.

🛠️ Key Features

Routes crypto data through PubFi capability
Uses PubFi gateway tools

🚀 Use Cases

Accessing or relaying crypto data using an MCP server layer
Integrating PubFi-based gateway handling for crypto data flows

⚡ Developer Benefits

Centralizes crypto data routing via PubFi capability and gateway tooling
Provides a named MCP server endpoint (ai.pubfi/mcp, slug: ai-pubfi-mcp) for integration

⚠️ Limitations

Only described at the level of routing crypto data through PubFi/gateway tools; no additional tools, fields, or operational details were provided.

PubFi Route Tools MCP Example

This example runs a dependency-free stdio bridge for PubFi's hosted MCP endpoint.

PubFi's MCP server remains hosted at https://mcp.pubfi.ai. This local file exists only because some MCP clients launch integrations as local stdio commands. It does not run a local provider adapter, it does not implement PubFi routing locally, and it does not accept upstream provider keys. It handles initialize and ping locally, forwards tools/list and authenticated tools/call requests to the hosted Rust MCP endpoint, and reads the PubFi caller key from an environment variable. Other hosted public introspection methods remain available directly on https://mcp.pubfi.ai; the stdio bridge keeps only the tool surface needed by local MCP clients.

Requirements

Node.js 18 or newer.
A PubFi API key only for authenticated tool calls or optional live execution.
No upstream Subscan, DeGov, supplier, wallet, or payment credentials.

No-Secret Smoke

The smoke passes without secrets by checking initialization, public tool listing, and the missing-key gate for tool calls:

node examples/agents/pubfi-route-tools-mcp/smoke_pubfi_route_tools_mcp.mjs

Expected report mode:

json

{
  "schema_version": "pubfi_mcp_agent_smoke_report.v1",
  "verdict": "pass",
  "mode": "auth_required"
}

Authenticated Dry Run

export PROD_PUBFI_API_KEY='<PubFi API key>'
export PUBFI_MCP_ENDPOINT='https://mcp.pubfi.ai'
node examples/agents/pubfi-route-tools-mcp/smoke_pubfi_route_tools_mcp.mjs

For staging MCP endpoints, set STG_PUBFI_API_KEY instead. The bridge selects the caller-key environment variable from PUBFI_MCP_ENDPOINT or PUBFI_MCP_ORIGIN.

The dry run verifies:

the five generic PubFi MCP tool names;
capability search;
route planning;
route explanation;
schema readback;
provider-specific execution rejection.

Optional Live Execution

Live execution consumes request allocation, currently targets the callable capability:wallet.account_balance route, and requires the hosted backend to have server-side provider credentials configured:

export PROD_PUBFI_API_KEY='<PubFi API key>'
export PUBFI_MCP_ENDPOINT='https://mcp.pubfi.ai'
export PUBFI_MCP_EXECUTE_LIVE=1
export PUBFI_MCP_SMOKE_WALLET_ADDRESS='<wallet address to query>'
node examples/agents/pubfi-route-tools-mcp/smoke_pubfi_route_tools_mcp.mjs

Do not paste the API key or wallet address into issue comments, prompts, public logs, or docs.

Execution Boundary

pubfi.route.execute executes only supported callable PubFi capability route ids with route-planning evidence. Contract-ready capabilities can appear in catalog or schema readback without becoming live MCP execution routes. Provider-specific route ids, unsupported capability ids, missing planning evidence, non-callable plans, supplier API execution, automatic payment, wallet or facilitator contact, and production route-time model authority fail closed or remain disabled.

MCP Client Config

json

{
  "mcpServers": {
    "pubfi-route-tools": {
      "command": "node",
      "args": ["examples/agents/pubfi-route-tools-mcp/server.mjs"],
      "env": {
        "PUBFI_MCP_ENDPOINT": "https://mcp.pubfi.ai"
      }
    }
  }
}

Load PROD_PUBFI_API_KEY through your local secret store rather than committing it to this file.

query	string	optional	Natural-language crypto data need or capability search query.
required_capabilities	array	optional	Optional capability ids or capability keywords to prioritize.
categories	array	optional	Optional capability categories such as wallet or on_chain_state.

intent	object	optional	Structured route intent with objective, chains, categories, and required capabilities.
objective	string	optional	Natural-language data objective when intent is not supplied.
chains	array	optional	Candidate networks or chains.
categories	array	optional	Capability categories to match.
required_capabilities	array	optional	Capabilities the selected route must satisfy.
dry_run	boolean	optional	Keep planning/explanation in dry-run mode.

route_id	string	required	Capability route id selected by pubfi.route.plan.
route_plan	object	required	Route-planning evidence returned by pubfi.route.plan.
arguments	object	required	Capability-specific execution arguments such as wallet address and network.
idempotency_key	string	optional	Optional caller-provided idempotency key for execution.
request_id	string	optional	Optional caller-provided request id for tracing.

intent	object	optional	Structured route intent with objective, chains, categories, and required capabilities.
objective	string	optional	Natural-language data objective when intent is not supplied.
chains	array	optional	Candidate networks or chains.
categories	array	optional	Capability categories to match.
required_capabilities	array	optional	Capabilities the selected route must satisfy.
dry_run	boolean	optional	Keep planning/explanation in dry-run mode.

PubFi MCP

ai.pubfi/mcp (ai-pubfi-mcp)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

pubfi.capabilities.search

pubfi.route.plan

pubfi.route.execute

pubfi.route.explain

pubfi.schema.get