Mcp
Find test gaps, generate grounded tests, and dynamically prove behavior with mutation testing.
- Transport
- Not stated
- Package
- —
- Registry id
- ai.orangepro/mcp
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
OrangePro maps every public behavior in your codebase, scores each one by real test evidence, and shows you the structural blind spots before your users find them. Runs locally. Your code never leaves your machine.
npx -y @orangepro/mcp-server@latest start .
Table of Contents
- What you get
- Evidence tiers
- Quick start
- Use with your coding agent
- How it works
- Language support
- Privacy
- CLI reference
- MCP tools
- Platform
- Contributing
What you get
One command produces an interactive HTML report:
npx -y @orangepro/mcp-server@latest start .
open .orangepro/behavior-coverage.html
The report has two modes: Simple (integration-level blind spots, plain English) and Expert (full behavior list, evidence tiers, flows, system map). Toggle with the pill switch at the top.
→ Live example: Twenty CRM (5,237 behaviors mapped)
System map — entry lanes (GraphQL, HTTP, Jobs) flowing into services, sized by traffic, colored by evidence tier, red-ringed by risk.
Priority gaps of another open source Project HONO — top 20 unproven behaviors ranked by blast radius, with generated test drafts.
Evidence tiers
Every behavior gets exactly one tier. Nothing is labeled "tested" on faith.
| Tier | Color | What it means |
|---|---|---|
| Dynamically Proven | 🟢 | A real test kills a targeted mutation of this behavior |
| Runtime-covered | 🟢 | Coverage tool executed this code |
| Statically Linked | 🟡 | A test imports and calls this code — structural link, not proof |
| Unconfirmed Candidate | ⚪ | A similar test file exists — a lead, not evidence |
| No Signal | 🔴 | Nothing tests this behavior |
"Dynamically Proven 0" is normal on first run. Proof requires running tests against targeted mutations. That's the trust model.
Quick start
cd /path/to/your/repo
npm install # install the repo's own dependencies first
npx -y @orangepro/mcp-server@latest start .
open .orangepro/behavior-coverage.html
No API key needed. The report shows your system map, evidence tiers, priority gaps, and delta since last run.
Want test generation? Add a model key (BYOK):
export ANTHROPIC_API_KEY="..." # or OPENAI_API_KEY / OLLAMA_BASE_URL
npx -y @orangepro/mcp-server@latest start .
AI output never changes evidence tiers. Only the mutation-kill oracle can mint Dynamically Proven.
Output:
.orangepro/
├── behavior-coverage.html ← open this
├── graph.json ← deterministic evidence graph
├── COVERAGE_REPORT.md ← coverage and gap summary
└── ai/ ← candidate flows (when a key is configured)
orangepro_generated/ ← generated tests; your source files are never touched
Each rerun shows a delta banner: what entered the codebase, what moved up in risk, what got resolved.
Use with your coding agent
OrangePro runs as an MCP server. Add to your client's config:
{
"mcpServers": {
"orangepro-local": {
"command": "npx",
"args": ["-y", "@orangepro/mcp-server@latest", "mcp"]
}
}
}
From the project's README.