Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.rog0x/git

NPM · @ROG0X/MCP-GIT-TOOLS · SCANNED SEP 21

Git log, diff, blame, branch stats for AI agents

0 this week 85 Trust /100
Trust breakdown (7 categories)

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
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 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 184 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 Management93
  • Stability observed for 28 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
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
Install

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

# add to Claude Code
claude mcp add rog0x-git -- npx -y @rog0x/mcp-git-tools
// .cursor/mcp.json
{
  "mcpServers": {
    "rog0x-git": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-git-tools"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rog0x-git": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-git-tools"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rog0x-git -- npx -y @rog0x/mcp-git-tools
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rog0x-git": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@rog0x/mcp-git-tools"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rog0x-git --command npx --arg -y --arg @rog0x/mcp-git-tools
# ~/.hermes/config.yaml
mcp_servers:
  rog0x-git:
    command: "npx"
    args: ["-y", "@rog0x/mcp-git-tools"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rog0x-git": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@rog0x/mcp-git-tools"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rog0x-git -t stdio -c npx -a -y @rog0x/mcp-git-tools
// mcp.json
{
  "mcpServers": {
    "rog0x-git": {
      "command": "npx",
      "args": [
        "-y",
        "@rog0x/mcp-git-tools"
      ]
    }
  }
}
Changelog

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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
Diagnostics

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 21 Sept 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 →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~598 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
endLinenumberEnd line number (1-based, inclusive).
filePathstringyesPath to the file (relative to repo root).
refstringCommit ref to blame at (defaults to HEAD).
repoPathstringyesAbsolute path to the local Git repository.
startLinenumberStart 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.

NameTypeReqDescription
baseBranchstringBase branch to compare against. Defaults to 'main' or 'master'.
includeRemotebooleanInclude remote-tracking branches.
mergedOnlybooleanShow only branches merged into base branch.
repoPathstringyesAbsolute path to the local Git repository.
unmergedOnlybooleanShow 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.

NameTypeReqDescription
fromstringStart ref (commit hash, branch, tag). Defaults to HEAD~1.
pathstringLimit diff to a specific file or directory.
repoPathstringyesAbsolute path to the local Git repository.
summaryOnlybooleanIf true, return only stat summary without full diff.
tostringEnd 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.

NameTypeReqDescription
authorstringFilter commits by author name or email (substring match).
countnumberNumber of recent commits to return. Defaults to 20.
pathstringFilter commits that touched this file or directory path.
repoPathstringyesAbsolute path to the local Git repository.
sincestringShow commits after this date (ISO 8601 or natural language).
untilstringShow 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.

NameTypeReqDescription
repoPathstringyesAbsolute path to the local Git repository.
topAuthorsnumberNumber of top authors to include. Defaults to 10.
topFilesnumberNumber of most-changed files to include. Defaults to 10.

No output schema declared.

No examples provided.

Common questions

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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 21 September 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.