twentyone million
REMOTE · TWENTYONEMILLION.ART
Read the wall and claim one $1 USDC square on Base. No utility, not a token or investment.
Available components
Last scanned (57 minutes ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 370 tokens (~185/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://twentyonemillion.art/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=twentyonemillion.art | CN=YR1,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 665ce8844cdc6198d897ad0f1d1ac16b553 |
| SANs: twentyonemillion.art | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of twentyonemillion.art. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| art. | present | 29485, 32002 | 8, 8 | Verified |
| twentyonemillion.art. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://twentyonemillion.art/api/mcp | Verified | 200 | |
| http (plaintext) | http://twentyonemillion.art/api/mcp | HTTPS enforced | 308 | https://twentyonemillion.art/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claim_square Claim a square ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | – | Optional. 1 to 30 characters: letters, numbers, underscore, or hyphen. A leading @ is allowed. Omit it and the wall assigns a short handle from the paying address. |
| message | string | – | Optional. One line, at most 140 characters. The wall strips links and HTML. Omit it for an empty line. |
No output schema declared.
No examples provided.
wall_status Wall status ~35
Read the live status of the twentyone million wall. Free. No wallet and no payment. Returns the JSON from /api/status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the twentyone million MCP server?
twentyone million is a hosted endpoint at https://twentyonemillion.art/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · twentyonemillion.art
claude mcp add --transport http 21-million-wall-twentyone-million 'https://twentyonemillion.art/api/mcp'
What is the twentyone million MCP server?
twentyone million is an MCP server listed in the public MCP registry as io.github.21-million-wall/twentyone-million. Read the wall and claim one $1 USDC square on Base. No utility, not a token or investment. This page covers its hosted endpoint (https://twentyonemillion.art/api/mcp).
Is the twentyone million MCP server safe to use?
twentyone million scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the twentyone million MCP server expose?
twentyone million exposes 2 tools: wall_status, claim_square. Their descriptions and schemas cost roughly 234 tokens of context every time the server is loaded.
Does the twentyone million MCP server require authentication?
No. We connected to twentyone million without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the twentyone million MCP server still maintained?
twentyone million is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.