# RepoRipple (pypi · reporipple)

Deterministic repository change-impact analysis for engineers and coding agents.

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- pypi · `reporipple`: 82/100 (this document), [markdown](https://verifymcp.io/servers/adiarora06-reporipple/reporipple.md), [page](https://verifymcp.io/servers/adiarora06-reporipple/reporipple)

## Channel facts

- Registry: `pypi`
- Package: `reporipple`
- Version: `0.3.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-01.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to adiarora06/RepoRipple).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 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 (good).
  - Tool/resource definitions use about 201 tokens (~100/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
  - 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

RepoRipple runs locally as a PyPI package, launched with uvx reporipple. 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 adiarora06-reporipple -- uvx reporipple
```

### Cursor

```json
{
  "mcpServers": {
    "adiarora06-reporipple": {
      "command": "uvx",
      "args": [
        "reporipple"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "adiarora06-reporipple": {
      "command": "uvx",
      "args": [
        "reporipple"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add adiarora06-reporipple -- uvx reporipple
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "adiarora06-reporipple": {
      "type": "local",
      "command": [
        "uvx",
        "reporipple"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add adiarora06-reporipple --command uvx --arg reporipple
```

### Hermes

```yaml
mcp_servers:
  adiarora06-reporipple:
    command: "uvx"
    args: ["reporipple"]
```

### Netclaw

```json
{
  "McpServers": {
    "adiarora06-reporipple": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "reporipple"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add adiarora06-reporipple -t stdio -c uvx -a reporipple
```

### Other

```json
{
  "mcpServers": {
    "adiarora06-reporipple": {
      "command": "uvx",
      "args": [
        "reporipple"
      ]
    }
  }
}
```

## 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-01 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-30 (score 67, +2)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.10
- [functional] Package version: 0.2.0 → 0.3.0

### 2026-09-29 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-28 (score 80, +25)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 55)

First indexed and scored.

## MCP tools (2)

### `forecast_change` (~78 tokens)

Forecast a code change

Estimate the blast radius of proposed repository-relative file changes.

Input parameters:

- `changed_files` (array, required): Repository-relative files that are expected to change.
- `max_depth` (integer): Maximum reverse-dependency traversal depth.
- `repository` (string): Repository directory, relative to the server's allowed root. Absolute paths are accepted only when they remain inside that root.

Output parameters:

- `changed_files` (array)
- `documentation_to_review` (array)
- `graph_edges` (integer)
- `graph_files` (integer)
- `impacted_files` (array)
- `repository` (string)
- `risk_level` (string)
- `risk_reasons` (array)
- `suggested_tests` (array)
- `warnings` (array)

### `analyze_worktree` (~79 tokens)

Analyze current Git changes

Analyze worktree changes, or compare HEAD with an optional Git base revision.

Input parameters:

- `base`: Optional Git revision to compare with HEAD.
- `max_depth` (integer): Maximum reverse-dependency traversal depth.
- `repository` (string): Repository directory, relative to the server's allowed root. Absolute paths are accepted only when they remain inside that root.

Output parameters:

- `changed_files` (array)
- `documentation_to_review` (array)
- `graph_edges` (integer)
- `graph_files` (integer)
- `impacted_files` (array)
- `repository` (string)
- `risk_level` (string)
- `risk_reasons` (array)
- `suggested_tests` (array)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/adiarora06-reporipple/reporipple#diagnostics

## Score history

- 2026-10-01: 82
- 2026-09-30: 67
- 2026-09-29: 65
- 2026-09-28: 80
- 2026-09-27: 55

## Common questions

### What is the RepoRipple MCP server?

RepoRipple is an MCP server listed in the public MCP registry as io.github.adiarora06/reporipple. Deterministic repository change-impact analysis for engineers and coding agents. This page covers its PyPI package (reporipple).

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

RepoRipple scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. 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 RepoRipple MCP server expose?

RepoRipple exposes 2 tools: forecast_change, analyze_worktree. Their descriptions and schemas cost roughly 157 tokens of context every time the server is loaded.

### Is the RepoRipple MCP server still maintained?

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

RepoRipple 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

- PyPI project: https://pypi.org/project/reporipple/
- Socket report: https://socket.dev/pypi/package/reporipple
- Repository: https://github.com/adiarora06/RepoRipple
- Changelog RSS feed: https://verifymcp.io/servers/adiarora06-reporipple/reporipple.xml
- Changelog JSON feed: https://verifymcp.io/servers/adiarora06-reporipple/reporipple.json
- HTML version of this page: https://verifymcp.io/servers/adiarora06-reporipple/reporipple