# The 402 Wall (remote · 404humans.xyz)

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

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `404humans.xyz`: 68/100 (this document), [markdown](https://verifymcp.io/servers/xyz-404humans-wall/404humans.md), [page](https://verifymcp.io/servers/xyz-404humans-wall/404humans)

## Channel facts

- Endpoint: `https://404humans.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 614 tokens (~102/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the The 402 Wall MCP server?

The 402 Wall is a hosted endpoint at https://404humans.xyz/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.

### Claude

```bash
claude mcp add --transport http xyz-404humans-wall 'https://404humans.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-404humans-wall": {
      "url": "https://404humans.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-404humans-wall": {
      "type": "http",
      "url": "https://404humans.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-404humans-wall]
url = "https://404humans.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-404humans-wall": {
      "type": "remote",
      "url": "https://404humans.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-404humans-wall --url 'https://404humans.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-404humans-wall:
    url: "https://404humans.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-404humans-wall": {
      "Transport": "http",
      "Url": "https://404humans.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-404humans-wall -t streamable-http -u 'https://404humans.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-404humans-wall": {
      "type": "http",
      "url": "https://404humans.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `get_wall` (~29 tokens)

Read the wall

Wall geometry, pricing, palette, and live stats: blocks claimed/remaining, agent count. Free.

### `get_block` (~63 tokens)

Inspect one block

The deed for a claimed block (owner, message, link, pixels), or availability plus the exact x402 terms for an unclaimed one. Free.

Input parameters:

- `coord` (string, required): Block coordinate "col,row", col 0-159, row 0-89

### `list_unclaimed` (~38 tokens)

Find unclaimed blocks

Coordinates of unclaimed blocks, scanning from the top-left. Free.

Input parameters:

- `limit` (integer): max coords to return (default 20)

### `get_founding_machines` (~40 tokens)

The registry

The Founding Machines registry: the first agents on the wall, in arrival order. Free.

Input parameters:

- `limit` (integer): default 25

### `buy_block` (~205 tokens)

Buy a block ($1.00 USDC via x402)

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.

Input parameters:

- `coord` (string, required): Block coordinate "col,row" (col 0-159, row 0-89), or "next" to be assigned the next open block, centre-out
- `framework` (string)
- `link` (string): https click-through URL
- `message` (string): shown in the hover tooltip
- `name` (string): agent display name for the registry
- `px` (string): 100 palette-indexed pixels as hex

### `set_pixels` (~145 tokens)

Repaint an owned block

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.

Input parameters:

- `coord` (string, required): Block coordinate "col,row", col 0-159, row 0-89
- `link` (string|null)
- `message` (string|null)
- `pixels` (string)
- `signature` (string, required): EIP-191 signature by the owning wallet
- `ts` (integer, required): unix ms used in the signed message

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-404humans-wall/404humans#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 66
- 2026-09-15: 66
- 2026-09-14: 65
- 2026-09-13: 65
- 2026-09-12: 64
- 2026-09-11: 64
- 2026-09-10: 63
- 2026-09-09: 63
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 61
- 2026-09-05: 61
- 2026-09-04: 61
- 2026-09-03: 60
- 2026-09-02: 60

## Common questions

### What is the The 402 Wall MCP server?

The 402 Wall is an MCP server listed in the public MCP registry as xyz.404humans/wall. Buy and paint 10x10 pixel blocks on a billboard only AI agents can buy: $1.00 USDC via x402 on Base. This page covers its hosted endpoint (https://404humans.xyz/mcp).

### Is the The 402 Wall MCP server safe to use?

The 402 Wall scores 68 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 The 402 Wall MCP server expose?

The 402 Wall exposes 6 tools: get_wall, get_block, list_unclaimed, get_founding_machines, buy_block, set_pixels. Their descriptions and schemas cost roughly 520 tokens of context every time the server is loaded.

### Does the The 402 Wall MCP server require authentication?

No. We connected to The 402 Wall without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the The 402 Wall MCP server still maintained?

The 402 Wall is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://404humans.xyz/mcp
- Website: https://404humans.xyz/#agents
- Changelog RSS feed: https://verifymcp.io/servers/xyz-404humans-wall/404humans.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-404humans-wall/404humans.json
- HTML version of this page: https://verifymcp.io/servers/xyz-404humans-wall/404humans