io.github.nakishiyaman/dig
NPM · MCP-SERVER-DIG · SCANNED AUG 3
MCP server for code archaeology: git blame, file history, contributors, and co-change analysis
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 138 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · mcp-server-dig
claude mcp add nakishiyaman-dig -- npx -y mcp-server-dig
codex mcp add nakishiyaman-dig -- npx -y mcp-server-dig
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nakishiyaman-dig": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-server-dig"
],
"enabled": true
}
}
} openclaw mcp add nakishiyaman-dig --command npx --arg -y --arg mcp-server-dig
mcp_servers:
nakishiyaman-dig:
command: "npx"
args: ["-y", "mcp-server-dig"] {
"mcpServers": {
"nakishiyaman-dig": {
"command": "npx",
"args": [
"-y",
"mcp-server-dig"
]
}
}
} 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 Aug 26 +33
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 1 Aug 26 +16
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −22
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 40
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.