ripple-mcp

# Ripple [](LICENSE) [](https://python.org) [](https://modelcontextprotocol.io) [](#guard) **Code intelligence from git history — not static analysis.** Works inside **Claude Code · Cursor · GitHub Copilot Agent · OpenHands · Windsurf** Static analysis tells you what *could* break. Git history tells you what *actually* breaks together. The gap between those two is where production incidents live — and where Ripple operates. --- ## Try it in 60 seconds — no GPU, no config Analyze any public repo's blast radius from its commit history: ```bash git clone https://github.com/Amitshukla2308/Index-the-code cd Index-the-code pip install -e . python3 apps/cli/demo.py https://github.com/your-org/your-repo open hr-demo-report.html ``` You get an HTML report of the highest-risk files ranked by co-change history. **On Flask:** `src/flask/app.py` scores 1120 — the single most-coupled file across 2000 commits. No surprise. Immediately useful. --- ## What it does ### Blast Radius — +322% recall over static import graph Every other tool counts import edges. Ripple counts how often files *actually changed together* across your git history. The difference: only **14.9% of import neighbors ever co-change** — the static graph predicts risk for files that don't need review. Temporal signals catch the 85% the graph misses. | Metric | Static (v1) | Temporal (v2) | Delta | |--------|------------|--------------|-------| | recall@10 | 0.11 | **0.47** | **+322%** | | MRR | 0.08 | **0.36** | +359% | ### Guard — static semantic checks at 2.4ms/file AI-generated code passes every review gate because it *looks* correct. Guard verifies what it *claims*: checks that comments match the code that follows, that locks aren't released …