Skip to main content
Glama
mrfentmen

repo-forensics-mcp

by mrfentmen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to repo-forensics-mcp

No user-submitted related servers found.

    Related Servers

    • git-intel

      JBrightmanAI
      A
      license
      A
      quality
      C
      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

    • GitIntel

      hoangsonww
      A
      license
      A
      quality
      B
      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

    • git-intel-mcp

      s-zaid-13
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that analyzes Git repository history and provides insights through AI-compatible tools. It supports hotspot detection, contributor analysis, and code churn tracking.
      -

    • git-summary-mcp

      yifanyifan897645
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants deep understanding of your local Git repositories, providing instant repo overviews, change summaries, blame analysis, changelogs, branch health checks, and history search.
      76 npm
      MIT

    • Git Forensics MCP

      davidorex
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources