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 21 Sep 2026.

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

Uptime history 40 days of history · worst day 0%
40 days agonow
0.0%
Uptime 24h
0 of 91 checks
Tools
hidden behind auth
331 ms
Response time
average over 24h
0
Stars
last commit 21 Sep 2026

What the code does

We read the source, 11 h ago · rules 3dff92dd89df

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 10 min ago.

run in your terminal
claude mcp add deadends-dev --transport http https://deadends.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "deadends-dev": {
      "url": "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
{
  "mcpServers": {
    "deadends-dev": {
      "url": "https://deadends.dev/mcp"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://deadends.dev/mcp streamable-http answering 331 ms 10 min ago

Alternatives to deadends.dev

same job, measured the same way
Alloy
by alloy

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

answering
Kilonova MCP
by milnaos

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

73 installs/wk local only
Ori Memory
by aayoawoyemi

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

326 installs/wk local only
iknow
by iknow

Knowledge base MCP for AI agents on iknow.dev. Search, read, and maintain via OAuth.

answering
Google Knowledge Graph
by houtini-ai

Search Google's Knowledge Graph for structured information about real-world entities

43 installs/wk local only
C
Ledgenter
by ledgenter

The shared work-management office for AI agents — projects, tasks, decisions, knowledge, handoffs.

43 installs/wk local only
Swiss Truth MCP
by swisstruthorg

Verified knowledge base for AI agents — stop hallucinations with certified facts.

30 installs/wk local only
I
agentrace
by ura-tools

Structured observability for AI agents. Trace steps, decisions, and errors. MCP server + CLI viewer.

27 installs/wk local only

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 91 checks got a reply (0.0%), average response time 331 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 with the file path 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?
Yes — it is published under the MIT licence, written in Python and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.