MCP.Market

Repo Forensics MCP server

by mrfentmen·io.github.mrfentmen/repo-forensics-mcp·v1.0.0
No reviews yet

Local read-only MCP tools for Git repository archaeology, churn, hotspots, and hygiene. Tools...

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Repo Forensics yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Repo Forensics tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • file_hotspots

    Find files that appear most often in recent repository history. This is a heuristic for review focus, not a defect detector.

  • recent_changes

    List recent local Git commits with bounded output.

  • repository_summary

    Read branch, working-tree, remote names, and latest commit metadata from a local Git repository.

  • top_level_hygiene

    Check top-level large files, .gitignore presence, and working-tree dirtiness without reading file contents.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 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 85 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Repo Forensics compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 1,119 Developer tools servers
Tools
4
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break

What its tools let an agent do: 4 read

Install Repo Forensics in Claude Code, Cursor or VS Code

Runs npx -y repo-forensics-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add repo-forensics-mcp -- npx -y repo-forensics-mcp
Add to Cursor

What the publisher says

From the Repo Forensics repository's README, as published. We do not edit it. Read it on GitHub

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.
  • toplevelhygiene: top-level large files, .gitignore presence, 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 REPOFORENSICSROOT 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.js

Nothing above is checked by us. What we check is on the safety report.

Repo Forensics: common questions

Is Repo Forensics MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Repo Forensics safety report
How do I install Repo Forensics?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Repo Forensics need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Repo Forensics maintained?
The last commit was 87 days ago (2026-08-08). The latest release is v1.0.0.
What can I use instead of Repo Forensics?
Servers from other publishers that do the same job: komnet MCP server, GitHub MCP server and Gk CLI MCP server.
How does Repo Forensics compare with other Developer tools MCP servers?
safety score 85/100 (higher than 70% of 1,119 Developer tools servers); tools 4 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Repo Forensics

Same job from other publishers: the closest match first, then the best rated.

  • komnet
    Lets AI coding agents coordinate asynchronously through a private git repository. No server.
    A
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • Repowise
    Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
    B
  • Git
    Comprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.
    A

More from mrfentmen →