deadends.dev
Related Servers
Alternatives to deadends.dev
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables agents to query a registry of documented AI-agent failures for debugging incidents, deployable on Cloudflare Workers.1MIT

openqfrofficial
FlicenseNot gradedqualityBmaintenanceEnables AI agents to search and retrieve machine-readable records of failed quantitative trading strategies, helping them avoid repeating unsuccessful backtests.-
DAiMONofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to check proposed actions against a local ledger of previously ruled-out work, receiving graded alerts with prior verdicts to avoid repeating dead ends.AGPL 3.0- AlicenseNot gradedqualityBmaintenanceEnables coding agents to record rejected approaches, decisions, and constraints, with expiring reasons, in a git-tracked Markdown store the agent consults before proposing anything. This makes agents stop re-suggesting options that were already ruled out, and entries quietly drop out of view once they lapse.103 npm1MIT
- AlicenseAqualityAmaintenanceEnables AI agents to query live, cross-agent tool failure fingerprints and recovery outcomes before retrying, so they can act on collective evidence and avoid repeating proven-ineffective retries.42MIT
- AlicenseAqualityAmaintenanceEnables AI agents to query a public signed ledger of known failures and fixes before retrying, then ingest, confirm, fail, and share dense claims so subsequent agents avoid paying the same cost.29293 PyPI3Apache 2.0
TDQS
Scored across 11 tools
Each tool targets a distinct operation: exact error lookup vs fuzzy search vs batch, per-domain listing vs stats, country listing vs summary, and detail vs chain. The descriptions clearly differentiate overlapping pairs like lookup_error and search_errors.
All tools use snake_case with a consistent verb_noun pattern: list_*, get_*, search_*, batch_lookup, report_outcome. Even the exception (lookup_error) still follows the verb_noun convention.
11 tools is well within the ideal 3-15 range. Each tool covers a distinct aspect of the error database (listing, searching, details, chains, statistics, feedback) without redundancy.
The set covers the full workflow: discover domains, list errors, search and lookup, get details, traverse chains, analyze stats, and provide feedback. No obvious gaps for its stated purpose.