Structured failure knowledge for AI agents — dead ends, workarounds, error chains
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: Code errors (2,089 entries, 51 domains): what NOT to try when an agent Country-scoped dead ends (56+ entries across 20+ countries):…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
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: Code errors (2,089 entries, 51 domains): what NOT to try when an agent Country-scoped dead ends (56+ entries across 20+ countries): visa rules, banking requirements, legal red lines (lèse-majesté, §86a, Article 301), cultural taboos…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.