MCP.Market

deadends.dev MCP server

online · 100% uptime
by deadends.dev·dev.deadends/deadends-dev·v0.9.0
No reviews yet

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

C65/100grade C
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
Growing

0 stars40 downloads/wk

Reviews

Write one

Nobody has reviewed deadends.dev yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

deadends.dev tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

1 high1 medium
  • Code scan1500 source files scanned20/25
  • Live reliabilityremote unreachable: Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> </body> </html>0/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (2)

  • highRemote endpoint did not respondreliability.unreachable

    Streamable HTTP error: Error POSTing to endpoint: <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> </body> </html>

  • mediumeval / new Function usedexec.eval
    deadends_dev-0.9.0/data/canons/data/json-trailing-comma-parse-error/json-parser-any.json: …": "" }, { "action": "Use eval() or Function() to parse JSON with trail…
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How deadends.dev compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,019 ms
faster than 11% of 30,031 servers
Downloads a week
40
more than 31% of 12,191 servers with a package

Install deadends.dev in Claude Code, Cursor or VS Code

claude mcp add --transport http deadends-dev https://deadends.dev/mcp
Add to Cursor

What the publisher says

From the deadends.dev repository's README, as published. We do not edit it. Read it on GitHub

deadends.dev

<!-- mcp-name: dev.deadends/deadends-dev -->

Stop AI agents from repeating known failures - in code AND in the real world.

AI assistants reliably fumble two kinds of problems: known-failed code fixes, and country-specific real-world rules they've never been exposed to in training. deadends.dev now covers both:

hits ModuleNotFoundError, CUDA OOM, CrashLoopBackOff, etc.

  • Code errors (2,089 entries, 51 domains): what NOT to try when an agent

(ETA/eVisitor, NZeTA, e-visas, arrival cards), banking requirements, legal red lines (lèse-majesté, §86a, Article 301), cultural taboos (chopsticks in rice, clock gifts in China, red-ink names in Korea), food safety (tap-water safety by country), emergency numbers, driving norms (left-hand traffic), housing contracts - all the friction where a plausible-sounding global answer is wrong locally.

  • Country-scoped dead ends (250+ entries across 52 countries): visa rules

Why the expansion? Coding dead ends are largely solved by a good LLM.

Country-specific friction - Japanese hanko requirements, Schengen 90/180

math, Ramadan business hours, Saudi alcohol ban, Indian beef taboos - is

where generic AI advice breaks hardest. The codebase and schema are

identical; the env segment just carries a country code.

90% Precision@1 · 0.935 MRR · Data Quality Dashboard

Website: deadends.dev · MCP Server: Smithery · PyPI: deadends-dev · API: /api/v1/index.json

Repository: https://github.com/dbwls99706/deadends.dev

Why Use This?

What makes this different from asking an LLM?

code (kr, jp, us, de...) so the same taboo can be answered differently for different jurisdictions.

  • Deterministic: Same query → same answer, every time. No hallucination.
  • Country-scoped: ID format {domain}/{slug}/{env} - env holds the country

or verifiable reporting. No "based on general knowledge" answers.

  • Primary-sourced: Every country canon cites government sites, embassies,
  • Community-validated: Fix success rates updated from real outcome reports.
  • Sub-millisecond: Local regex matching, no API roundtrip.

현실적인 한계 (운영 관점)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

deadends.dev: common questions

Is deadends.dev MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the deadends.dev safety report
How do I install deadends.dev?
It runs remotely at deadends.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does deadends.dev need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is deadends.dev maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v0.9.0.
Is deadends.dev up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does deadends.dev compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,019 ms (faster than 11% of 30,031 servers). Full comparison.