repo-forensics-mcp
v1.0.2
Published
Local read-only MCP tools for Git repository archaeology, churn, hotspots, and hygiene. Tools include repository summary, recent changes, file hotspots
Maintainers
Readme
repo-forensics-mcp
A local-only MCP companion for understanding a Git repository before a review, refactor, or release.
Tools
repository_summary: branch, working tree status, remotes, and latest commit metadata.recent_changes: bounded recent commit history.file_hotspots: files appearing most often in recent history.top_level_hygiene: top-level large files,.gitignorepresence, and dirty state without reading file contents.
The server invokes local Git with fixed argument arrays. By default, paths must stay under the parent workspace of the package process; set REPO_FORENSICS_ROOT to an explicit workspace root when launching it. It returns remote names rather than remote URLs to avoid leaking credentials. It does not fetch, push, write files, inspect remote services, or send repository data over the network. Hotspots and hygiene are heuristics, not a complete code-quality or security audit.
Run
npm install
npm run build
node dist/index.jsQuick start
npm install
npm run build
node dist/index.jsThe server uses stdio, so it can be connected to Claude Desktop, Cursor, VS Code, MCP Inspector, or another compatible MCP client.
Tools at a glance
repository_summary: Read branch, working-tree, remote names, and latest commit metadata from a local Git repository.recent_changes: List recent local Git commits with bounded output.file_hotspots: Find files that appear most often in recent repository history. This is a heuristic for review focus, not a defect detector.top_level_hygiene: Check top-level large files, .gitignore presence, and working-tree dirtiness without reading file contents.
Limits and privacy
This project is intentionally narrow. It should be treated as a practical helper, not a complete certification or security audit. Check the implementation and the returned data before using it with sensitive material. No credentials are required unless the project explicitly says otherwise.
Try it
After building, connect the server through your MCP client. The repository root also contains smoke-test.mjs for projects covered by the shared harness. A typical tool call starts with repository_summary.
Licence — no paywall
Every tool in this package is free: no licence key, no premium tier, no hosted licence gateway. The paywall machinery this repo once carried (per-tool licence checks and paid hosted endpoints) was removed repo-wide on 2026-10-17. Nothing that this package installs or calls asks you to pay.
