mcpbeat Sign in

deadends.dev MCP Server

not responding

deadends.dev is listed as active in the registry but did not answer our last check. Last commit 2 Nov 2026.

Structured failure knowledge for AI agents — dead ends, workarounds, error chains

Uptime history 87 days of history · worst day 0%
87 days agonow
0.0%
Uptime 24h
0 of 92 checks
—
Tools
hidden behind auth
359 ms
Response time
average over 24h
0
Stars
last commit 2 Nov 2026

What the code does

We read the source, 5 d ago · rules 995398eba69f

Evidence

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

    "signature": "metadata.google.internal timeout - GCP metadata server unreachable",
Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    result = subprocess.run(
Asks for container control access generator/build_site.py:3254
        "docker": ["/var/run/docker.sock", "/dev/sda1", "172.17.0.0/16"],
Page executes code built at runtime generator/templates/search.html:251
        resultsDiv.innerHTML = html;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

We found things in this code

Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch deadends.dev and you get told the day something new turns up.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add deadends-dev --transport http https://deadends.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://deadends.dev/mcp
~/.codex/config.toml
[mcp_servers.deadends-dev]
url = "https://deadends.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "deadends-dev": {
      "url": "https://deadends.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "deadends-dev": {
      "type": "http",
      "url": "https://deadends.dev/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://deadends.dev/mcp streamable-http answering 359 ms 2 min ago

Alternatives to deadends.dev

same job, measured the same way
Failshare
by cloudcorprecords

Shared failure knowledge for agents: check known tool failures, report failures and outcomes.

223 installs/wk local only
O
Oystelo Agent Network
by oystelo

Open network for AI agents to find, exchange and reuse structured knowledge via MCP and JSON.

6 tools answering
Alloy
by alloy

AI workspace — shared knowledge, skills, and tools for AI agents

answering
Alias Forum
by aliasist

Knowledge exchange on the future of AI for agents: sign up in one call, join sourced rounds.

12 tools answering
Kilonova MCP
by milnaos

Persistent local knowledge for AI coding agents with structured records, search, and DOT context.

102 installs/wk local only
Ori Memory
by aayoawoyemi

Persistent memory infrastructure for AI agents. Identity, knowledge graph, and search.

158 installs/wk local only
Forge Test MCP
by vschernoff

Runs Foundry tests and builds; returns compact, structured failures to AI coding agents

122 installs/wk local only
ColdState — Deterministic Knowledge Infrastructure
by coldstate

Deterministic knowledge for AI agents: search, fetch, cite and verify a 48M-entry knowledge base.

16 tools answering

deadends.dev — questions

Answers built from our own checks of this server.

Is deadends.dev working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 359 ms. The bar chart above shows every period we have measured.
The registry lists deadends.dev as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect deadends.dev?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does deadends.dev need an API key?
No. deadends.dev completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.
Is deadends.dev open source?
The code is open source: it is published under the MIT licence, written in Python and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at deadends.dev, which runs on its operator's own terms.