# GitFerry (npm · gitferry)

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

- Trust score: 89/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `gitferry`: 89/100 (this document), [markdown](https://verifymcp.io/servers/mayank1307-gitferry/gitferry.md), [page](https://verifymcp.io/servers/mayank1307-gitferry/gitferry)

## Channel facts

- Registry: `npm`
- Package: `gitferry`
- Version: `0.4.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 43 of 124 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to mayank1307/gitferry).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 18 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add mayank1307-gitferry -- npx -y gitferry mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mayank1307-gitferry": {
      "command": "npx",
      "args": [
        "-y",
        "gitferry",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mayank1307-gitferry": {
      "command": "npx",
      "args": [
        "-y",
        "gitferry",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mayank1307-gitferry -- npx -y gitferry mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mayank1307-gitferry": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "gitferry",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mayank1307-gitferry --command npx --arg -y --arg gitferry --arg mcp
```

### Hermes

```yaml
mcp_servers:
  mayank1307-gitferry:
    command: "npx"
    args: ["-y", "gitferry", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mayank1307-gitferry": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "gitferry",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mayank1307-gitferry -t stdio -c npx -a -y gitferry mcp
```

### Other

```json
{
  "mcpServers": {
    "mayank1307-gitferry": {
      "command": "npx",
      "args": [
        "-y",
        "gitferry",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 89, +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.

### 2026-11-19 (score 88, +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.

### 2026-11-17 (score 87, +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.

### 2026-11-15 (score 86, +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.

### 2026-11-13 (score 85, +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.

### 2026-11-11 (score 84, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-11-09 (score 80, +5)

- [security improvement] Source repository: unverified → pass

### 2026-11-08 (score 75, −5)

- [security regression] Provenance: pass → unverified

## MCP tools (3)

### `pack_changes` (~301 tokens)

Pack local Git changes

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.

Input parameters:

- `base` (string): Ref/sha the bundle applies onto (default: merge-base with the upstream tracking branch)
- `cwd` (string, required): Absolute path to the git repository (or any directory inside it)
- `includeCommits` (boolean): Include unpushed commits (default true)
- `includeStaged` (boolean): Include staged (index) changes (default true)
- `includeUnstaged` (boolean): Include unstaged working-tree changes (default true)
- `includeUntracked` (boolean): Include untracked files (default true)
- `includeWorktree` (boolean): Include staged AND unstaged changes; master switch over includeStaged/includeUnstaged (default true)
- `only` (string): Select all, uncommitted, staged, unstaged, committed, or repo (tracked-file snapshot). Default all. Include flags can further narrow the selection; repo is exclusive.
- `output` (string): Output bundle path; defaults to <repo>-<branch>-<sha>.gitferry in cwd
- `portable` (boolean): Write a plain ZIP for git + unzip targets instead of the smaller Brotli-wrapped format (default false)

### `inspect_bundle` (~62 tokens)

Inspect a local GitFerry bundle

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.

Input parameters:

- `bundlePath` (string, required): Absolute path to the .gitferry bundle file

Output parameters:

- `checksumsVerified` (boolean)
- `manifest` (object)

### `apply_bundle` (~159 tokens)

Apply a local GitFerry bundle

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.

Input parameters:

- `bundlePath` (string, required): Absolute path to the .gitferry bundle file
- `cwd` (string, required): Absolute path to the target git repository
- `dryRun` (boolean): Validate and report the plan without changing anything (default false)
- `force` (boolean): Override repo-fingerprint, dirty-tree, and file-overwrite guards (default false)
- `includeUntracked` (boolean): Write untracked files from the bundle (default true)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mayank1307-gitferry/gitferry#diagnostics

## Score history

- 2026-11-21: 89
- 2026-11-20: 88
- 2026-11-19: 88
- 2026-11-18: 87
- 2026-11-17: 87
- 2026-11-16: 86
- 2026-11-15: 86
- 2026-11-14: 85
- 2026-11-13: 85
- 2026-11-12: 84
- 2026-11-11: 84
- 2026-11-10: 80
- 2026-11-09: 80
- 2026-11-08: 75
- 2026-11-07: 80
- 2026-11-06: 80
- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 70

## 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.

## Links

- npm package: https://www.npmjs.com/package/gitferry
- Socket report: https://socket.dev/npm/package/gitferry
- Repository: https://github.com/mayank1307/gitferry
- Changelog RSS feed: https://verifymcp.io/servers/mayank1307-gitferry/gitferry.xml
- Changelog JSON feed: https://verifymcp.io/servers/mayank1307-gitferry/gitferry/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mayank1307-gitferry/gitferry.json
- HTML version of this page: https://verifymcp.io/servers/mayank1307-gitferry/gitferry
