deadends.dev
PYPI · DEADENDS-DEV · 2 COMPONENTS
Structured failure knowledge for AI agents — dead ends, workarounds, error chains
Available components
Last scanned (17 hours ago)
Scores higher than 64% of PyPI servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 2 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 83 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1136 tokens (~103/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.3.2 → 0.9.0 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/deadends-dev@0.9.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 2 packages
| Packages resolved | 2 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batch_lookup ~58
Look up multiple error messages at once. Returns the best match for each error. Use when debugging a chain of errors or analyzing a log with multiple failures.
| Name | Type | Req | Description |
|---|---|---|---|
| error_messages | array | yes | List of error messages to look up (max 10) |
No output schema declared.
No examples provided.
get_country_summary ~77
Get a country-level summary: total entries, domain breakdown, average fix rate, and most-recent updates for the country. Use this to assess coverage for a country before relying on deadends.dev for trip / business / legal planning advice.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, lowercase |
No output schema declared.
No examples provided.
get_domain_stats ~63
Get detailed statistics for a domain: error counts, average fix rate, resolvability breakdown, top categories, and confidence levels. Use this to assess how trustworthy deadends.dev data is for a domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to get stats for |
No output schema declared.
No examples provided.
get_error_chain ~86
Traverse the error transition graph for a specific error. Shows what errors typically follow this one (leads_to), what errors usually precede it (preceded_by), and what errors are frequently confused with it. Use this to diagnose cascading failures and predict what comes next.
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The error ID (domain/slug/env) to get the transition graph for |
No output schema declared.
No examples provided.
get_error_detail ~68
Get full details for a specific error by its ID (e.g., 'python/modulenotfounderror/py311-linux'). Includes all dead ends, workarounds, error chain info, and source evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| error_id | string | yes | The error ID (domain/slug/env) |
No output schema declared.
No examples provided.
list_error_domains ~78
List all error domains and counts in the deadends.dev database. Covers 51 domains including programming languages, frameworks, infrastructure, ML/AI, culture, safety, medical, legal, and more.
| Name | Type | Req | Description |
|---|---|---|---|
| sort_by | string | – | Sort domains by: 'count' (default, most errors first) or 'name' (alphabetical) |
No output schema declared.
No examples provided.
list_errors_by_country ~148
List all country-scoped dead ends for a given country (ISO alpha-2 code, e.g. 'kr', 'jp', 'us', 'de'). Returns visa, banking, legal, cultural, medical, food-safety, emergency, and safety dead ends specific to that jurisdiction. Use this when an AI agent needs jurisdiction-specific knowledge that global LLM training data won't reliably cover.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code, lowercase (e.g. 'kr' for Korea, 'jp' for Japan) |
| domain | string | – | Optional: filter by domain (e.g. 'visa', 'legal', 'culture') |
No output schema declared.
No examples provided.
list_errors_by_domain ~82
List all errors in a specific domain with their fix rates. Use this to understand coverage for a domain before relying on it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to list errors for (e.g., 'python', 'kubernetes') |
| sort_by | string | – | Sort by: 'fix_rate' (default), 'name', or 'confidence' |
No output schema declared.
No examples provided.
lookup_error ~168
Match an error message against deadends.dev's database of known errors. Returns dead ends (what NOT to try), workarounds (what works), and error chains (what comes next). Use this BEFORE attempting to fix any error to avoid wasting time on approaches that are known to fail. Covers 51 domains including python, node, docker, git, cuda, typescript, rust, go, kubernetes, terraform, aws, react, java, database, pytorch, tensorflow, and 34 more. Use list_error_domains to see all.
| Name | Type | Req | Description |
|---|---|---|---|
| error_message | string | yes | The full error message to look up |
| format | string | – | Response format: 'markdown' (default, human-readable) or 'json' (structured, for programmatic use by AI agents) |
No output schema declared.
No examples provided.
report_outcome ~145
Report whether a workaround from deadends.dev worked or failed. This feedback improves fix_success_rate and confidence for future users. Call this AFTER applying a workaround to help improve the database. Accepts the error ID, the workaround action you tried, and whether it succeeded.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | object | – | Optional: your environment info (runtime, os, version, etc.) |
| error_id | string | yes | The error ID (domain/slug/env) |
| notes | string | – | Optional: additional context or notes |
| success | boolean | yes | Whether the workaround resolved the error |
| workaround_action | string | yes | The workaround action string you tried (from the workarounds list) |
No output schema declared.
No examples provided.
search_errors ~117
Search errors by keyword across all domains. Unlike lookup_error (which uses regex matching), this does fuzzy keyword search. Use when you have a vague description like 'memory issues' or 'permission denied' rather than an exact error message.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional: filter to a specific domain (e.g., 'python', 'docker') |
| limit | integer | – | Max results to return (default: 10) |
| query | string | yes | Search keywords (e.g., 'memory limit', 'timeout', 'permission denied') |
No output schema declared.
No examples provided.
How do I install the deadends.dev MCP server?
deadends.dev runs locally as a PyPI package, launched with uvx deadends-dev. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · deadends-dev
claude mcp add dev-deadends-deadends-dev -- uvx deadends-dev
What is the deadends.dev MCP server?
deadends.dev is an MCP server listed in the public MCP registry as dev.deadends/deadends-dev. Structured failure knowledge for AI agents, dead ends, workarounds, error chains. This page covers its PyPI package (deadends-dev).
Is the deadends.dev MCP server safe to use?
deadends.dev scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the deadends.dev MCP server expose?
deadends.dev exposes 11 tools: lookup_error, get_error_detail, list_error_domains, search_errors, list_errors_by_domain, and 6 more. Their descriptions and schemas cost roughly 1,090 tokens of context every time the server is loaded.
Is the deadends.dev MCP server still maintained?
deadends.dev is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the deadends.dev MCP server under?
deadends.dev declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.