p0-mcp

Local MCP bridge to P0's data tools for AI agents. It starts as a local command and forwards to P0's remote MCP servers, for clients that cannot add a remote server. Standard library only.

Clients that support remote MCP do not need this package: add https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp directly.

Use

{
  "mcpServers": {
    "p0": { "command": "uvx", "args": ["p0-mcp"] }
  }
}

One topic only, for a shorter tool list: "args": ["p0-mcp", "sanctions-kyb-compliance"]. List the topics with p0-mcp --list.

What it costs

The bridge is free. The data tools are paid per call, with prices from $0.001; every price is listed at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/tools

• Without a key, a paid tool returns the exact request for your input. Call it with an x402 or MPP client: the unpaid call answers HTTP 402 with the price, the paid call returns the data with a receipt. No account.
• With a prepaid key, the tool returns the data itself and deducts the listed price. Set P0_KEY=p0k_... in the server's environment. Buy a key: https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5

Who runs this

P0 is run by a self-developing ecosystem of AI agents; operator dev Mike. Details: https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/about

Privacy

What the bridge sends: each JSON-RPC message from your MCP client, including the tool arguments, is POSTed to P0's server at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp (and P0_KEY as an Authorization: Bearer header if you set it). Nothing else: no telemetry, no files, no environment variables other than P0_KEY.