Over-Reach Detector MCP server
io.github.choreoatlas/over-reach-detector·v0.0.6Detect when AI code changes exceed declared task scope (MCP server).
0 stars18 downloads/wk
Reviews
Write oneNobody has reviewed Over-Reach Detector yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Over-Reach Detector tools (1)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
check_scope_toolCheck whether an AI's actual code diff exceeds the declared task scope.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan4 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 126 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Over-Reach Detector compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 58% of 1,299 Productivity servers
- Tools
- 1
- the typical Productivity server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 18
- more than 5% of 427 Productivity servers with a package
What its tools let an agent do: 1 read
Install Over-Reach Detector in Claude Code, Cursor or VS Code
claude mcp add over-reach-detector -- uvx over-reach-detector
What the publisher says
From the Over-Reach Detector repository's README, as published. We do not edit it. Read it on GitHub
Over-Reach Detector (MCP server)
<!-- mcp-name: io.github.choreoatlas/over-reach-detector -->
Detect and report when AI coding agents change files outside their declared task scope. Designed to plug into Cursor, Claude Code, and other MCP-compatible AI coding agents via the standard stdio transport.
Compares two things:
- Declared scope — the files (as fnmatch globs) and categories (tests, docs, infra, config, code) the task is allowed to touch.
- Actual diff — the files the AI actually modified.
If the actual diff exceeds the declared scope, the tool returns status=over_reach and lists the offending files and categories.
What this tool does and does not do
over-reach-detector is an audit/disclosure tool, not a sandbox and not a blocker.
It compares a declared task scope with the actual files/categories changed by an AI coding agent. If the actual changes exceed the declared scope, it reports that mismatch.
It does not prevent file writes by itself. It does not decide whether to revert, approve, or block a change. The caller remains responsible for enforcement, rollback, or human review.
Install
From PyPI:
pip install over-reach-detectorFrom source:
git clone https://github.com/choreoatlas/over_reach_detector
cd over_reach_detector
pip install -e .Quick start
Run all tests: python -m pytest -v
Try the CLI directly: python -m overreachdetector.detector --input fixtures/examplepr1.json --format markdown
Use as MCP server
Start the server (stdio transport): over-reach-detector (or python -m overreachdetector.server from source)
Register with your AI agent:
- Cursor: in ~/.cursor/mcp.json, add (after pip install over-reach-detector):
{
"mcpServers": {
"over-reach-detector": {
"command": "over-reach-detector"
}
}
}Dev / from source: use "command": "python", "args": ["-m", "overreachdetector.server"] (run from repo root).
- Claude Code: after pip install over-reach-detector, run claude mcp add over-reach-detector over-reach-detector (writes to ~/.claude.json). Dev / from source: claude mcp add over-reach-detector /absolute/path/to/python -m overreachdetector.server.
The tool
checkscopetool takes:
- declaredfiles: list of fnmatch globs (e.g. ["docs/.md", "tests/*.py"])
- declared_categories: subset of ["tests", "docs", "infra", "config", "code"]
- actual_files: list of file paths the AI modified
- output_format: "json" (default) or "markdown"
Returns a report with:
- status: inscope (within declared scope) | overreach (reported mismatch) | empty
- file_overreach: files not matching any declared glob
- category_overreach: inferred categories outside the declared set
Scope discipline
Current scope: CLI + MCP stdio server + 1 tool. Python only. fnmatch-based globs.
Out of scope (forbidden): code quality review, security audit, completeness governance, languages other than Python, multi-tool MCP servers, HTTP/SSE transport, GitHub Actions integration. These are deliberately deferred to later versions or never.
Example usage
Call checkscopetool directly from Python (same logic the MCP server exposes):
import json
from over_reach_detector import server
result = server.check_scope_tool(
declared_files=["docs/*.md"],
declared_categories=["docs"],
actual_files=["docs/a.md", "scripts/extra.py"],
output_format="json",
)
report = json.loads(result)
print(report["status"]) # "over_reach"
print(report["file_overreach"]) # ["scripts/extra.py"]License
MIT — see LICENSE.
Nothing above is checked by us. What we check is on the safety report.
Over-Reach Detector: common questions
- Is Over-Reach Detector MCP server safe?
- Mostly: it is graded B (82/100). Read the Over-Reach Detector safety report
- How do I install Over-Reach Detector?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Over-Reach Detector need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Over-Reach Detector maintained?
- The last commit was 164 days ago (2026-05-24). The latest release is v0.0.6.
- What can I use instead of Over-Reach Detector?
- Servers from other publishers that do the same job: no_human MCP server, loci MCP server and Agentpack MCP server.
- How does Over-Reach Detector compare with other Productivity MCP servers?
- safety score 82/100 (higher than 58% of 1,299 Productivity servers); tools 1 (the typical Productivity server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Over-Reach Detector
Same job from other publishers: the closest match first, then the best rated.
- no_humanFile a task with your local no_human and check on it: task_add and task_status over stdio.not reviewedEstablishedB
- lociCross-session memory and hybrid RAG over your notes and docs. Local-first, with cited answers.not reviewedEstablishedA
- AgentpackRepo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP.not reviewedGrowingA