MCP.Market

culprit MCP server

by noordeen123·io.github.noordeen123/culprit·v0.4.0·6 stars
No reviews yet

Deterministic, offline root-cause analysis and pre-commit fix verification for coding agents.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

6 stars28 downloads/wk

Reviews

Write one

Nobody has reviewed culprit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

culprit tools (11)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • analyze

    Full RCA in one call: classify -> suspects (bugfix) or blast-radius (feature) -> risk score -> test impact.

  • check_completeness

    Is the fix complete? Find other references to changed symbols not touched by this fix.

  • classify_change

    Classify whether a change is a bugfix or a feature, with evidence.

  • find_suspects

    Find the commits most likely to have introduced a bug.

  • from_trace

    RCA from a stack trace or crash log; no diff or PR needed.

  • get_blast_radius

    Map what a feature change affects: who imports the changed modules, covering tests, high-risk areas.

  • get_evolution

    ``git log -L`` over a line range: every commit that touched those lines, oldest to newest, with per-step diffs.

  • get_intent

    Commit body + the PR it came from (title, body, url) + linked issues (Fixes/Closes/Resolves #N).

  • get_risk_score

    QA risk score for a change: 0-100 with level (low/medium/high) and contributing factors.

  • get_test_impact

    Which existing tests should be run for this change.

  • verify_fix

    Check fix completeness against a raw unified diff before committing.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan32 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How culprit compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
11
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
6
more than 85% of 28,688 servers
Downloads a week
28
more than 15% of 12,191 servers with a package

What its tools let an agent do: 11 read

Install culprit in Claude Code, Cursor or VS Code

claude mcp add culprit -- uvx culprit
Add to Cursor

What the publisher says

From the culprit repository's README, as published. We do not edit it. Read it on GitHub

culprit

<!-- mcp-name: io.github.noordeen123/culprit -->

Root-cause analysis for agent-driven development. Your coding agent finds what introduced a bug, and verifies its own fix is complete before it commits.

Quick start · Tools · Accuracy · Architecture · MCP registry

A real run. The fix patched one caller of parse_config and missed two, so it scores partial.

Why an agent needs this

An agent can dig through git history to find what broke, and it is good at it. What it will not reliably do is spend a dozen tool calls on that every time, or stop and check whether the helper it just changed has three other callers before it commits. culprit turns both into one deterministic call that returns structured JSON it can act on:

  • ⚡️ Instant. No test runs, no bisect. Benchmarked at 41% fewer agent tool calls.
  • 🔒 Read-only and offline. Never writes to your repo or PR. No API key, no network.
  • 🔌 MCP-native. 11 tools over stdio, on the official MCP registry, plus a one-command plugin.
  • 🗣️ Language-agnostic. Suspects work anywhere git does. Blast radius reads 12 language families.

Does it actually work?

Benchmarked against 50 real regressions, 25 from git and 25 from systemd, where the introducing commit is known from each fix's Fixes: trailer (author-verified ground truth). Given only the fix commit, culprit blames the removed lines to rank the commits that introduced the bug.

Deterministic and offline, on large C codebases the engine has never seen. Reproduce with python benchmarks/run.py, which clones the repos and scores every case.

But an agent can run git blame itself

It can, and it is good at it. So the honest question is not whether culprit is accurate, but whether it beats or helps an agent that has git and no culprit. Same 10 regressions, three arms, isolated so no arm can read the answer from the fix commit:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

culprit: common questions

Is culprit MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the culprit safety report
How do I install culprit?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does culprit need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is culprit maintained?
The last commit was 70 days ago (2026-08-26). The latest release is v0.4.0.
How does culprit compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 11 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.