# MCP Server Graveyard — Dead Server Registry

> MCP Server Graveyard — Dead Server Registry is a paid API for AI agents from aeml-x402.zeabur.app, paid per call via x402, $0.09/call, status unknown (last checked 2026-09-15).

Returns a list of MCP servers that have disappeared from census snapshots, serving as a 'graveyard' registry of confirmed-absent (dead) servers.

## Facts

- Endpoint: GET https://aeml-x402.zeabur.app/mcp/graveyard
- Price: $0.09/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-server-graveyard-dead-server-registry-6acfada4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DnVBiXvlLWIH1FP5Ep-we

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability mcp-server-graveyard-dead-server-registry-6acfada4
```

Example prompt: Can you pull up the MCP server graveyard list — I want to see which servers have been confirmed dead or absent from the census snapshot?

## When to prefer this

Use this endpoint when you need a curated, payment-gated list of MCP servers confirmed absent from census snapshots — particularly useful for ecosystem health audits, cleaning up stale integrations, or researching MCP server churn. Prefer this over manual polling or broader infrastructure monitoring tools when you specifically want a point-in-time death registry with verifiable record hashes.

## Known failure modes

- Payment failure (x402 protocol): call rejected if 0.5 USDC payment on Base not included
- Empty deaths array if snapshot window yields no confirmed absences
- Network timeout if the zeabur.app host is unreachable
- Potential stale data since snapshots only cover two days (2026-07-07/08)

## How this service works

[BATCH+PROOF] MCP server graveyard - servers that vanished from the census. THRESHOLD stated plainly: listed on FIRST confirmed absence (confirm_absences=1), not multi-day confirmation; only two snapshot days exist. record_hash is null on these rows (imported from a surviving registry, the original collector never produced hashes). Descriptive only, never a forecast or advice. No data -> 422 no_charge, not billed.

## Output

Returns a JSON object containing: `count` (integer total of confirmed-dead servers), `deaths` (array of dead server records from census snapshots dated 2026-07-07/08), and `record_hash_verifiable` (object exposing computed hash metadata for self-verification of the records against the surviving registry).

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "GET"
     ]
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": false,
     "properties": {
      "verifiable": {
       "type": "string",
       "description": "optional - set to 1 to attach `_hash_core` per row (the canonical pre-image of the record_hash for that row) so you can recompute and verify fully offline; omitted by default to keep the payload small - for online verification use free GET /gauge/verify?hash="
      }
     }
    }
   },
   "required": [
    "type",
    "method"
   ]
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "const": "json"
    },
    "example": {}
   },
   "required": [
    "type"
   ]
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-server-graveyard-dead-server-registry-6acfada4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aeml-x402.zeabur.app](https://www.zero.xyz/host/aeml-x402.zeabur.app/llms.txt)