# git-a2a (oci · ghcr.io/neprel/git-a2a:1.7.1)

Git module dependencies and owning-agent routing for coding agents

- Trust score: 49/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- mcpb · `git-a2a_1.7.1.mcpb`: 17/100, [markdown](https://verifymcp.io/servers/neprel-git-a2a/https-github-com-neprel-git-a2a-releases-download-v1-7-1-git-a2a-1-7-1-mcpb.md), [page](https://verifymcp.io/servers/neprel-git-a2a/https-github-com-neprel-git-a2a-releases-download-v1-7-1-git-a2a-1-7-1-mcpb)
- npm · `git-a2a`: 97/100, [markdown](https://verifymcp.io/servers/neprel-git-a2a/git-a2a.md), [page](https://verifymcp.io/servers/neprel-git-a2a/git-a2a)
- oci · `ghcr.io/neprel/git-a2a:1.7.1`: 49/100 (this document), [markdown](https://verifymcp.io/servers/neprel-git-a2a/ghcr-io-neprel-git-a2a-1-7-1.md), [page](https://verifymcp.io/servers/neprel-git-a2a/ghcr-io-neprel-git-a2a-1-7-1)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/neprel/git-a2a:1.7.1`
- 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-10-16.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 51 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 958 tokens (~79/item across 12 items; 8 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 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 (100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the git-a2a MCP server?

git-a2a runs locally as a container image, launched with docker run --rm -i ghcr.io/neprel/git-a2a:1.7.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add neprel-git-a2a -- docker run --rm -i ghcr.io/neprel/git-a2a:1.7.1
```

### Cursor

```json
{
  "mcpServers": {
    "neprel-git-a2a": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/neprel/git-a2a:1.7.1"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "neprel-git-a2a": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/neprel/git-a2a:1.7.1"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add neprel-git-a2a -- docker run --rm -i ghcr.io/neprel/git-a2a:1.7.1
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neprel-git-a2a": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/neprel/git-a2a:1.7.1"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  neprel-git-a2a:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/neprel/git-a2a:1.7.1"]
```

### Netclaw

```json
{
  "McpServers": {
    "neprel-git-a2a": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/neprel/git-a2a:1.7.1"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "neprel-git-a2a": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/neprel/git-a2a:1.7.1"
      ]
    }
  }
}
```

## 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-10-15 (score 49, +1)

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

### 2026-10-12 (score 48, +1)

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

### 2026-10-10 (score 47, +1)

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

### 2026-10-09 (score 46, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 47. That category is still filling its 30-day observation window: 11 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-10-06 (score 45, +1)

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

### 2026-10-04 (score 44, +1)

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

### 2026-10-03 (score 43, +3)

- [functional improvement] Stability: unverified → 0.27

### 2026-09-28 (score 40, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (8)

### `doctor` (~42 tokens)

Report Git and ecosystem tool prerequisites without installing anything.

Input parameters:

- `root` (string): repository root; must be inside an allowed root (startup dir, --roots, client roots)

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `explain` (~33 tokens)

Read the normative generated reference entry for one manifest field.

Input parameters:

- `path` (string, required): manifest field path such as agents.contacts.kind

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `fetch` (~77 tokens)

Restore disposable dependency cache content from exact lock coordinates.

Input parameters:

- `ids` (null|array): dependency ids; omit for all locked dependencies
- `root` (string): repository root; must be inside an allowed root (startup dir, --roots, client roots)
- `surface` (boolean): also restore the owner-published surface recorded in the lock

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `show` (~75 tokens)

Read this module or a locked dependency and optionally its published surface.

Input parameters:

- `id` (string): module dependency id; omit for this module
- `root` (string): repository root; must be inside an allowed root (startup dir, --roots, client roots)
- `surface` (boolean): fetch and list the owner-published surface

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `status` (~85 tokens)

Check dependency, wiring, card, trust, and roster health.

Input parameters:

- `ids` (null|array): dependency ids; omit for all
- `offline` (boolean): do not contact remotes or card URLs
- `root` (string): repository root; must be inside an allowed root (startup dir, --roots, client roots)
- `verbose` (boolean): include detailed findings

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `usage` (~32 tokens)

Read the compact or full deterministic briefing for a coding agent.

Input parameters:

- `prompt` (boolean): include the full fresh-agent briefing

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `validate` (~64 tokens)

Validate manifest and lock files against the git-a2a standard.

Input parameters:

- `files` (null|array): manifest or lock paths; omit for current module files
- `root` (string): repository root; must be inside an allowed root (startup dir, --roots, client roots)

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

### `who` (~85 tokens)

Resolve an intent to the owning agents and their declared contacts.

Input parameters:

- `id` (string): module dependency id; omit for this module
- `intent` (string): routing intent; defaults to question
- `path` (string): optional repository path for scope matching
- `root` (string): repository root; must be inside an allowed root (startup dir, --roots, client roots)

Output parameters:

- `data`: structured command result for read tools
- `diagnostics` (null|array): ordered stderr verdict and advisory lines
- `exitCode` (integer): git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
- `records` (null|array): ordered stdout records for write tools

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/neprel-git-a2a/ghcr-io-neprel-git-a2a-1-7-1#diagnostics

## Score history

- 2026-10-16: 49
- 2026-10-15: 49
- 2026-10-14: 48
- 2026-10-13: 48
- 2026-10-12: 48
- 2026-10-10: 47
- 2026-10-09: 46
- 2026-10-06: 45
- 2026-10-04: 44
- 2026-10-03: 43
- 2026-10-02: 40
- 2026-10-01: 40
- 2026-09-30: 40
- 2026-09-29: 40
- 2026-09-28: 40
- 2026-09-27: 40
- 2026-09-26: 40
- 2026-09-25: 40
- 2026-09-24: 6
- 2026-09-23: 6
- 2026-09-22: 6
- 2026-09-21: 6
- 2026-09-20: 6
- 2026-09-19: 6
- 2026-09-18: 6
- 2026-09-17: 6
- 2026-09-16: 6
- 2026-09-15: 6
- 2026-09-14: 6
- 2026-09-13: 6

## Common questions

### What is the git-a2a MCP server?

git-a2a is an MCP server listed in the public MCP registry as io.github.neprel/git-a2a. Git module dependencies and owning-agent routing for coding agents. This page covers its container image (ghcr.io/neprel/git-a2a:1.7.1).

### Is the git-a2a MCP server safe to use?

git-a2a scores 49 out of 100 on VerifyMCP. 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 git-a2a MCP server expose?

git-a2a exposes 8 tools: doctor, explain, fetch, show, status, and 3 more. Their descriptions and schemas cost roughly 493 tokens of context every time the server is loaded.

### Is the git-a2a MCP server still maintained?

git-a2a is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- GitHub Container Registry: https://ghcr.io/neprel/git-a2a
- Repository: https://github.com/neprel/git-a2a
- Changelog RSS feed: https://verifymcp.io/servers/neprel-git-a2a/ghcr-io-neprel-git-a2a-1-7-1.xml
- Changelog JSON feed: https://verifymcp.io/servers/neprel-git-a2a/ghcr-io-neprel-git-a2a-1-7-1.json
- HTML version of this page: https://verifymcp.io/servers/neprel-git-a2a/ghcr-io-neprel-git-a2a-1-7-1