Git Reflog Archaeologist Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 30, 2026

Aggregate local Git reflog and recovery signals without exposing repository content. Tools...

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that summarizes Git reflog, stash and unreachable-object signals to hint whether lost work may still be recoverable.

What you can do
  • Summarize reflog activity: entry counts, age buckets, and loose or packed object counts
  • Summarize recovery potential: unreachable object counts grouped by type
  • Summarize stashes: stash count and age buckets
  • Return coarse hints such as recent-history-may-be-recoverable or unreachable-commits-found, without hashes, refs, paths, authors or file contents
When to use it
Useful right after an accidental reset, a deleted branch or an abandoned experiment, when you want a quick, privacy-preserving read on whether Git metadata suggests recovery is still possible before digging further.
Requirements
Runs as a local Node.js process installed from the npm package and started over stdio; a GIT_ARCHAEOLOGY_ROOT setting bounds which repository can be inspected. No network access, accounts or API keys are needed.
Before you install
It only reports signals and does not guarantee that anything can be restored. It reads local Git metadata, so point GIT_ARCHAEOLOGY_ROOT at the intended repository; it does not run mutating commands such as reset, prune or garbage collection.

Installation

In SourceWeft

  1. Open Git Reflog Archaeologist 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

git-reflog-archaeologist-mcp

Git Reflog Archaeologist is a local MCP for the moment after an accidental reset, deleted branch, or abandoned experiment. It looks at Git metadata that can help answer whether recovery may still be possible.

Tools

  • reflog_signals: aggregate reflog count, age buckets, and loose or packed object counts
  • recovery_signals: aggregate unreachable object counts by type
  • stash_signals: aggregate stash count and age buckets

The outputs include coarse recovery hints such as recent-history-may-be-recoverable or unreachable-commits-found. They do not return commit hashes, subjects, ref names, file paths, remote names, author data, or file contents.

Safety

  • Local Git commands only. No network access is used.
  • The selected repository must stay inside GIT_ARCHAEOLOGY_ROOT.
  • Git output is line and count bounded.
  • The server never runs mutating commands such as reset, reflog expire, prune, or garbage collection.
  • This is a recovery signal tool, not a guarantee that an object can be restored.

Run

bash
npm installnpm run buildnode dist/index.js

The server uses stdio and works with Claude Desktop, Cursor, VS Code, MCP Inspector, and compatible CLI harnesses.

Source: README.md at commit 0c1fbdd

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.