Git Forensics MCP

by davidorex

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Related Servers

Alternatives to Git Forensics MCP

No user-submitted related servers found.

Related Servers

git-intel-mcp
Version Control Code Analysis Developer Tools
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.
Updated a month ago (2026-08-19 14:40 UTC)
-
git-intel
Version Control Code Analysis Developer Tools
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.
Updated 2 months ago (2026-07-18 00:33 UTC)
12
MIT
repo-forensics-mcp
Version Control Code Analysis Developer Tools
mrfentmen
F
license
A
quality
C
maintenance
A local-only MCP server for understanding Git repositories, offering repository summary, recent changes, file hotspots, and hygiene checks without network access.
Updated a month ago (2026-08-08 23:50 UTC)
4
-
GitIntel
Version Control Code Analysis
hoangsonww
A
license
A
quality
A
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.
Updated 15 days ago (2026-09-07 20:41 UTC)
12
12
MIT
Codebase Intelligence MCP
Code Analysis Version Control Developer Tools
atishay2411
A
license
Not graded
quality
C
maintenance
A production-grade MCP server for local git repositories that provides tools for code search, git history analysis, complexity metrics, test discovery, and dependency management.
Updated 2 months ago (2026-07-18 20:27 UTC)
MIT
git-summary-mcp
Version Control Code Analysis Developer Tools
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.
Updated 5 months ago (2026-04-13 13:58 UTC)
76 npm
MIT

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

B3.3/5.0

Scored 2026-04-18 11:40 across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: analyze_file_changes focuses on file-level changes, analyze_time_period covers time-based activity, get_branch_overview provides branch states, and get_merge_recommendations handles merge strategies. The descriptions make it easy to differentiate between them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (analyze_file_changes, analyze_time_period, get_branch_overview, get_merge_recommendations) with clear, descriptive names. There are no deviations in naming conventions.

Tool Count4/5

With 4 tools, the count is reasonable for a Git forensics server, though it feels slightly minimal. Each tool appears to serve a distinct function, but the scope might benefit from a few more tools for broader coverage without being excessive.

Completeness3/5

The tools cover analysis and recommendations well, but there are notable gaps for a Git forensics domain, such as missing CRUD operations (e.g., no tools for creating or modifying data) and limited coverage of common forensic tasks like commit history analysis or user activity tracking. Agents might need workarounds for some scenarios.