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.

GitFerry

NPM · GITFERRY

Pack, inspect, and apply portable Git change bundles across offline repositories.

Available components

+4 this week 89 Trust /100

Last scanned (15 hours ago)

Scores higher than 83% 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
  • 43 of 124 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 mayank1307/gitferry). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 18 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 522 tokens (~174/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 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
  • Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +4
    • Stability: unverified → 0.27 ▲ functional
  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ 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 21 Nov 2026 · Analysed npm/gitferry@0.4.2

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 mayank1307/gitferry
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/mayank1307/gitferry/.github/workflows/release.yml@refs/tags/v0.4.2
Rekor log index 3662359972
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6a5d3ecb52084b651d309cf6c8ee0bdaf2b7e5f7ca2e658300e5fedbc80c232c4c94290d48598239c875aaa264e9aeae79c12543d562d41ebc8cde0dd

Background: How many MCP packages publish verified provenance →

Dependencies 124 packages
Packages resolved 124
Stale 43
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~522 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
apply_bundle ~159

Validate and apply a trusted local .gitferry bundle: replay commits, restore staged/unstaged changes, and write untracked or snapshot files. Modifies the target unless dryRun=true. Preview first and review conflicts afterward. force bypasses repository, dirty-tree, and overwrite guards.

NameTypeReqDescription
bundlePathstringyesAbsolute path to the .gitferry bundle file
cwdstringyesAbsolute path to the target git repository
dryRunboolean–Validate and report the plan without changing anything (default false)
forceboolean–Override repo-fingerprint, dirty-tree, and file-overwrite guards (default false)
includeUntrackedboolean–Write untracked files from the bundle (default true)

No output schema declared.

No examples provided.

inspect_bundle ~62

Read a local .gitferry bundle, verify checksums and manifest structure, and report its contents without modifying files. Checksums detect corruption; they do not authenticate the sender.

NameTypeReqDescription
bundlePathstringyesAbsolute path to the .gitferry bundle file
NameTypeReqDescription
checksumsVerifiedbooleanyes–
manifestobjectyes–

No examples provided.

pack_changes ~301

Read a local Git repository and write a portable .gitferry bundle of commits, staged/unstaged changes, and untracked files. only=repo instead captures tracked files as a snapshot. Review untracked files for secrets before sharing. No network transfer is performed.

NameTypeReqDescription
basestring–Ref/sha the bundle applies onto (default: merge-base with the upstream tracking branch)
cwdstringyesAbsolute path to the git repository (or any directory inside it)
includeCommitsboolean–Include unpushed commits (default true)
includeStagedboolean–Include staged (index) changes (default true)
includeUnstagedboolean–Include unstaged working-tree changes (default true)
includeUntrackedboolean–Include untracked files (default true)
includeWorktreeboolean–Include staged AND unstaged changes; master switch over includeStaged/includeUnstaged (default true)
onlystring–Select all, uncommitted, staged, unstaged, committed, or repo (tracked-file snapshot). Default all. Include flags can further narrow the selection; repo is exclusive.
outputstring–Output bundle path; defaults to <repo>-<branch>-<sha>.gitferry in cwd
portableboolean–Write a plain ZIP for git + unzip targets instead of the smaller Brotli-wrapped format (default false)

No output schema declared.

No examples provided.

Install

How do I install the GitFerry MCP server?

GitFerry runs locally as an npm package, launched with npx -y gitferry 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 · gitferry

# add to Claude Code
claude mcp add mayank1307-gitferry -- npx -y gitferry mcp
Common questions

What is the GitFerry MCP server?

GitFerry is an MCP server listed in the public MCP registry as io.github.mayank1307/gitferry. Pack, inspect, and apply portable Git change bundles across offline repositories. This page covers its npm package (gitferry).

Is the GitFerry MCP server safe to use?

GitFerry scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 GitFerry MCP server expose?

GitFerry exposes 3 tools: pack_changes, inspect_bundle, apply_bundle. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.

Is the GitFerry MCP server still maintained?

GitFerry is still listed as active in the MCP registry. We last reached this channel on 21 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 GitFerry MCP server under?

GitFerry 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 GitFerry MCP server?

VerifyMCP ran 16 checks on GitFerry, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.