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.yifanyifan897645/git-summary

NPM · GIT-SUMMARY-MCP

Git repo intelligence: summaries, blame, changelogs, branch health, and history search

Available components

0 this week 0 Trust /100

Last scanned (27 minutes ago)

Scores higher than 0% of npm servers

Category Version Control

Recent critical change

CVE-2026-102828 affects this package (11 Oct 2026). See the changelog before you install this server.

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 Security73
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 536 tokens (~89/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
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.

  • 4 Nov 26 0
    • Stability: pass → 0.93 functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 26 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.80 → pass security
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 5 Nov 2026 · Analysed npm/git-summary-mcp@0.1.2

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 4 findings
ID CVE Severity Vector Fix available
GHSA-v5rq-49vh-5v5c CVE-2026-102829 critical yes
GHSA-858h-whjf-mvg5 CVE-2026-102827 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-g4wm-2vf7-vfgr CVE-2026-102826 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-x6jw-m9v5-85vh CVE-2026-102828 critical yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 97 packages
Packages resolved 97
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~536 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 ~104

Analyze who wrote each line of a file, when, and in which commit. Get top contributors and ownership breakdown. Optionally limit to a line range.

NameTypeReqDescription
end_linenumber–End line number (optional, for partial blame)
filestringyesFile path relative to repo root
repo_pathstring–Path to the Git repository (defaults to cwd)
start_linenumber–Start line number (optional, for partial blame)

No output schema declared.

No examples provided.

git_branch_health ~55

Analyze all local branches: find stale branches, merged branches ready for cleanup, and branches that are ahead/behind. Helps keep your repo tidy.

NameTypeReqDescription
repo_pathstring–Path to the Git repository (defaults to cwd)

No output schema declared.

No examples provided.

git_changelog ~105

Auto-generate a changelog from Git commits. Groups commits by type (feat, fix, docs, etc.) using conventional commit format. Specify a range or get the full log.

NameTypeReqDescription
fromstring–Start commit/tag (e.g. 'v1.0.0')
repo_pathstring–Path to the Git repository (defaults to cwd)
tostring–End commit/tag (e.g. 'v2.0.0')

No output schema declared.

No examples provided.

git_changes ~107

Get a summary of changes in a commit range: what files changed, who changed them, and a diff stat. Useful for understanding what happened between two points in history.

NameTypeReqDescription
max_commitsnumber–Max commits to analyze (default 30)
rangestring–Git commit range, e.g. 'main..feature' or 'HEAD~5..HEAD' or a tag range
repo_pathstring–Path to the Git repository (defaults to cwd)

No output schema declared.

No examples provided.

git_search ~92

Search through Git history for commits matching a query. Searches both commit messages and code changes (pickaxe search). Find when a change was introduced or a bug was created.

NameTypeReqDescription
max_resultsnumber–Maximum results to return (default 20)
querystringyesSearch term to find in commit messages or code changes
repo_pathstring–Path to the Git repository (defaults to cwd)

No output schema declared.

No examples provided.

git_summary ~73

Get a structured overview of a Git repository: current branch, recent commits, contributors, and repo stats. Works on any local Git repo.

NameTypeReqDescription
commit_countnumber–Number of recent commits to include (default 20)
repo_pathstring–Path to the Git repository (defaults to current working directory)

No output schema declared.

No examples provided.

Install

How do I install the io.github.yifanyifan897645/git-summary MCP server?

io.github.yifanyifan897645/git-summary runs locally as an npm package, launched with npx -y git-summary-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · git-summary-mcp

# add to Claude Code
claude mcp add yifanyifan897645-git-summary -- npx -y git-summary-mcp
Common questions

What is the io.github.yifanyifan897645/git-summary MCP server?

io.github.yifanyifan897645/git-summary is an MCP server listed in the public MCP registry as io.github.yifanyifan897645/git-summary. Git repo intelligence: summaries, blame, changelogs, branch health, and history search. This page covers its npm package (git-summary-mcp).

What tools does the io.github.yifanyifan897645/git-summary MCP server expose?

io.github.yifanyifan897645/git-summary exposes 6 tools: git_summary, git_changes, git_blame, git_changelog, git_branch_health, git_search. Their descriptions and schemas cost roughly 536 tokens of context every time the server is loaded.

Is the io.github.yifanyifan897645/git-summary MCP server still maintained?

io.github.yifanyifan897645/git-summary is still listed as active in the MCP registry. We last reached this channel on 5 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.yifanyifan897645/git-summary MCP server under?

io.github.yifanyifan897645/git-summary declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.