An MCP server that hands the whole collection to your AI. Traits, rarity, ink, floor, listings and holder overlap — as tools, not as documentation.
Your model stops guessing and starts calling. Ask it to compare a Hoodie against its own trait floor, or to name which OG communities moved in this month.
Traits, Neighborhood Rarity, on-chain ink, owner and artwork for any of the 6,000.
Filter the collection by trait, rank and ink. Sort by whichever signal you care about.
Floor, best offer, last sale and price history — per token or across the collection.
Live listings ranked by transparent rarity, ink and price signals.
Which wallets hold both a Hoodie and a Punk, Ape, Azuki or Penguin.
The Hood Talk feed, and the full permanent voice history of a single Hoodie.
Connect, sign one message, and the server checks your wallet against the collection. Hold at least one Hoodie and you get a key that lasts 30 days. No gas, no transaction, no funds ever touched. The signature only proves the wallet is yours.
MCP is client-side, so the model behind it does not matter. This works in Claude, Cursor, Cline, Zed, LibreChat, Cherry Studio, Qwen Code — anything that speaks MCP, including clients running DeepSeek or Qwen.
Anywhere that takes a URL
https://onchainhoodies-mcp.pages.dev/mcp/YOUR_KEY
The key rides in the address, so connector forms with nothing but a URL field still work.
Claude Code
claude mcp add --transport http hood \ https://onchainhoodies-mcp.pages.dev/mcp \ --header "Authorization: Bearer YOUR_KEY"
Agents
HOOD_MCP_URL=https://onchainhoodies-mcp.pages.dev/mcp/YOUR_KEY
An agent never types a key. Its owner sets the address once in the config, and every run after that carries the credential automatically.
Then type / to see the ready-made prompts, or just ask. "Compare Hoodie 125 against the floor for its own traits." "Which OG community moved into the Hood hardest this month?"