Reprocheck MCP server

by CloudCorpRecords·io.github.CloudCorpRecords/reprocheck·v0.2.0

Red-first repro verifier: a fix counts only when the repro fails on the base and passes on the fix.

A92/100grade A

What users say

No reviews yet

Safety scan

A92/100

Adoption

New

0 stars0 downloads/wk

Reviews

Nobody has reviewed Reprocheck yet.

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

write = sends, deletes, buys or posts

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

detect_test_runners
Detect which native test runners a local repository supports (pytest and/or go test), with the filesystem evidence for each and the test files found. Runs no code from the target repository.
run_repro_checkwrite action
Verify a fix the honest way: run the same repro in clean git worktrees of the base ref and the head ref. VERIFIED only when it fails on the base and passes on the head. NOT-REPRODUCED when it passes on the base too, STILL-FAILING when it fails on both, BROKEN-BY-HEAD when the change introduced the failure, ERROR when a run could not complete. Give either a raw command, or a native runner (pytest,

scanner v0.1.10 · 2026-10-26 · same rubric, same numbers if you re-run it

no findings

Code scan14 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 0 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.Rubric Appeal a finding JSON

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

Safety score: 92/100; higher than 90% of 48,273 servers
Tools: 2; the typical server has 7
Tools that change things: 50%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read · 1 run or deploy

Release history: 2 versions in the registry since 2026-10-19, latest 2026-10-26, typically one every 6 days.

Runs npx -y @reneturcios/reprocheck on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add reprocheck -- npx -y @reneturcios/reprocheck

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