Concepts

MCP Server

The cc0pedia database + the cc0.company agent-services catalog, as a remote Model Context Protocol server. Pay-per-call over x402.

https://cc0.company/api/mcp is a remote Model Context Protocol server (Streamable HTTP, JSON-RPC 2.0). It exposes every managed cc0.company service as a tool an AI agent can call: the cc0pedia read API over the largest machine-readable CC0 database, CC0 image generation, a daily market brief, and re-brokered third-party agents. Tools are discovered live from the catalog, so the set grows over time without changing your client.

Open-source repo

Manifest, runnable examples, and the full tool catalog live at github.com/cryptomfer/cc0company-mcp.

Connect

Claude Code:

bash

claude mcp add --transport http cc0pedia https://cc0.company/api/mcp

Cursor — .cursor/mcp.json:

json

{ "mcpServers": { "cc0pedia": { "url": "https://cc0.company/api/mcp" } } }

Claude Desktop / claude.ai: Settings → Connectors → Add custom connector → the URL above. Any MCP client works — Streamable HTTP transport, no auth to connect.

Payment — x402

Every tools/call is a paid x402 request. initialize, tools/list and ping are free. The first call to a tool returns 402 Payment Required with the challenge in the PAYMENT-REQUIRED header; your x402 client signs a USDC (ERC-3009) authorization on Base and retries with the PAYMENT-SIGNATURE header. Use an x402-enabled client that wraps the MCP transport's fetch.

Network — Base mainnet (eip155:8453)
Asset — USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Scheme — exact, fixed price per call
Pay only for what you use — a call that resolves nothing returns a 4xx and the charge is cancelled

Vanilla clients without an x402 wallet can connect and list tools, but tool calls return 402 until paid. It's the same flow the agent services use — and the same catalog behind it, so prices match.

Send tools/call unbatched

A batched JSON-RPC request cannot carry the 402 challenge back. Send each tools/call as a single request; the server refuses a batched one with an explanatory result.

Tools

Discovered live from tools/list. The server always advertises the four cc0pedia tools, then merges in whatever the agent-services catalog is currently serving. Today:

Tool	Price (USDC)	What it returns
`cc0pedia`	0.01	One CC0 creator / collection / work — provenance, license, onchain pointers, full body
`cc0pedia-search`	0.01	Ranked search across the CC0 database
`cc0pedia-verify`	0.01	License oracle — is this contract a documented CC0 work?
`cc0pedia-market`	0.01	Live market for a CC0 asset — token price / FDV / liquidity / volume, or NFT floor / volume / owners
`cc0-daily-brief`	0.05	Top CC0 NFT collections by 24h volume, with narrative
`sartoshi-gen`, `darkfarms-gen`, `hokusai-gen`, `van-gogh-gen`, `monet-gen`	0.069	CC0 image generation (async — returns a job to poll)
`mfergpt-lore`	0.025	Third-party, re-brokered over x402
`mfergpt-ask`, `mfergpt-mferfy`	0.055	Third-party, re-brokered over x402
`tcgenerate-random`	1.005	Third-party, re-brokered — trading card image pinned to IPFS

Each tool's description carries its live price, so treat tools/list as the source of truth rather than this table.

Free discovery

bash

curl -s https://cc0.company/api/mcp \
  -X POST -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Agents

Platform Fees