Skip to content

twentyone million MCP server

io.github.21-million-wall/twentyone-million21-million-wallstreamable-httpv1.0.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the twentyone million MCP server can do

The twentyone million MCP server is published by the GitHub account 21-million-wall. It has 2 tools. It can create or change data (1 tool: claim_square), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (wall_status and claim_square).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • claim_squareClaim one square on the twentyone million wall.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • wall_statusRead the live status of the twentyone million wall.Reads text others writeNo findings

    Why it is in this group

    • The name "wall_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read the live status of the twentyone million wall. Free. No wallet and no payment. Returns the JSON from /api/status.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://twentyonemillion.art/api/mcp: tools/list returned 2 tools to an anonymous client, including claim_square (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__twentyone-million__wall_status"
    ],
    "ask": [
      "mcp__twentyone-million__claim_square"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as twentyone-million. Review it before you use it.

Capability tags behind 2 rules
  • mcp__twentyone-million__wall_status untrusted-input
  • mcp__twentyone-million__claim_square untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.21-million-wall/twentyone-million/verify?hash=67cfc3e39bb6f29606ff9ceda1ae818c340459ff7b2a828d0fa641855a5e1558" | jq -e '.changed == false'

Pinned hash 67cfc3e39bb6, from Nov 16, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.21-million-wall/twentyone-million/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.21-million-wall/twentyone-million
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.21-million-wall/twentyone-million.svg)](https://radar.anlyon.com/servers/io.github.21-million-wall/twentyone-million)

Source: MCP Registry · repository. Synced Nov 3, 2026, 11:17 UTC.

twentyone million MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the twentyone million MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the twentyone million MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the twentyone million MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the twentyone million MCP server have?

2 tools: 1 write, 1 read. claim_square and wall_status.

Does the twentyone million MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the twentyone million MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the twentyone million MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.