git-reflog-archaeologist-mcp
Related Servers
Alternatives to git-reflog-archaeologist-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn 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.23 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for fast, bounded, read-only Git evidence, enabling AI agents to query commit history, diffs, status, and snapshots by parsing repository storage directly.345 npmMIT
- AlicenseBqualityDmaintenanceA specialized MCP server for in-depth analysis of git repositories, offering tools for branch overview, time period analysis, file changes, and merge recommendations.47Apache 2.0
- FlicenseAqualityCmaintenanceA local-only MCP server for understanding Git repositories, offering repository summary, recent changes, file hotspots, and hygiene checks without network access.4-
- FlicenseAqualityDmaintenanceAn MCP server that transforms repositories into queryable knowledge by combining static code analysis with git history tracking. It allows users to investigate codebase structure, identify fragile files based on churn, and receive risk assessments through natural language queries.7-
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that provides read-only access to Git repository history, exposing commit metadata and optionally content patches via configurable policies, with optional AI-powered analysis while never modifying Git state.13 npmApache 2.0
TDQS
Scored across 3 tools
Each tool targets a distinct Git data source: reflog, unreachable objects, and stash. The descriptions clearly separate their inputs and outputs, leaving no ambiguity about which tool to choose for a given task.
All tool names follow the exact same pattern of '<domain>_signals', creating a predictable and uniform naming scheme. This consistency makes it easy to infer the purpose of any tool in the set.
With only three tools, the server is tightly scoped to its 'archaeologist' purpose. Each tool covers a different aspect of Git history recovery, and none feel redundant or extraneous.
The server covers the main recovery-related signals: reflog activity, unreachable objects, and stash state. While other signals like branch or tag history could be added, the core recovery workflow is well represented and no critical gaps are apparent.