​
MCP Client Setup

PubFi exposes generic route and capability tools over MCP. The hosted endpoint is:
The discovery manifest is:

​
Tools

  • pubfi.capabilities.search
  • pubfi.route.plan
  • pubfi.route.execute
  • pubfi.route.explain
  • pubfi.schema.get
Provider ids, endpoint paths, schemas, prices, source freshness, and readiness appear as catalog or route-result data. They are not public tool names.

​
Auth

Hosted MCP tools/call requests require a PubFi API key. Public handshake and introspection methods, such as initialize, ping, tools/list, resources/list, resources/templates/list, prompts/list, and notifications/initialized, can be called without a key:
Do not pass upstream provider keys as MCP arguments. PubFi leases upstream credentials server-side when the selected route is callable and configured.

​
Local Stdio Bridge

The current public-safe local example lives in the source repository at:
PubFi’s MCP server is hosted at https://mcp.pubfi.ai. The local file is not a second MCP backend and it does not run provider logic locally. It is a dependency-free stdio bridge for MCP clients that launch tools as local commands. The bridge handles initialize and ping locally, forwards tools/list and authenticated tools/call requests to the hosted Rust MCP endpoint, and writes the response back to stdio. Other hosted public introspection methods remain available on https://mcp.pubfi.ai; the local bridge keeps its stdio surface intentionally small.
  1. Call pubfi.capabilities.search.
  2. Call pubfi.route.plan.
  3. Call pubfi.route.explain when the plan needs a reason readback.
  4. Call pubfi.schema.get before constructing execution input.
  5. Call pubfi.route.execute only for supported callable capability route ids with planning evidence.

​
Tool Inputs

The hosted tools/list method publishes the current JSON Schema for each tool. The current public input fields are:

​
Fail-Closed Behavior

Unsupported provider-specific route ids, missing planning evidence, non-callable plans, and paid supplier execution attempts should return explicit gate readbacks rather than silently calling upstream APIs.