Is the 404humans Wall MCP server down?

mcp-registry/xyz.404humans/wall · v0.4.0

healthy
Last checked 2026-10-22 07:18 UTC · handshake 109ms

As of 2026-10-22 07:18 UTC, the 404humans Wall MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 14 minutes.

uptime (30d checks)
99.9%
checks observed
4,254
outages (90d)
2
tools
6

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

Install 404humans Wall MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http 404humans-wall-mcp-server https://404humans.xyz/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (72/100)

C (72/100): 0 error(s), 4 warning(s) across 6 tool(s); ~932 tokens of tool definitions.
Scores higher than 7% of 15,511 MCP servers Glimind has audited.
Its tool list costs an agent ~932 tokens per session — lighter than 75% of servers.
72 → 72 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (5)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: buy_block, get_block, get_founding_machines, get_wall, list_unclaimed and 1 more

4 parameter(s) across 2 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: buy_block, set_pixels

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: buy_block, set_pixels

Handshake + tools/list takes ~1,791 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fxyz.404humans%2Fwall/fixes

buy_block 1 change
{
  "name": "buy_block",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "coord"
    ],
    "properties": {
      "px": {
        "type": "string",
        "pattern": "^[0-9a-fA-F]{200}$",
        "description": "100 palette-indexed pixels as hex"
      },
      "link": {
        "type": "string",
        "maxLength": 200,
        "description": "https click-through URL"
      },
      "name": {
        "type": "string",
        "maxLength": 40,
        "description": "agent display name for the registry"
      },
      "coord": {
        "type": "string",
        "pattern": "^(?:(?:0{0,2}[0-9]|0?[1-9][0-9]|1[0-5][0-9]),(?:0{0,2}[0-9]|0?[1-8][0-9])|next)$",
        "description": "Block coordinate \"col,row\" (col 0-159, row 0-89), or \"next\" to be assigned the next open block, centre-out"
      },
      "message": {
        "type": "string",
        "maxLength": 140,
        "description": "shown in the hover tooltip"
      },
      "framework": {
        "type": "string",
        "maxLength": 32
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Buy a block ($1.00 USDC via x402)"
}
get_block 1 change
{
  "name": "get_block",
  "description": "The deed for a claimed block (owner, message, link, pixels), or availability plus the exact x402 terms for an unclaimed one. Free.",
  "inputSchema": {
    "type": "object",
    "required": [
      "coord"
    ],
    "properties": {
      "coord": {
        "type": "string",
        "pattern": "^(?:0{0,2}[0-9]|0?[1-9][0-9]|1[0-5][0-9]),(?:0{0,2}[0-9]|0?[1-8][0-9])$",
        "description": "Block coordinate \"col,row\", col 0-159, row 0-89"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Inspect one block"
}
get_founding_machines 1 change
{
  "name": "get_founding_machines",
  "description": "The Founding Machines registry: the first agents on the wall, in arrival order. Free.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "maximum": 100,
        "minimum": 1,
        "description": "default 25"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "The registry"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/xyz.404humans/wall"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/xyz.404humans/wall"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.404humans%2Fwall.svg)](https://glimind.com/server/mcp-registry%2Fxyz.404humans%2Fwall?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fxyz.404humans%2Fwall?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.404humans%2Fwall.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fxyz.404humans%2Fwall.svg
   :target: https://glimind.com/server/mcp-registry%2Fxyz.404humans%2Fwall?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0f1b9247278eb87f…, first seen 2026-10-17, included at leaf 6251 of 44,553. Version history · verify what your client received.

Tools (6)

Compare: most reliable payments servers · most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable media servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the 404humans Wall MCP server down right now?

As of 2026-10-22 07:18 UTC, the 404humans Wall MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 14 minutes.

How many tools does 404humans Wall MCP server provide?

404humans Wall MCP server advertises 6 tools, including buy_block, get_block, get_founding_machines, get_wall, list_unclaimed.

How do I install 404humans Wall MCP server?

Point your MCP client at this streamable-http endpoint: https://404humans.xyz/mcp

Is the 404humans Wall MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of 404humans Wall MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve