io.github.rog0x/git
NPM · @ROG0X/MCP-GIT-TOOLS
Git log, diff, blame, branch stats for AI agents
Available components
Last scanned (3 hours ago)
Scores higher than 89% 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 Security98
- No malware found by supply-chain analysis.Pass
- A known CVE affects @rog0x/mcp-git-tools, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 230 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 598 tokens (~119/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- CVE-2026-106764 affects this package ▼ security
- Known CVEs: pass → partial ▼ security
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
- 21 Oct 26 +1
- Stability: 0.97 → pass security
- 20 Oct 26 −1
- Stability: pass → 0.97 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 6 Nov 2026 · Analysed npm/@rog0x/mcp-git-tools@1.0.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-jwc4-922r-f2rw | CVE-2026-106764 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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 ~114
Show who last modified each line of a file in a local Git repository, with commit hash, author, date, and line content.
| Name | Type | Req | Description |
|---|---|---|---|
| endLine | number | – | End line number (1-based, inclusive). |
| filePath | string | yes | Path to the file (relative to repo root). |
| ref | string | – | Commit ref to blame at (defaults to HEAD). |
| repoPath | string | yes | Absolute path to the local Git repository. |
| startLine | number | – | Start line number (1-based). |
No output schema declared.
No examples provided.
git_branch ~118
List branches in a local Git repository with last commit info, ahead/behind counts relative to a base branch, and merged/unmerged status.
| Name | Type | Req | Description |
|---|---|---|---|
| baseBranch | string | – | Base branch to compare against. Defaults to 'main' or 'master'. |
| includeRemote | boolean | – | Include remote-tracking branches. |
| mergedOnly | boolean | – | Show only branches merged into base branch. |
| repoPath | string | yes | Absolute path to the local Git repository. |
| unmergedOnly | boolean | – | Show only branches NOT merged into base branch. |
No output schema declared.
No examples provided.
git_diff ~128
Show diff between two commits, branches, or tags in a local Git repository. Returns a summary of files changed, insertions, deletions, and the full or filtered diff output.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start ref (commit hash, branch, tag). Defaults to HEAD~1. |
| path | string | – | Limit diff to a specific file or directory. |
| repoPath | string | yes | Absolute path to the local Git repository. |
| summaryOnly | boolean | – | If true, return only stat summary without full diff. |
| to | string | – | End ref. Defaults to HEAD. |
No output schema declared.
No examples provided.
git_log ~141
Get commit history from a local Git repository. Returns last N commits with hash, author, date, and message. Supports filtering by author, date range, and file path.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Filter commits by author name or email (substring match). |
| count | number | – | Number of recent commits to return. Defaults to 20. |
| path | string | – | Filter commits that touched this file or directory path. |
| repoPath | string | yes | Absolute path to the local Git repository. |
| since | string | – | Show commits after this date (ISO 8601 or natural language). |
| until | string | – | Show commits before this date. |
No output schema declared.
No examples provided.
git_stats ~97
Get comprehensive statistics for a local Git repository: total commits, contributors, first/last commit dates, commits per author, commits per month, and most frequently changed files.
| Name | Type | Req | Description |
|---|---|---|---|
| repoPath | string | yes | Absolute path to the local Git repository. |
| topAuthors | number | – | Number of top authors to include. Defaults to 10. |
| topFiles | number | – | Number of most-changed files to include. Defaults to 10. |
No output schema declared.
No examples provided.
How do I install the io.github.rog0x/git MCP server?
io.github.rog0x/git runs locally as an npm package, launched with npx -y @rog0x/mcp-git-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-git-tools
claude mcp add rog0x-git -- npx -y @rog0x/mcp-git-tools
What is the io.github.rog0x/git MCP server?
io.github.rog0x/git is an MCP server listed in the public MCP registry as io.github.rog0x/git. Git log, diff, blame, branch stats for AI agents. This page covers its npm package (@rog0x/mcp-git-tools).
Is the io.github.rog0x/git MCP server safe to use?
io.github.rog0x/git scores 86 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 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.rog0x/git MCP server expose?
io.github.rog0x/git exposes 5 tools: git_log, git_diff, git_blame, git_stats, git_branch. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.
Is the io.github.rog0x/git MCP server still maintained?
io.github.rog0x/git is still listed as active in the MCP registry. We last reached this channel on 6 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.rog0x/git MCP server under?
io.github.rog0x/git declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/git MCP server?
VerifyMCP ran 15 checks on io.github.rog0x/git, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.rog0x/git: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.