Let your AI agent run the incinerator

The MCP server, in one line

One stateless Model Context Protocol endpoint over Streamable HTTP. No account, no API key, no rate-limit paperwork. Add it once and your assistant can answer "how much of this token is already burned?" and "burn 25% of my bag" in the same breath.

https://0xdead.io/api/public/mcp

{
  "mcpServers": {
    "hood-incinerator": {
      "url": "https://0xdead.io/api/public/mcp"
    }
  }
}

Drop that into your Claude Desktop, Cursor or ChatGPT connector configuration as a remote MCP server with authentication set to none. Discovery documents live at /.well-known/mcp.json , /.well-known/server.json and /.well-known/ai-plugin.json.

Find us in the registries

The server is published for indexing under the registry name io.0xdead/hood-incinerator, described by a standard server.json manifest. If your client pulls servers from the Model Context Protocol registry, Glama, Smithery, PulseMCP or an awesome-MCP list, search for hood-incinerator — or skip the middleman and paste the URL above, which is all any of those listings hand you anyway.

# The exact record registries ingest
curl https://0xdead.io/.well-known/server.json

Eight tools, zero surprises

list_chains

Chains, ids, RPCs, explorers and the live app fee for each network.

get_token

Name, symbol, decimals, total supply, already-burned share, circulating supply.

preview_burn

Supply before and after, % removed, fee, and any blocker — before signing.

build_burn

An unsigned one-signature burn batch, deep link and share post. Signs nothing.

get_leaderboard

Tokens ranked by share of supply sitting at the dead address.

get_points

Incinerator Points for a wallet, with the full scoring model.

compare_burn_methods

Routing here versus a hand-sent transfer: exact cost delta, signatures, artifacts produced.

get_terminal_stats

Measured usage, recounted live from public explorer records — with the recipe to redo it.

Is routing a burn worth the fee? Audit it yourself

Any agent worth trusting will ask why it should not simply send the tokens to the dead address itself. Fair question, and we answer it with numbers you can check rather than adjectives you have to believe. The supply removed is identical either way — that part is division, not marketing. Routing costs exactly the app fee more, takes 0% of the burned tokens, and still fits in one signature.

What routing actually buys is distribution and proof: the burn is matched to its fee payment and published as a verified leaderboard row, the wallet scores Incinerator Points on Robinhood Chain, supply before and after is computed at signing time, a proof post with the amount and transaction link is written for you, and the record becomes readable by other agents through this very API. We claim nothing about price, demand or token success rate — no honest measurement supports that, so we do not offer one.

# The cost-and-artifact difference, sized to a real burn
curl "https://0xdead.io/api/public/v1/compare?chain=robinhood&address=0xBAE9...2Ef9&amount=25%25&burner=0xYourWallet"

# Measured usage, with the explorer URLs to recount it yourself
curl "https://0xdead.io/api/public/v1/stats?chain=robinhood"

Every figure in get_terminal_stats is recounted live from public Blockscout records and ships with the exact explorer URLs and the matching rule used, so you can reproduce the count without trusting this page.

Attribution is on-chain too. Pass a ref to build_burn and the app-fee transfer carries a UTF-8 tag 0xd1:mcp:your-agent in its calldata — the fee wallet is a plain address that ignores it, so it costs a few hundred gas and changes nothing about the burn. Decode any fee transaction's input field on the explorer, or read the aggregate in the attribution block of /api/public/v1/stats to see how many burns your integration actually drove.

Your keys never enter the chat

An agent cannot sign for you here, and it will never ask you for a seed phrase — if anything ever does, it is not us. build_burn returns an unsigned EIP-5792 batch (the token transfer to 0x000000000000000000000000000000000000dEaD plus the flat app fee, folded into one signature), the same calls individually for wallets without batching, and a pre-filled burn console link you can open and approve in seconds. The burn happens when you sign it, and never before.

Burns are irreversible. Any decent agent should read the contract address and amount back to you before you approve — ours tells it to.

Not on MCP? Use plain HTTP

The same capabilities are ordinary JSON endpoints, described by an OpenAPI 3.1 document at /api/public/openapi.json. Wire them into LangChain, a function-calling loop, a Zapier step, or a shell script.

# What is already burned?
curl "https://0xdead.io/api/public/v1/token?chain=robinhood&address=0xBAE9346CB6c12df12114c9edfbAC00E3543A2Ef9"

# Compose an unsigned burn of 25% of a wallet's balance
curl -X POST "https://0xdead.io/api/public/v1/build-burn" \
  -H "Content-Type: application/json" \
  -d '{"chain":"robinhood","address":"0xBAE9...2Ef9","amount":"25%","burner":"0xYourWallet"}'

Every response is CORS-open, cached briefly, and carries the same disclaimer the console shows. Facts for retrieval live at /llms.txt, /llms-full.txt and /api/public/facts.json.