# io.github.CloudCorpRecords/reprocheck (npm · @reneturcios/reprocheck)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/reprocheck`: 72/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-reprocheck/reneturcios-reprocheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-reprocheck/reneturcios-reprocheck)
- oci · `ghcr.io/cloudcorprecords/reprocheck`: 48/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-reprocheck/ghcr-io-cloudcorprecords-reprocheck.md), [page](https://verifymcp.io/servers/cloudcorprecords-reprocheck/ghcr-io-cloudcorprecords-reprocheck)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/reprocheck`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 463 tokens (~231/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/reprocheck MCP server?

io.github.CloudCorpRecords/reprocheck runs locally as an npm package, launched with npx -y @reneturcios/reprocheck. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-reprocheck -- npx -y @reneturcios/reprocheck
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-reprocheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/reprocheck"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-reprocheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/reprocheck"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-reprocheck -- npx -y @reneturcios/reprocheck
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-reprocheck": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/reprocheck"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-reprocheck --command npx --arg -y --arg @reneturcios/reprocheck
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-reprocheck:
    command: "npx"
    args: ["-y", "@reneturcios/reprocheck"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-reprocheck": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/reprocheck"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-reprocheck -t stdio -c npx -a -y @reneturcios/reprocheck
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-reprocheck": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/reprocheck"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 68, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 52, −15)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Schema quality: 281 → 231
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-10-24 (score 67, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-23 (score 72, +2)

- [functional improvement] Stability: unverified → 0.13

## MCP tools (2)

### `run_repro_check` (~402 tokens)

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, go, or auto) with an optional testFile and testName, and reprocheck builds the real pytest or go test command itself. An uncommitted repro or regression test file can be copied into both worktrees with testFile. The report includes a machine readable receipt with the red (base) and green (head) evidence. The working tree is never modified.

Input parameters:

- `baseRef` (string, required): Base ref (the code before the fix), e.g. main or a commit SHA
- `command` (string): The raw repro command to run in both worktrees, e.g. npm test. Omit when runner is given
- `headRef` (string, required): Head ref (the code with the fix), e.g. HEAD or a branch
- `repoPath` (string, required): Path to a local git repository
- `runner` (string): Native test runner to use instead of a raw command: pytest, go, or auto (detect from the repo)
- `setupCommand` (string): Optional setup command run in each worktree first, e.g. npm install
- `testFile` (string): Repo-relative path of an uncommitted repro/test file in the working tree to copy into both worktrees
- `testName` (string): A single named test for a native runner, e.g. test_add for pytest or TestAdd for go test
- `timeoutSeconds` (number): Per-command timeout in seconds, default 300

### `detect_test_runners` (~61 tokens)

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.

Input parameters:

- `repoPath` (string, required): Path to a local repository or directory

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-reprocheck/reneturcios-reprocheck#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 68
- 2026-10-27: 68
- 2026-10-26: 52
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-10-23: 72
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 55

## Common questions

### What is the io.github.CloudCorpRecords/reprocheck MCP server?

io.github.CloudCorpRecords/reprocheck is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/reprocheck. Red-first repro verifier: a fix counts only when the repro fails on the base and passes on the fix. This page covers its npm package (@reneturcios/reprocheck).

### Is the io.github.CloudCorpRecords/reprocheck MCP server safe to use?

io.github.CloudCorpRecords/reprocheck scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.CloudCorpRecords/reprocheck MCP server expose?

io.github.CloudCorpRecords/reprocheck exposes 2 tools: run_repro_check, detect_test_runners. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/reprocheck MCP server still maintained?

io.github.CloudCorpRecords/reprocheck is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/reprocheck MCP server under?

io.github.CloudCorpRecords/reprocheck declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/reprocheck
- Socket report: https://socket.dev/npm/package/@reneturcios/reprocheck
- Repository: https://github.com/CloudCorpRecords/reprocheck
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-reprocheck/reneturcios-reprocheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-reprocheck/reneturcios-reprocheck.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-reprocheck/reneturcios-reprocheck