mcpdirectory.dev
9,129 servers · updated 23 Sept

Deadends Dev MCP server

community Active last commit 17 d
{
  "mcpServers": {
    "deadends-dev": {
      "command": "uvx",
      "args": [
        "deadends-dev"
      ]
    }
  }
}
file .mcp.json (in your project root)install uvx deadends-devversion 0.9.0

What it does

This server provides structured data about known failure patterns in two areas: coding errors (2,089 entries across 51 domains) and country-specific real-world rules and cultural constraints (250+ entries across 52 countries). It helps AI agents avoid repeating failed approaches and making culturally or legally inappropriate suggestions by returning deterministic, primary-sourced answers instead of hallucinated guidance.

  • Stop an AI agent from suggesting a failed code fix like `sudo pip install` by querying the dead end database and getting the failure rate and correct workaround.
  • Prevent an agent from giving culturally inappropriate advice, such as suggesting tipping in Japan or public displays of affection in the UAE, by checking country-scoped legal and cultural dead ends.
  • Trace error chains to understand that error A leads to error B 78% of the time, allowing an agent to anticipate and handle related failures together.

Tools this server exposes

ToolDoes
query_deadendSearch the dead end database by error type, domain, slug, or country code to retrieve known failure patterns, workarounds, and success rates.
list_domainsReturn all available code and country domains currently covered in the database.
get_country_deadendsRetrieve all dead ends scoped to a specific country code, including legal, cultural, and practical constraints.
report_outcomeSubmit real outcome data to update fix success rates and help improve the database.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.