A
licenseNot graded
qualityC
maintenanceAn autonomous task decomposition and execution agent that plans, executes, verifies, and commits code changes for engineering goals.
MIT
culprit
by noordeen123
Related Servers
Alternatives to culprit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceThe 'Blast Radius' detector for AI Agents. Prevent regressions using Git history and organizational memory.1387MIT
- AlicenseCqualityAmaintenanceLocal-first error memory for AI coding agents, enabling them to search past fixes before attempting new repairs and save verified cases as Markdown.3MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect, edit, and test code within a bounded repository environment to solve software engineering tasks and verify fixes.-
- AlicenseBqualityAmaintenanceEnables coding agents to develop on one machine and verify results on another, using branch-bound runbooks, isolated checkpoints, and structured receipts to guide repair iterations.1040MIT
- AlicenseNot gradedqualityAmaintenanceA runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.1MIT
TDQS
B3.3/5.0
Scored across 11 tools
Disambiguation2/5
Several tool pairs have overlapping responsibilities: from_trace and find_suspects both take a stack trace and return suspects, verify_fix and check_completeness both assess fix completeness, and get_test_impact/get_blast_radius both surface covering tests. The descriptions are detailed, but an agent could easily select the wrong tool for the same underlying task.
Naming Consistency3/5
Most names are lowercase snake_case verb_noun, but the verbs are inconsistent across get_, classify_, find_, check_, verify_, and two tools break the pattern entirely: from_trace and analyze. The naming is readable but not predictable enough to be considered a consistent convention.
Tool Count4/5
Eleven tools is within a reasonable range for a change-analysis server, but the set is slightly larger than necessary because some tools duplicate or wrap each other's functionality. It is not bloated, just a bit redundant.
Completeness5/5
The tool surface covers the full RCA workflow: classify, identify suspects, map blast radius, compute test impact, score risk, verify completeness, inspect evolution, and read intent. The analyze tool also provides an orchestrated end-to-end path, while individual tools allow drilling into specific signals without obvious dead ends.
Maintenance
ActivityActive
ResponsivenessNo issues