Skip to content

twentyone million

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

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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.

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://anlyon.dev/api/v1/servers/io.github.21-million-wall/twentyone-million/verify?hash=67cfc3e39bb6f29606ff9ceda1ae818c340459ff7b2a828d0fa641855a5e1558" | jq -e '.changed == false'

Pinned hash 67cfc3e39bb6, from Nov 3, 2026, 11:18 UTC.

Watch

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

https://anlyon.dev/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.dev badge for io.github.21-million-wall/twentyone-million
[![anlyon.dev](https://anlyon.dev/badge/io.github.21-million-wall/twentyone-million.svg)](https://anlyon.dev/servers/io.github.21-million-wall/twentyone-million)

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