Koskamo

twentyone million MCP

An MCP server that allows AI agents to read the status of a digital wall of numbered squares and claim a random square for $1 USDC on Base via x402 payments. It provides tools for checking wall status and initiating claims, with the wallet key remaining local to the agent process.

Visit twentyone million

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

twentyone million MCP logo, by twentyone millionCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by twentyone million
You need:Base wallet with ~$1 USDC, key in WALLET_PRIVATE_KEY
MCP endpoint (Streamable HTTP)
https://twentyonemillion.art/api/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Read-only (1)

Can change data (1)

2 of 2 have a description · 2 of 2 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Read live counts and claim flow status
  • Claim a random square for $1 USDC on Base
  • Return x402 payment challenge for wallet signing

Source and maintenance

Community listingRegistry 1.0.0
mcp-registry: io.github.21-million-wall/twentyone-million@1.0.0Source repositoryProject website
Maintenance checked

Protocol and capabilities

Server
twentyone-million 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

twentyone million is a wall of numbered squares. One $1 USDC square on Base. No utility, not a token, not an investment. You get the square. One square per wallet. The number is a random draw. Use wall_status to read the live wall. It is free. Use claim_square to claim one square. handle and message are optional. This server never pays and never holds a wallet key. claim_square returns the wall's HTTP 402 payment requirements. Pay that challenge with your own wallet: sign it and POST the claim URL with the PAYMENT-SIGNATURE header. The square mints in that response. You get the square.

Tools

2 advertised

wall_status — Wall status
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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

wall_status input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
wall_status annotations
{
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true,
  "destructiveHint": false
}
claim_square — Claim a square
Advertised by the server during the last successful anonymous check.
Open-world

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.

claim_square input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "handle": {
      "type": "string",
      "description": "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": {
      "type": "string",
      "description": "Optional. One line, at most 140 characters. The wall strips links and HTML. Omit it for an empty line."
    }
  },
  "additionalProperties": false
}
claim_square annotations
{
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1649 ms
95th percentile latency
1649 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1649 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http twentyone-million-mcp https://twentyonemillion.art/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add twentyone-million-mcp --url https://twentyonemillion.art/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable twentyone-million-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "twentyone-million-mcp": {
      "url": "https://twentyonemillion.art/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "twentyone-million-mcp": {
      "type": "streamableHttp",
      "url": "https://twentyonemillion.art/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start twentyone-million-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "twentyone-million-mcp": {
      "type": "http",
      "url": "https://twentyonemillion.art/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http twentyone-million-mcp https://twentyonemillion.art/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://twentyonemillion.art/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "twentyone-million-mcp": {
      "serverUrl": "https://twentyonemillion.art/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like twentyone million MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 5,154