io.github.nakishiyaman/dig
NPM · MCP-SERVER-DIG
MCP server for code archaeology: git blame, file history, contributors, and co-change analysis
Available components
Last scanned (23 hours ago)
Scores higher than 51% of npm servers
Category Version Control
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 232 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −3
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/mcp-server-dig@0.4.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
git_blame_context ~91
Get blame information with semantic context — who wrote each section and when. Groups consecutive lines by the same commit into blocks for easier comprehension.
| Name | Type | Req | Description |
|---|---|---|---|
| end_line | integer | – | End of line range |
| file_path | string | yes | Relative path to the file within the repo |
| repo_path | string | yes | Absolute path to the git repository |
| start_line | integer | – | Start of line range |
No output schema declared.
No examples provided.
git_commit_show ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | Commit hash (short or full), branch name, or tag |
| repo_path | string | yes | Absolute path to the git repository |
| show_diff | boolean | – | Include the full diff output (default: false, shows stat only) |
No output schema declared.
No examples provided.
git_contributor_patterns ~115
Analyze contributor patterns — who has expertise in what areas. Useful for identifying reviewers, understanding code ownership, and finding domain experts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute path to the git repository |
| since | string | – | Date filter, e.g. "2024-01-01" or "1 year ago" |
No output schema declared.
No examples provided.
git_diff_context ~134
Show the diff between two commits, branches, or tags. Useful for understanding what changed between releases, branches, or any two points in history.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | 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 | yes | Absolute path to the git repository |
| stat_only | boolean | – | Show only file change statistics (default: false) |
No output schema declared.
No examples provided.
git_file_history ~101
Get the commit history for a specific file. Useful for understanding how and why a file evolved over time.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | Relative path to the file within the repo |
| max_commits | integer | – | Maximum number of commits to return |
| repo_path | string | yes | Absolute path to the git repository |
| since | string | – | Date filter, e.g. "2024-01-01" or "6 months ago" |
No output schema declared.
No examples provided.
git_hotspots ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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) |
No output schema declared.
No examples provided.
git_related_changes ~96
Find files that frequently change together with a given file (co-change analysis). Useful for understanding implicit dependencies and finding related code.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | 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 | yes | Absolute path to the git repository |
No output schema declared.
No examples provided.
git_search_commits ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Search string to match against commit messages |
| repo_path | string | yes | Absolute path to the git repository |
| since | string | – | Date filter, e.g. "2024-01-01" or "6 months ago" |
No output schema declared.
No examples provided.
How do I install the io.github.nakishiyaman/dig MCP server?
io.github.nakishiyaman/dig runs locally as an npm package, launched with npx -y mcp-server-dig. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-dig
claude mcp add nakishiyaman-dig -- npx -y mcp-server-dig
What is the io.github.nakishiyaman/dig MCP server?
io.github.nakishiyaman/dig is an MCP server listed in the public MCP registry as io.github.nakishiyaman/dig. MCP server for code archaeology: git blame, file history, contributors, and co-change analysis. This page covers its npm package (mcp-server-dig).
Is the io.github.nakishiyaman/dig MCP server safe to use?
io.github.nakishiyaman/dig scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.nakishiyaman/dig MCP server expose?
io.github.nakishiyaman/dig exposes 8 tools: git_file_history, git_blame_context, git_related_changes, git_contributor_patterns, git_search_commits, and 3 more. Their descriptions and schemas cost roughly 906 tokens of context every time the server is loaded.
Is the io.github.nakishiyaman/dig MCP server still maintained?
io.github.nakishiyaman/dig is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.nakishiyaman/dig MCP server under?
io.github.nakishiyaman/dig declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.