# RepoPilot (npm · repopilot)

Local, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.

- Trust score: 78/100 (medium)
- Change this week: +28
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `repopilot`: 78/100 (this document), [markdown](https://verifymcp.io/servers/mykytastel-repopilot/repopilot.md), [page](https://verifymcp.io/servers/mykytastel-repopilot/repopilot)

## Channel facts

- Registry: `npm`
- Package: `repopilot`
- Version: `0.25.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-10-17.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 5 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to MykytaStel/repopilot).
  - Clear OSI-approved license (MIT OR Apache-2.0).
  - Actively maintained (last published 6 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 53/100
  - 40% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2316 tokens (~257/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the RepoPilot MCP server?

RepoPilot runs locally as an npm package, launched with npx -y repopilot. 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 mykytastel-repopilot -- npx -y repopilot
```

### Cursor

```json
{
  "mcpServers": {
    "mykytastel-repopilot": {
      "command": "npx",
      "args": [
        "-y",
        "repopilot"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mykytastel-repopilot": {
      "command": "npx",
      "args": [
        "-y",
        "repopilot"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mykytastel-repopilot -- npx -y repopilot
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mykytastel-repopilot --command npx --arg -y --arg repopilot
```

### Hermes

```yaml
mcp_servers:
  mykytastel-repopilot:
    command: "npx"
    args: ["-y", "repopilot"]
```

### Netclaw

```json
{
  "McpServers": {
    "mykytastel-repopilot": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "repopilot"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mykytastel-repopilot -t stdio -c npx -a -y repopilot
```

### Other

```json
{
  "mcpServers": {
    "mykytastel-repopilot": {
      "command": "npx",
      "args": [
        "-y",
        "repopilot"
      ]
    }
  }
}
```

## 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-10-14 (score 78, +28)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 40
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] First check of Tool coverage: 100

### 2026-10-12 (score 50, 0)

- [functional] Package version: 0.24.3 → 0.25.0

### 2026-10-08 (score 50, 0)

- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 0.24.1 → 0.24.3

### 2026-10-03 (score 50, +15)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 0.24.0 → 0.24.1

### 2026-10-02 (score 35)

First indexed and scored.

## MCP tools (6)

### `repopilot_review_change` (~864 tokens)

Review a Git change locally: what it touched and which checks it weakened. Use it before finishing work or before a merge. By default it reviews uncommitted work (working tree vs HEAD); pass `base` (e.g. "origin/main") to review a branch. For a repository health check that is not about one change, use repopilot_scan instead. Returns a JSON report with a decision, findings on changed lines vs the rest, blast radius (files that import the changed files), and deterministic signals grouped by confidence tier (definitely / maybe / noise) in `tiered_signals`: checks the change weakened (focused or skipped tests, removed tests, tests that lost assertions, new lint/type/coverage suppressions, relaxed CI or tool gates); security-boundary changes (auth, CORS, CI, dependency manifests, committed .env); behavioral changes (network, subprocess, filesystem, env, dependency, migration, or raw SQL added; error handling, an auth check, or a test removed; a changed quiet-fallback candidate in parsed JS/TS or Python; a removed named TypeScript/JavaScript export that a resolved local caller still imports; a Rust public function whose parameter count changes while a proven module-qualified caller keeps the old argument count); algorithmic changes (deeper nesting, a new nested loop, a grown function, new recursion); and taint-lite reachability (HTTP request or process arguments reaching SQL, exec, filesystem-write, or outbound-network sinks in a changed function). Treat quiet-fallback signals as candidates to verify, not proof of harmful behavior, and preserve intentional recovery paths. Signals are evidence, not verdicts; explain one with repopilot_explain_review_signal. RepoPilot uploads nothing. Only a non-empty `verify` array selects configured local checks. Each selected check runs only after one-time form-mode Elicitation consent from a client that negotiated protocol `2025-11-25` and `elicitation.form`; otherwise it is skipped. The prompt shows the command, exact arguments, and w…

Input parameters:

- `base` (string): Base Git ref to diff against, e.g. "origin/main". Optional; defaults to the working tree vs HEAD.
- `baseline` (string): Optional baseline file (from `repopilot baseline create`). Findings recorded in it count as accepted debt, separate from new findings.
- `config` (string): Optional repopilot.toml path. Defaults to the one discovered in the repository.
- `detail` (string): "compact" returns at most 20 findings and 20 signals; "full" returns all of them.
- `fail_on_review` (string): "definitely" fails the report's gate when a gate-eligible definitely-tier signal is present; "none" reports signals without gating.
- `filters` (object): Optional thresholds and rule IDs that narrow the returned findings.
- `head` (string): Head Git ref. Optional and only valid together with "base".
- `intent` (object): Optional inline statement of what the change is meant to touch (paths, contract families, critical paths, verification IDs). The report marks drift outside it. It is metadata only and cannot execute…
- `intent_path` (string): Optional repository-rooted TOML file that states what the change is meant to touch. The report marks drift outside it. Use either this or `intent`, not both.
- `limit` (integer): Maximum findings to return.
- `offset` (integer): Zero-based finding offset.
- `path` (string): Repository path to review. Defaults to the current working directory.
- `profile` (string): "default" hides low-signal suggestions; "strict" shows all findings.
- `scope` (string): "changed" reports findings in the changed files only; "full" also returns findings from the rest of the repository.
- `verify` (array): IDs of checks configured in repopilot.toml to request for the reviewed revision. Each needs a separate one-time user approval through form-mode Elicitation; unsupported clients skip checks. Omit to r…

### `repopilot_scan` (~306 tokens)

Audit a repository, folder, or file for findings across architecture, coupling, code quality, security, and testing, and return the JSON scan report (findings, metrics, risk summary). Use it for a health check that is not about one change. To review what a change touched or which checks it weakened, use repopilot_review_change; for a short Markdown brief to read before editing, use repopilot_context. Explain a returned finding with repopilot_explain_finding. Runs entirely on disk; nothing is uploaded.

Input parameters:

- `base` (string): Base Git ref for "changed" scope, e.g. "origin/main": scans files changed between base and HEAD. Without it, "changed" means changed against HEAD, including untracked files.
- `config` (string): Optional repopilot.toml path. Defaults to the one discovered in the repository.
- `filters` (object): Optional thresholds and rule IDs that narrow the returned findings.
- `limit` (integer): Maximum findings to return.
- `offset` (integer): Zero-based finding offset.
- `path` (string): Path to scan. Defaults to the current working directory.
- `profile` (string): "default" hides low-signal suggestions; "strict" shows all findings.
- `scope` (string): "full" scans every file under `path`; "changed" scans only changed files (against HEAD, or against `base` when given) and skips repository-level rules.

### `repopilot_context` (~245 tokens)

Generate a budgeted Markdown brief of the repository (risks, hotspots, structure) to read before editing, especially in an unfamiliar codebase. Use it for orientation. For the full findings as JSON, use repopilot_scan; to review a change, use repopilot_review_change. Pass `analysis_handle` to make sure the brief still matches an earlier scan or review. Built locally from a scan; no AI service is called and nothing is uploaded.

Input parameters:

- `analysis_handle` (string): Optional `analysisHandle` from an earlier repopilot_scan or repopilot_review_change call. The call fails if the workspace changed since that analysis.
- `budget` (integer): Optional approximate token budget for the brief. Defaults to the standard budget.
- `config` (string): Optional repopilot.toml path. Defaults to the one discovered in the repository.
- `focus` (string): Optional focus: security, architecture (or arch), quality, framework, or all.
- `path` (string): Repository path. Defaults to the current working directory.
- `profile` (string): "default" hides low-signal suggestions; "strict" includes all findings.

Output parameters:

- `change_proof` (object): Canonical ChangeProof from the referenced review handle, when selected.
- `decision` (object): Canonical primary review decision and next action from the referenced review handle, when selected.
- `evidence` (object): Canonical evidence class, coverage, and provenance from the referenced review handle, when selected.
- `markdown` (string)

### `repopilot_explain_file` (~212 tokens)

Explain how RepoPilot treats one file: the role it assigns (for example test, generated, config, or CLI command handler) and the evidence for it, which rules apply, the ordered overrides that change a rule's severity, and whether the default profile would show the result. Use it to understand a file without a report, or to ask why a rule (`rule`, optionally one detector `signal`) would or would not fire there. To explain a finding already in a scan or review, use repopilot_explain_finding; for a review signal, use repopilot_explain_review_signal. Reads local files only and returns JSON.

Input parameters:

- `path` (string, required): Path to the file to explain.
- `rule` (string): Optional rule ID (see the repopilot://rules resource) to focus the explanation on.
- `signal` (string): Optional detector signal within `rule` to focus on, e.g. "rust.todo" for language.rust.panic-risk.

### `repopilot_explain_finding` (~255 tokens)

Explain why a finding was reported. Use it when you have a `finding_id` from repopilot_scan or repopilot_review_change in this session and need to know why it fired or whether it still reproduces. It replays the stored rule decision against the current workspace, returns the full decision trace, and reports whether the decision matched or drifted. For a review signal (`signal_id`), use repopilot_explain_review_signal; for a file with no finding, use repopilot_explain_file. Local-only.

Input parameters:

- `analysis_handle` (string): Optional `analysisHandle` from an earlier scan or review in this session, to use that report instead of the latest one.
- `evidence_path` (string): Optional evidence path from an ambiguity candidate. Used with line_start to select one occurrence without changing the stable finding ID.
- `finding_id` (string, required): Stable finding ID from the findings array of the selected session report.
- `line_start` (integer): Optional evidence start line from an ambiguity candidate.
- `source` (string): Which report holds the finding: the latest repopilot_scan ("last-scan") or the latest repopilot_review_change ("last-review").

### `repopilot_explain_review_signal` (~169 tokens)

Explain one signal from a review: where it came from, its confidence tier, whether it can fail a gate, the files it affects, how to verify it, and its limits. Use it after repopilot_review_change, with a `signal_id` from that report's `tiered_signals`. For a finding (`finding_id` in the findings array), use repopilot_explain_finding instead. Reads the stored review only; it runs nothing and changes nothing.

Input parameters:

- `analysis_handle` (string): Optional `analysisHandle` from an earlier repopilot_review_change call. Omit to use the latest review in this session.
- `signal_id` (string, required): The `signal_id` of an entry in the review report's `tiered_signals`.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mykytastel-repopilot/repopilot#diagnostics

## Score history

- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 50
- 2026-10-12: 50
- 2026-10-08: 50
- 2026-10-04: 50
- 2026-10-03: 50
- 2026-10-02: 35

## Common questions

### What is the RepoPilot MCP server?

RepoPilot is an MCP server listed in the public MCP registry as io.github.MykytaStel/repopilot. Local, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius. This page covers its npm package (repopilot).

### Is the RepoPilot MCP server safe to use?

RepoPilot scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 RepoPilot MCP server expose?

RepoPilot exposes 6 tools: repopilot_review_change, repopilot_scan, repopilot_context, repopilot_explain_file, repopilot_explain_finding, repopilot_explain_review_signal. Their descriptions and schemas cost roughly 2,051 tokens of context every time the server is loaded.

### Is the RepoPilot MCP server still maintained?

RepoPilot is still listed as active in the MCP registry. We last reached this channel on 17 October 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 RepoPilot MCP server under?

RepoPilot declares the MIT OR Apache-2.0 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/repopilot
- Socket report: https://socket.dev/npm/package/repopilot
- Repository: https://github.com/MykytaStel/repopilot
- Website: https://github.com/MykytaStel/repopilot/blob/main/docs/mcp.md
- Changelog RSS feed: https://verifymcp.io/servers/mykytastel-repopilot/repopilot.xml
- Changelog JSON feed: https://verifymcp.io/servers/mykytastel-repopilot/repopilot.json
- HTML version of this page: https://verifymcp.io/servers/mykytastel-repopilot/repopilot