self-healing-test-mcp
Related Servers
Alternatives to self-healing-test-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible AI coding agents to obtain clean failing-test context, ranked suspect lines, runtime value comparisons, bounded code search, and patch verification so they can fix Python test failures with fewer tokens.MIT
- AlicenseAqualityBmaintenanceEnables autonomous coding agents to localize faults from tracebacks, verify candidate patches against deterministic anti-reward-hacking rules, apply transactional changes with automatic rollback, and inspect AST symbols through MCP tools.5MIT
- AlicenseNot gradedqualityBmaintenanceProvides a code-quality backend MCP tool that automatically writes and repairs pytest tests, runs them in a sandbox, validates their effectiveness via mutation testing, and surfaces suspected source bugs for human review.MIT
- AlicenseAqualityBmaintenanceEnables turning pasted or logged crash output from Python, Node, Java, Go, Rust, and .NET into compact root-cause reports, mapping frames onto project code, fingerprinting and comparing traces, explaining exceptions, and redacting secrets over MCP.7MIT
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools that give LLM agents a full QA engineer workflow: scanning projects, generating deterministic test suites, executing them across browser/API/mobile, diagnosing failures, and proposing fixes that require human approval.-
- AlicenseAqualityBmaintenanceEnables AI coding agents to observe real-time Node, Vite, Next.js, Storybook, TypeScript, and browser runtime errors from a wrapped dev server, source-mapped to exact file, line, and column with the log lines preceding each crash. It exposes MCP tools for listing open errors, fetching full stack details, and checking or marking fixes as resolved, all locally with no code changes.458 npmMIT
TDQS
Scored across 3 tools
Each tool targets a distinct stage of the test-debugging workflow: parsing tracebacks, generating tests, and auditing assertions. There is no realistic scenario where an agent would confuse one for another; verbs and objects are both unambiguous.
All three names follow a strict snake_case verb_noun pattern (decompile_stack_trace, generate_edge_case_tests, audit_test_assertions) with concrete verbs and resource-like nouns. No mixed conventions or vague verbs.
Three tools is on the thin side but each covers a genuinely separate workflow step, so nothing feels padded or redundant. The surface is tight and well-scoped for a focused test-quality server, just slightly under what the 'self-healing' framing implies.
The set covers diagnose (decompile), create (generate tests), and review (audit assertions), but the 'self-healing' promise is unfulfilled: there is no tool to run tests, apply a generated fix, or patch/rewrite weak assertions found by the audit. Agents can work around by doing the healing themselves, but the lifecycle has notable gaps.