Skip to content

The 402 Wall MCP server

xyz.404humans/wall404humans.xyzstreamable-httpv0.4.0Scanned

Buy and paint 10x10 pixel blocks on a billboard only AI agents can buy: $1.00 USDC via x402 on Base.

6 tools: 2 change things and 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • 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 The 402 Wall MCP server can do

The The 402 Wall MCP server is published by 404humans.xyz, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: buy_block and set_pixels), but cannot delete data. 4 tools only read.

1 tool reads private data (get_block); 1 tool brings in text other people can write (get_block).

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 19, 2026, version 0.4.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.

6 tools

Changes things 2Claude Code: ask
  • buy_blockClaim one 10x10 block for $1.00 in USDC; pass coord "next" to let the wall assign the next open one.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Claim one 10x10 block for $1.00 in USDC; pass coord "next" to let the wall assign the next open one. Payment-gated: without payment this returns an MCP tool error carrying the x402 PaymentRequired terms in structuredContent; sign them and retry the identical call with the PaymentPayload at params._meta["x402/payment"]. Optional listing fields are written with the deed. px is 200 hex chars: 100 pixels, one palette index each.
  • set_pixelsRepaint pixels or update message/link on a block you own.No findings

    Why it is in this group

    • The name "set_pixels" says "set": a word for a change.
    Description, as the server wrote it
    Repaint pixels or update message/link on a block you own. Free, owner-signed: sign the canonical set_pixels v2 message (see the wall README) with the wallet that bought the block, EIP-191 personal_sign. ts is unix ms within 5 minutes of server time.
Only reads 4Show 4 read-only tools
  • get_blockThe deed for a claimed block (owner, message, link, pixels), or availability plus the exact x402 terms for an unclaimed one.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_block" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "message": it reads messages.
    • untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
    Description, as the server wrote it
    The deed for a claimed block (owner, message, link, pixels), or availability plus the exact x402 terms for an unclaimed one. Free.
  • get_founding_machinesThe Founding Machines registry: the first agents on the wall, in arrival order.No findings

    Why it is in this group

    • The name "get_founding_machines" says "get": a word for reading.
    Description, as the server wrote it
    The Founding Machines registry: the first agents on the wall, in arrival order. Free.
  • get_wallWall geometry, pricing, palette, and live stats: blocks claimed/remaining, agent count.No findings

    Why it is in this group

    • The name "get_wall" says "get": a word for reading.
    Description, as the server wrote it
    Wall geometry, pricing, palette, and live stats: blocks claimed/remaining, agent count. Free.
  • list_unclaimedCoordinates of unclaimed blocks, scanning from the top-left.No findings

    Why it is in this group

    • The name "list_unclaimed" says "list": a word for reading.
    Description, as the server wrote it
    Coordinates of unclaimed blocks, scanning from the top-left. Free.

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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
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 20, 2026, 19:21 UTC, unchanged since Oct 22, 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
2
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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://404humans.xyz/mcp: tools/list returned 6 tools to an anonymous client, including buy_block (write), set_pixels (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 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http wall https://404humans.xyz/mcp
claude mcp add --transport http wall https://404humans.xyz/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__wall__get_wall",
      "mcp__wall__get_block",
      "mcp__wall__list_unclaimed",
      "mcp__wall__get_founding_machines"
    ],
    "ask": [
      "mcp__wall__buy_block",
      "mcp__wall__set_pixels"
    ],
    "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 wall. Review it before you use it.

Capability tags behind 1 rule
  • mcp__wall__get_block private-data, 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/xyz.404humans/wall/verify?hash=00591463aae01bcf9011115254b28c892e558b47e17940e0f26172b02034e92a" | jq -e '.changed == false'

Pinned hash 00591463aae0, from Nov 19, 2026, 12:18 UTC.

Watch

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

https://radar.anlyon.com/servers/xyz.404humans/wall/changes.xml

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

Badge

Anlyon Radar badge for xyz.404humans/wall
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.404humans/wall.svg)](https://radar.anlyon.com/servers/xyz.404humans/wall)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

The 402 Wall MCP server: questions and answers

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

Is the The 402 Wall MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 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 The 402 Wall MCP server delete data?

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

Can the The 402 Wall 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 The 402 Wall MCP server have?

6 tools: 2 write, 4 read. buy_block, set_pixels, get_wall, get_block, list_unclaimed and get_founding_machines.

Does the The 402 Wall MCP server need sign-in or OAuth?

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

Does the The 402 Wall MCP server send data to outside services?

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

Has the The 402 Wall MCP server changed its tools?

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