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.Dave-London/pare-git

NPM · @PARETOOLS/GIT

Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON.

Available components

0 this week 94 Trust /100

Last scanned (18 hours ago)

Scores higher than 97% of npm servers

Category Version Control

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
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Dave-London/Pare). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 15 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1958 tokens (~97/item across 20 items; 20 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 21 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.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 19 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 16 Oct 26 +1

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

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 4 Nov 2026 · Analysed npm/@paretools/git@0.8.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Dave-London/Pare
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Dave-London/Pare/.github/workflows/release.yml@refs/heads/main
Rekor log index 952352681
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:931f1e043e0ef2b4de69ae6b8a8308a277339843ca339624f01fcd4e84998c855e5db4246355cec83b6f3ce9405b38a3481ea7706c2eed15cf97324c6

Background: How many MCP packages publish verified provenance →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,910 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
add ~81

Stages files for commit. Returns structured data with count and list of staged files. Use instead of running `git add` in the terminal.

NameTypeReqDescription
allboolean–Stage all changes (git add -A)
filesarray–File paths to stage (required unless all is true)
pathstring–Repository path (default: cwd)
NameTypeReqDescription
filesarrayyes–
stagednumberyes–

No examples provided.

blame ~129

Shows commit annotations for a file, grouped by commit. Returns structured blame data with deduplicated commit metadata (hash, author, date) and their attributed lines. Use instead of running `git blame` in the terminal.

NameTypeReqDescription
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
endLinenumber–End line number for blame range
filestringyesFile path to blame
pathstring–Repository path (default: cwd)
startLinenumber–Start line number for blame range
NameTypeReqDescription
commits–yes–
filestringyes–
totalLinesnumberyes–

No examples provided.

branch ~106

Lists, creates, or deletes branches. Returns structured branch data. Use instead of running `git branch` in the terminal.

NameTypeReqDescription
allboolean–Include remote branches
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
createstring–Create a new branch with this name
deletestring–Delete branch with this name
pathstring–Repository path (default: cwd)
NameTypeReqDescription
branches–yes–
currentstringyes–

No examples provided.

checkout ~85

Switches branches or restores files. Returns structured data with ref, previous ref, and whether a new branch was created. Use instead of running `git checkout` in the terminal.

NameTypeReqDescription
createboolean–Create a new branch (-b)
pathstring–Repository path (default: cwd)
refstringyesBranch name, tag, or commit to checkout
NameTypeReqDescription
createdbooleanyes–
previousRefstringyes–
refstringyes–

No examples provided.

cherry-pick ~105

Applies specific commits to the current branch. Returns structured data with applied commits and any conflicts. Use instead of running `git cherry-pick` in the terminal.

NameTypeReqDescription
abortboolean–Abort in-progress cherry-pick
commitsarray–Commit hashes to cherry-pick
continueboolean–Continue after resolving conflicts
noCommitboolean–Apply changes without committing (-n)
pathstring–Repository path (default: cwd)
NameTypeReqDescription
appliedarrayyes–
conflictsarrayyes–
successbooleanyes–

No examples provided.

commit ~72

Creates a commit with the given message. Returns structured data with hash, message, and change statistics. Use instead of running `git commit` in the terminal.

NameTypeReqDescription
amendboolean–Amend the previous commit
messagestringyesCommit message
pathstring–Repository path (default: cwd)
NameTypeReqDescription
deletionsnumberyes–
filesChangednumberyes–
hashstringyes–
hashShortstringyes–
insertionsnumberyes–
messagestringyes–

No examples provided.

diff ~129

Returns file-level diff statistics as structured data. Use full=true for patch content. Use instead of running `git diff` in the terminal.

NameTypeReqDescription
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
filestring–Limit diff to a specific file
fullboolean–Include full patch content in chunks
pathstring–Repository path (default: cwd)
refstring–Compare against a specific ref (branch, tag, commit)
stagedboolean–Show staged changes (--cached)
NameTypeReqDescription
filesarrayyes–
totalAdditionsnumber––
totalDeletionsnumber––
totalFilesnumberyes–

No examples provided.

log ~111

Returns commit history as structured data. Use instead of running `git log` in the terminal.

NameTypeReqDescription
authorstring–Filter by author name or email
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
maxCountnumber–Number of commits to return (default: 10)
pathstring–Repository path (default: cwd)
refstring–Branch, tag, or commit to start from
NameTypeReqDescription
commitsarrayyes–
totalnumberyes–

No examples provided.

merge ~108

Merges a branch into the current branch. Returns structured data with merge status, fast-forward detection, conflicts, and commit hash. Use instead of running `git merge` in the terminal.

NameTypeReqDescription
abortboolean–Abort in-progress merge (--abort)
branchstringyesBranch to merge
messagestring–Custom merge commit message
noFfboolean–Force merge commit (--no-ff)
pathstring–Repository path (default: cwd)
NameTypeReqDescription
branchstringyes–
commitHashstring––
conflictsarrayyes–
fastForwardbooleanyes–
mergedbooleanyes–

No examples provided.

pull ~103

Pulls changes from a remote repository. Returns structured data with success status, summary, change statistics, and any conflicts. Use instead of running `git pull` in the terminal.

NameTypeReqDescription
branchstring–Branch to pull (default: current tracking branch)
pathstring–Repository path (default: cwd)
rebaseboolean–Use rebase instead of merge (--rebase)
remotestring–Remote name (default: "origin")
NameTypeReqDescription
conflictsarrayyes–
deletionsnumberyes–
filesChangednumberyes–
insertionsnumberyes–
successbooleanyes–
summarystringyes–

No examples provided.

push ~108

Pushes commits to a remote repository. Returns structured data with success status, remote, branch, and summary. Use instead of running `git push` in the terminal.

NameTypeReqDescription
branchstring–Branch to push (default: current branch)
forceboolean–Force push (--force)
pathstring–Repository path (default: cwd)
remotestring–Remote name (default: "origin")
setUpstreamboolean–Set upstream tracking (-u)
NameTypeReqDescription
branchstringyes–
remotestringyes–
successbooleanyes–
summarystringyes–

No examples provided.

rebase ~112

Rebases the current branch onto a target branch. Supports abort and continue for conflict resolution. Returns structured data with success status, branch info, conflicts, and rebased commit count. Use instead of running `git rebase` in the terminal.

NameTypeReqDescription
abortboolean–Abort in-progress rebase
branchstring–Target branch to rebase onto (required unless abort/continue)
continueboolean–Continue after conflict resolution
pathstring–Repository path (default: cwd)
NameTypeReqDescription
branchstringyes–
conflictsarrayyes–
currentstringyes–
rebasedCommitsnumber––
successbooleanyes–

No examples provided.

remote ~73

Lists remote repositories with fetch and push URLs. Returns structured remote data. Use instead of running `git remote -v` in the terminal.

NameTypeReqDescription
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstring–Repository path (default: cwd)
NameTypeReqDescription
remotes–yes–
totalnumberyes–

No examples provided.

reset ~93

Unstages files by resetting them to a ref (default: HEAD). Returns structured data with the ref and list of unstaged files. Use instead of running `git reset` in the terminal.

NameTypeReqDescription
filesarray–File paths to unstage (omit to unstage all)
pathstring–Repository path (default: cwd)
refstring–Ref to reset to (default: HEAD)
NameTypeReqDescription
refstringyes–
unstagedarrayyes–

No examples provided.

restore ~96

Discards working tree changes or restores files from a specific commit. Returns structured data with restored files, source ref, and staged flag. Use instead of running `git restore` in the terminal.

NameTypeReqDescription
filesarrayyesFile paths to restore
pathstring–Repository path (default: cwd)
sourcestring–Restore from specific ref (--source)
stagedboolean–Restore staged changes (--staged)
NameTypeReqDescription
restoredarrayyes–
sourcestringyes–
stagedbooleanyes–

No examples provided.

show ~86

Shows commit details and diff statistics for a given ref. Use instead of running `git show` in the terminal.

NameTypeReqDescription
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstring–Repository path (default: cwd)
refstring–Commit hash, branch, or tag (default: HEAD)
NameTypeReqDescription
authorstring––
datestring––
diffobject––
hashstring––
hashShortstring––
messagestringyes–

No examples provided.

stash ~109

Pushes, pops, applies, or drops stash entries. Returns structured result with action, success, and message. Use instead of running `git stash` in the terminal.

NameTypeReqDescription
actionstringyesStash action to perform
indexnumber–Stash index for pop/apply/drop (e.g., 0 for stash@{0})
messagestring–Stash message (only used with push action)
pathstring–Repository path (default: cwd)
NameTypeReqDescription
actionstringyes–
messagestringyes–
successbooleanyes–

No examples provided.

stash-list ~76

Lists all stash entries with index, message, and date. Returns structured stash data. Use instead of running `git stash list` in the terminal.

NameTypeReqDescription
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstring–Repository path (default: cwd)
NameTypeReqDescription
stashes–yes–
totalnumberyes–

No examples provided.

status ~52

Returns the working tree status as structured data (branch, staged, modified, untracked, conflicts). Use instead of running `git status` in the terminal.

NameTypeReqDescription
pathstring–Repository path (default: cwd)
NameTypeReqDescription
aheadnumber––
behindnumber––
branchstringyes–
cleanbooleanyes–
conflictsarrayyes–
deletedarrayyes–
modifiedarrayyes–
stagedarrayyes–
untrackedarrayyes–
upstreamstring––

No examples provided.

tag ~76

Lists tags sorted by creation date. Returns structured tag data with name, date, and message. Use instead of running `git tag` in the terminal.

NameTypeReqDescription
compactboolean–Auto-compact when structured output exceeds raw CLI tokens. Set false to always get full schema.
pathstring–Repository path (default: cwd)
NameTypeReqDescription
tags–yes–
totalnumberyes–

No examples provided.

Install

How do I install the io.github.Dave-London/pare-git MCP server?

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

npm · @paretools/git

# add to Claude Code
claude mcp add dave-london-pare-git -- npx -y @paretools/git
Common questions

What is the io.github.Dave-London/pare-git MCP server?

io.github.Dave-London/pare-git is an MCP server listed in the public MCP registry as io.github.Dave-London/pare-git. Pare Git ג€” Structured git operations (status, log, diff, branch, commit, push) as typed JSON. This page covers its npm package (@paretools/git).

Is the io.github.Dave-London/pare-git MCP server safe to use?

io.github.Dave-London/pare-git scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.Dave-London/pare-git MCP server expose?

io.github.Dave-London/pare-git exposes 20 tools: status, log, diff, branch, show, and 15 more. Their descriptions and schemas cost roughly 1,910 tokens of context every time the server is loaded.

Is the io.github.Dave-London/pare-git MCP server still maintained?

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

io.github.Dave-London/pare-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.