io.github.tonyweckstrom1987/git-history
NPM · MCP-SERVER-GIT-HISTORY
Give AI agents Git history tools: commit search, file history, blame, contributors, ref diffs.
Available components
Last scanned (4 hours 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.
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
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 97 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 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 722 tokens (~103/item across 7 items; 7 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 −75
- CVE-2026-102828 affects this package: high ▼ critical
- CVE-2026-102829 affects this package: high ▼ critical
- Known CVEs: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Security disclosure: fail → unverified ▼ functional
- 4 Oct 26 +4
- Stability: unverified → 0.27 ▲ 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 5 Nov 2026 · Analysed npm/mcp-server-git-history@1.1.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 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 →
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 →
blame_file Hae tiedoston blame-tiedot ~143
Hakee tiedoston rivikohtaisen 'git blame' -tiedon: kuka ja missä commitissa kunkin rivin viimeksi kirjoitti. Käytä kun haluat selvittää KUKA kirjoitti tietyn rivin ja MISSÄ commitissa se tuli mukaan.
| Name | Type | Req | Description |
|---|---|---|---|
| endLine | integer | – | Rajaa blame päättymään tähän riviin (annettava yhdessä startLinen kanssa) |
| filePath | string | yes | Tiedoston polku repositorion juuresta (esim. src/index.js) |
| startLine | integer | – | Rajaa blame alkamaan tästä rivistä (annettava yhdessä endLinen kanssa) |
No output schema declared.
No examples provided.
get_commit_diff Hae commitin diffi ~61
Hakee tietyn commitin koko diffin (kaikki tiedostomuutokset). Käytä kun haluat nähdä TARKALLEEN mitä muuttui.
| Name | Type | Req | Description |
|---|---|---|---|
| commitHash | string | yes | Commitin hash (lyhyt tai pitkä muoto) |
No output schema declared.
No examples provided.
get_contributors Hae committaajayhteenveto ~88
Hakee yhteenvedon repositorion committaajista ja heidän commit-määristään (kuten 'git shortlog -sn'). Käytä kun haluat yleiskuvan siitä, KEITÄ projektissa on ollut mukana ja kuinka aktiivisia he ovat olleet.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Enintään näin monta committaajaa (oletus 20) |
No output schema declared.
No examples provided.
get_diff_between_refs Hae diffi kahden viitteen välillä ~150
Hakee diffin kahden commitin, branchin tai tagin välillä, valinnaisesti rajattuna yhteen tiedostoon. Käytä kun haluat verrata kahta pistettä historiassa (esim. kahta branchia tai releasea), et vain yhtä commitia.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | – | Rajaa diffi tähän tiedostoon (valinnainen) |
| fromRef | string | yes | Lähtöviite (commit-hash, branch tai tag), esim. 'main' tai 'v1.0.0' |
| toRef | string | yes | Kohdeviite (commit-hash, branch tai tag), esim. 'HEAD' |
No output schema declared.
No examples provided.
get_file_history Hae tiedoston muutoshistoria ~115
Hakee tiedoston muutoshistorian: milloin sitä on muokattu, kuka muokkasi ja mihin commit-viestiin muutos liittyi. Käytä kun haluat selvittää MILLOIN ja KUKA muokkasi tiettyä tiedostoa viimeksi.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Tiedoston polku repositorion juuresta (esim. src/index.js) |
| limit | integer | – | Enintään näin monta tulosta (oletus 20) |
No output schema declared.
No examples provided.
get_recent_commits Hae uusimmat commitit ~68
Hakee repositorion uusimmat commitit uusimmasta vanhimpaan. Käytä kun haluat yleiskuvan siitä, mitä projektissa on viime aikoina tehty.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Enintään näin monta tulosta (oletus 10) |
No output schema declared.
No examples provided.
search_commits Etsi commiteja ~97
Etsii Git-commiteja joiden commit-viesti sisältää annetun hakusanan (esim. bugin numero tai avainsana). Käytä tätä kun haluat selvittää MIKSI jokin muutos tehtiin.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Enintään näin monta tulosta (oletus 20) |
| query | string | yes | Hakusana tai -lause commit-viesteistä |
No output schema declared.
No examples provided.
How do I install the io.github.tonyweckstrom1987/git-history MCP server?
io.github.tonyweckstrom1987/git-history runs locally as an npm package, launched with npx -y mcp-server-git-history. 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-git-history
claude mcp add tonyweckstrom1987-git-history -- npx -y mcp-server-git-history
What is the io.github.tonyweckstrom1987/git-history MCP server?
io.github.tonyweckstrom1987/git-history is an MCP server listed in the public MCP registry as io.github.tonyweckstrom1987/git-history. Give AI agents Git history tools: commit search, file history, blame, contributors, ref diffs. This page covers its npm package (mcp-server-git-history).
What tools does the io.github.tonyweckstrom1987/git-history MCP server expose?
io.github.tonyweckstrom1987/git-history exposes 7 tools: search_commits, get_recent_commits, get_commit_diff, get_file_history, blame_file, and 2 more. Their descriptions and schemas cost roughly 722 tokens of context every time the server is loaded.
Is the io.github.tonyweckstrom1987/git-history MCP server still maintained?
io.github.tonyweckstrom1987/git-history 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.tonyweckstrom1987/git-history MCP server under?
io.github.tonyweckstrom1987/git-history declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.