Dig

io.github.nakishiyamanPublished by GitHub account nakishiyamanv0.4.1Updated Oct 24, 2026

MCP server for code archaeology: git blame, file history, contributors, and co-change analysis

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

An MCP server for code archaeology that lets an assistant inspect git blame, file history, contributors, and co-change patterns in a repository.

What you can do
Dig exposes repository history analysis to an assistant. Based on its description, it covers git blame, file history, contributor information, and co-change analysis, so an assistant can trace who changed lines, how a file evolved, who has worked on it, and which files tend to change together. It runs locally over stdio and is intended for desktop use.
When to use it
Worth adding when an assistant needs to reason about the history of a codebase rather than just its current state, for example investigating when a bug was introduced, finding the right reviewer for a file, or spotting files that change together. It is aimed at local development work on git repositories.
Requirements
Runs as a local process over stdio, installed from the npm package mcp-server-dig, so Node.js and npm are needed. It is desktop-only and not available as a web executable. No authentication, environment variables, or headers are declared.
Before you install
The description does not state whether the tools only read history or can also modify the repository, so confirm that before use. It reads repository data, including commit metadata such as author names and emails, which is sent to the assistant model. No credentials or secrets are requested.

Installation

In SourceWeft

  1. Open Dig 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

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.1LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.