Culprit
未认领Superpowers your agent's debugging: what introduced this bug, and is my fix actually complete? Deterministic, offline, read-only, MCP-native.
01 / 选择客户端
03 / 添加配置
claude mcp add --transport stdio 'culprit' -- 'uvx' '--from' 'culprit[mcp]' 'culprit-mcp'04 / 在客户端中确认
打开客户端的 MCP 设置，确认服务器已连接并列出工具。复制配置不代表连接成功。
更多AI & ML服务器
浏览完整目录安全概况
已认领和已认证的服务器每周接受一次静态扫描，显示代码能触及的范围（外部服务、环境变量、shell 命令、代理配置目录）以及带有已知公告的依赖。认领此列表即可获得。 安全概况的工作原理
11 个工具中显示 11 个
文档中列出的工具 (11)
内容来自项目文档。服务器握手不会验证每个工具的说明或行为。
analyze
Full RCA in one call: classify, suspects or blast radius, risk, test impact
check_completeness
Call sites of the changed symbol the fix did not touch
classify_change
Bugfix vs feature, with evidence
find_suspects
Rank the commits that introduced the bug
from_trace
RCA straight from a stack trace, no diff or PR needed
get_blast_radius
Feature impact: dependents, covering tests, high-risk files
get_evolution
Per-commit history of the buggy lines via git log -L
get_intent
The introducing commit's message, linked PR, referenced issues
get_risk_score
QA gate score (0 to 100, low/medium/high) with contributing factors
get_test_impact
Minimal test set to run for this change
verify_fix
Is this diff safe to commit? complete / partial / risky, plus the missed call sites