Repo Forensics Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Local read-only MCP server that lets an assistant inspect a Git repository's history, churn, hotspots and hygiene before a review or refactor.

What you can do
  • Summarize a repository: branch, working tree status, remote names and latest commit metadata
  • Read bounded recent commit history
  • Identify file hotspots that appear most often in recent history
  • Check top-level hygiene: large files, .gitignore presence and dirty state without reading file contents
When to use it
Useful when you want an assistant to get oriented in a local Git repository before a code review, refactor or release, or to spot frequently changed files and basic hygiene issues without granting write access.
Requirements
Runs as a local stdio process installed from the npm package repo-forensics-mcp; requires Node.js and a local Git installation. Paths are limited to the parent workspace of the package process unless REPO_FORENSICS_ROOT is set to an explicit workspace root. No accounts, API keys or network access are needed.
Before you install
Read-only by design: it does not fetch, push, write files or send repository data over the network, and returns remote names rather than URLs to avoid leaking credentials. Hotspot and hygiene results are heuristics, not a complete code-quality or security audit. Setting REPO_FORENSICS_ROOT widens which paths the server may inspect.

Installation

In SourceWeft

  1. Open Repo Forensics Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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, .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 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

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit c2d5ff7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.