Skip to main content
Glama

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.

Related MCP server: GitIntel

Run

npm install
npm run build
node dist/index.js

Available Tools

4 tools
file_hotspotsA

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

Inputs: cwd, limit.

recent_changesB

List recent local Git commits with bounded output.

Inputs: cwd, limit.

repository_summaryA

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

Inputs: cwd.

top_level_hygieneA

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

Inputs: cwd.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of repository forensics: overall state, recent history, file hotspots, and top-level hygiene. There is no overlap in their functions, making them easy to distinguish.

    Naming Consistency4/5

    All names use snake_case and are descriptive, but they mix noun phrases (repository_summary, file_hotspots) with adjective-noun forms (recent_changes, top_level_hygiene). The pattern is not strictly verb_noun, but it is readable and consistent in style.

    Tool Count5/5

    With only 4 tools, the server is well-scoped for a focused forensics purpose. Each tool provides a distinct slice of information without unnecessary bloat.

    Completeness4/5

    The set covers the basic forensics workflow: repo overview, change history, hotspot identification, and hygiene checks. Minor gaps exist, such as lacking diff or blame tools for deeper investigation, but the current surface is functional for its stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A specialized MCP server for in-depth analysis of git repositories, offering tools for branch overview, time period analysis, file changes, and merge recommendations.
      4
      7
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      A local Git intelligence MCP server that provides deep repository analytics including hotspots, temporal coupling, knowledge maps, churn analysis, and risk scoring for AI agents.
      12
      12
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A local Git intelligence MCP server that provides deep repository analytics including hotspots, churn, knowledge maps, and risk scoring, all computed from commit history without data leaving your machine.
      12
      MIT