twentyone million MCP Server

by 21-million-wall Your server? Claim it

not responding

twentyone million is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Read the wall and claim one $1 USDC square on Base. No utility, not a token or investment.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 5 days of history · worst day 0%

5 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

226 ms

Response time

average over 24h

open, no key

Access

streamable-http

twentyone million does not always answer

Over the last week it answered 5.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add twentyone-million --transport http https://twentyonemillion.art/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://twentyonemillion.art/api/mcp

~/.codex/config.toml

[mcp_servers.twentyone-million]
url = "https://twentyonemillion.art/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "twentyone-million": {
      "url": "https://twentyonemillion.art/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "twentyone-million": {
      "type": "http",
      "url": "https://twentyonemillion.art/api/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

claim

claim_square

Claim one square on the twentyone million wall. $1 USDC on Base, paid over x402 by your own wallet. This server does not pay and does not hold a key. The result is the wall's HTTP 402 payment requirements for the claim URL. Sign that challenge and retry the claim POST with the PAYMENT-SIGNATURE header. On success the JSON includes number and tile. handle and message are optional. One square per wallet. The number is a random draw. No utility, not a token, not an investment. You get the square.

wall

wall_status

Read the live status of the twentyone million wall. Free. No wallet and no payment. Returns the JSON from /api/status.

Endpoints

URL	Transport	State	Latency	Checked
https://twentyonemillion.art/api/mcp	streamable-http	answering	226 ms	2 min ago

Alternatives to twentyone million

same job, measured the same way

Cybercentry Verification

by co-cybercentry

Twelve tools: token, wallet, contract and site security. Two free, the rest $1 in USDC over x402.

14 tools answering

Cellionaire

by cellionaire

Read the 1000x1000 Cellionaire pixel wall and create USDC orders for cells; you pay on-chain.

6 tools answering

100pro Token Risk

by rendraputra

Read-only risk tools: token screen, contract source, wallet. $0.10 USDC on Base.

3 tools answering

MACH Base

by thealiphant

Investigate Base transactions, check wallet funds and contracts. Read-only MCP. USDC via x402.

18 tools answering

AgentUtility Retail

by agentutility

MCP server for the @agentutility retail cluster — pay-per-call x402 tools, no API keys, USDC on…

115 installs/wk local only

Databroker

by mossforge

Pay-per-call UK MOT history, reliability analytics and identifier utilities. x402 USDC on Base.

52 installs/wk local only

AgentUtility Wordmint

by agentutility

MCP server for the @agentutility wordmint cluster — pay-per-call x402 tools, no API keys, USDC on…

134 installs/wk local only

AgentUtility Bestiary

by agentutility

MCP server for the @agentutility bestiary cluster — pay-per-call x402 tools, no API keys, USDC on…

72 installs/wk local only

twentyone million — questions

Answers built from our own checks of this server.

What can twentyone million do?

It exposes 2 tools, read directly from the server on our last check. Among them: claim_square, wall_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is twentyone million working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 226 ms. The bar chart above shows every period we have measured.

Is twentyone million still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

The registry lists twentyone million as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect twentyone million?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does twentyone million need an API key?

No. twentyone million completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.