# io.github.nakishiyaman/dig (npm · mcp-server-dig)

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

- Trust score: 64/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `mcp-server-dig`: 64/100 (this document), [markdown](https://verifymcp.io/servers/nakishiyaman-dig/mcp-server-dig.md), [page](https://verifymcp.io/servers/nakishiyaman-dig/mcp-server-dig)

## Channel facts

- Registry: `npm`
- Package: `mcp-server-dig`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 138 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 906 tokens (~113/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add nakishiyaman-dig -- npx -y mcp-server-dig
```

### Codex

```bash
codex mcp add nakishiyaman-dig -- npx -y mcp-server-dig
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nakishiyaman-dig": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-dig"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nakishiyaman-dig --command npx --arg -y --arg mcp-server-dig
```

### Hermes

```yaml
mcp_servers:
  nakishiyaman-dig:
    command: "npx"
    args: ["-y", "mcp-server-dig"]
```

### Other

```json
{
  "mcpServers": {
    "nakishiyaman-dig": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-dig"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +33)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-02 (score 31, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-01 (score 16, +16)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 0, −22)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 22, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 40)

First indexed and scored.

## MCP tools (8)

### `git_file_history` (~101 tokens)

Get the commit history for a specific file. Useful for understanding how and why a file evolved over time.

Input parameters:

- `file_path` (string, required): Relative path to the file within the repo
- `max_commits` (integer): Maximum number of commits to return
- `repo_path` (string, required): Absolute path to the git repository
- `since` (string): Date filter, e.g. "2024-01-01" or "6 months ago"

### `git_blame_context` (~91 tokens)

Get blame information with semantic context — who wrote each section and when. Groups consecutive lines by the same commit into blocks for easier comprehension.

Input parameters:

- `end_line` (integer): End of line range
- `file_path` (string, required): Relative path to the file within the repo
- `repo_path` (string, required): Absolute path to the git repository
- `start_line` (integer): Start of line range

### `git_related_changes` (~96 tokens)

Find files that frequently change together with a given file (co-change analysis). Useful for understanding implicit dependencies and finding related code.

Input parameters:

- `file_path` (string, required): Relative path to the file within the repo
- `max_commits` (integer): How many commits to analyze
- `min_coupling` (integer): Minimum co-change count to include in results
- `repo_path` (string, required): Absolute path to the git repository

### `git_contributor_patterns` (~115 tokens)

Analyze contributor patterns — who has expertise in what areas. Useful for identifying reviewers, understanding code ownership, and finding domain experts.

Input parameters:

- `max_commits` (integer): Maximum number of commits to analyze
- `path_pattern` (string): Directory or path to scope analysis, e.g. "src/api/" or "lib/"
- `repo_path` (string, required): Absolute path to the git repository
- `since` (string): Date filter, e.g. "2024-01-01" or "1 year ago"

### `git_search_commits` (~136 tokens)

Search commit messages by keyword. Useful for finding when a feature was introduced, a bug was fixed, or locating commits related to a ticket number.

Input parameters:

- `author` (string): Filter by author name or email
- `max_commits` (integer): Maximum number of commits to return
- `path_pattern` (string): Limit search to commits touching this path
- `query` (string, required): Search string to match against commit messages
- `repo_path` (string, required): Absolute path to the git repository
- `since` (string): Date filter, e.g. "2024-01-01" or "6 months ago"

### `git_commit_show` (~95 tokens)

Show detailed information about a specific commit: full message, changed files, and optionally the diff. Useful for drilling into a commit found via git_search_commits.

Input parameters:

- `commit` (string, required): Commit hash (short or full), branch name, or tag
- `repo_path` (string, required): Absolute path to the git repository
- `show_diff` (boolean): Include the full diff output (default: false, shows stat only)

### `git_diff_context` (~134 tokens)

Show the diff between two commits, branches, or tags. Useful for understanding what changed between releases, branches, or any two points in history.

Input parameters:

- `commit` (string, required): Target commit, branch, or tag
- `compare_to` (string): Base to compare against (default: parent commit)
- `context_lines` (integer): Number of context lines in unified diff (default: 3)
- `file_path` (string): Limit diff to a specific file
- `repo_path` (string, required): Absolute path to the git repository
- `stat_only` (boolean): Show only file change statistics (default: false)

### `git_hotspots` (~138 tokens)

Identify the most frequently changed files in the repository. Files with high change frequency often indicate areas of technical debt, active development, or bug-prone code.

Input parameters:

- `max_commits` (integer): Number of commits to analyze (default: 500)
- `path_pattern` (string): Limit analysis to a specific directory, e.g. 'src/'
- `repo_path` (string, required): Absolute path to the git repository
- `since` (string): Date filter, e.g. "2024-01-01" or "6 months ago"
- `top_n` (integer): Number of top files to return (default: 20)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/nakishiyaman-dig/mcp-server-dig#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 31
- 2026-08-01: 16
- 2026-07-31: 0
- 2026-07-30: 22
- 2026-07-28: 40
- 2026-07-27: 40

## Links

- npm package: https://www.npmjs.com/package/mcp-server-dig
- Socket report: https://socket.dev/npm/package/mcp-server-dig
- Changelog RSS feed: https://verifymcp.io/servers/nakishiyaman-dig/mcp-server-dig/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/nakishiyaman-dig/mcp-server-dig/changelog.json
- HTML version of this page: https://verifymcp.io/servers/nakishiyaman-dig/mcp-server-dig