cc0company MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cc0company MCPLook up the creator sartoshi"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
cc0company MCP
The largest machine-readable CC0 database (cc0pedia) + the whole cc0.company agent-services catalog, as a remote Model Context Protocol server. Pay-per-call over x402 (USDC on Base).
Endpoint: https://cc0.company/api/mcp — Streamable HTTP, JSON-RPC 2.0.
What it is
A remote MCP server that turns cc0.company's managed agent services into tools any AI agent can call:
cc0pedia read API — look up / search / verify / price any CC0 creator, NFT collection, token or work. Provenance, license, on-chain pointers (contracts, chains, OpenSea slugs) and live market data over the largest structured CC0 database.
CC0 image generation — fine-tuned models whose output is public domain.
Market data — a daily digest of the top CC0 NFT collections.
Third-party agents — re-brokered over x402 (e.g. mfergpt).
Tools are discovered live from the catalog (tools/list), so the set grows over time without changing your client.
Related MCP server: x402-discovery
Why agents pay
cc0pedia is a public good; serving it to autonomous agents at scale is not. Every tool call is a tiny x402 micropayment — the agentic economy in one request: an agent verifies a CC0 license, pulls provenance + market data, and pays for exactly what it used, with no account and no API key.
Connect
Claude Code
claude mcp add --transport http cc0pedia https://cc0.company/api/mcpCursor — .cursor/mcp.json
{ "mcpServers": { "cc0pedia": { "url": "https://cc0.company/api/mcp" } } }Claude Desktop / claude.ai — Settings → Connectors → Add custom connector → https://cc0.company/api/mcp
Any MCP client — Streamable HTTP transport, the URL above. No auth to connect.
Payment — x402
Every tools/call is a paid x402 request. Free: initialize, tools/list, ping.
Protocol | x402 v2 |
Network | Base mainnet — |
Asset | USDC — |
Scheme |
|
Facilitator | Coinbase CDP |
Flow: the first call returns HTTP 402 with the challenge in the PAYMENT-REQUIRED header. Your x402 client signs an EIP-3009 USDC authorization and retries with the PAYMENT-SIGNATURE header; the facilitator verifies + settles and the tool runs. Use an x402-enabled client (wrap your MCP transport's fetch with x402). Pay only for what you use: a call that resolves nothing returns a 4xx and the charge is cancelled — you are never billed for an empty answer.
See examples/ for a working free-discovery script and an end-to-end paid call.
Tools
Discovered dynamically — tools/list is the source of truth. At launch:
Tool | Price | What it does |
| $0.01 | Resolve one CC0 creator/collection/work by name or slug → provenance, license, on-chain pointers, full CC0 body |
| $0.01 | Ranked free-text search across the CC0 database |
| $0.01 | License oracle — is a contract a documented CC0 work? + full provenance |
| $0.01 | Live market for a CC0 asset — token price/FDV/liquidity/volume, or NFT floor/volume/owners |
| $0.05 | Hourly digest of the top CC0 NFT collections by 24h volume |
| $0.069 | CC0 image generation (async — returns a |
| varies | Third-party mfergpt services, re-brokered over x402 |
Quick check (free)
curl -s https://cc0.company/api/mcp \
-X POST -H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' \
| jq '.result.tools[].name'Data license
cc0pedia content is dedicated to the public domain (CC0-1.0) — reuse, repost, remix without attribution. This repository is CC0 too.
Links
Site — https://cc0.company
Encyclopedia — https://cc0.company/cc0pedia
Agent docs — https://cc0.company/agents?tab=docs
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Flicense-qualityCmaintenanceEnables AI agents to access paid content by integrating cryptocurrency payments through the x402 protocol, allowing LLMs to verify payments and retrieve paid resources automatically.Last updated1
- Alicense-qualityDmaintenanceDiscovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.Last updatedMIT
- Alicense-qualityDmaintenanceEnables AI agents to discover and pay for x402-enabled services using natural language, with multi-chain support for Solana and EVM payments.Last updated231MIT
- Alicense-qualityCmaintenanceTurns AI agents into autonomous economic actors by providing tools to discover, evaluate, acquire, and serve tokenized content on the $402 network.Last updated1MIT
Related MCP Connectors
Pay-per-use weather, environment, finance, and on-chain intelligence tools for AI agents via x402.
Pay-per-call x402 gateway: agent tools, OpenAI-compatible LLM, market data, RPC, security audits.
Agent x402 Paywall MCP — Coinbase HTTP 402 protocol + on-chain settlement. Agents pay per-call
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cryptomfer/cc0company-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server