Agent connector

MCP tools

Primitive402 exposes catalog-backed tools over MCP so agent runtimes can call tools by stable machine name.

Current production mode: Base mainnet USDC billing beta on primitive402.dev.

status.json is the live source Billing policy Mainnet readiness Mainnet monitoring

Run locally

Primitive402 currently supports local stdio MCP only.

pnpm build
pnpm mcp

Tool names and endpoint mapping

`safe_fetch_url`

Safe Fetch URL

/v1/safe-fetch-url /x402/v1/safe-fetch-url

`check_prompt_injection_risk`

Check Prompt Injection Risk

/v1/check-prompt-injection-risk /x402/v1/check-prompt-injection-risk

`verify_claim_against_source`

Verify Claim Against Source

/v1/verify-claim-against-source /x402/v1/verify-claim-against-source

`create_page_proof`

Create Page Proof

/v1/create-page-proof /x402/v1/create-page-proof

`extract_return_policy`

Extract Return Policy

/v1/extract-return-policy /x402/v1/extract-return-policy

`extract_subscription_terms`

Extract Subscription Terms

/v1/extract-subscription-terms /x402/v1/extract-subscription-terms

`check_product_fit`

Check Product Fit

/v1/check-product-fit /x402/v1/check-product-fit

Example tool call

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "safe_fetch_url",
    "arguments": {
      "url": "https://example.com",
      "output": "markdown"
    }
  }
}

Tool library

For route-by-route input fields, output fields, prices, and examples, use /docs/tools.

Remote MCP readiness

Current MCP support is local stdio only. A future hosted or gateway-compatible MCP surface may use Streamable HTTP, but Primitive402 has not implemented a remote MCP endpoint yet.

Auth and payment questions are still open. Current x402 route behavior remains HTTP API based through /x402/v1/*; remote MCP must preserve tool safety, schema clarity, rate limits, payment semantics, SSRF protection, no-secret logging, and clear separation between public tools and internal/admin surfaces.

Remote MCP readiness plan