git-a2a
OCI · GHCR.IO/NEPREL/GIT-A2A:1.7.1 · 3 COMPONENTS
Git module dependencies and owning-agent routing for coding agents
Available components
Last scanned (19 hours ago)
Scores higher than 74% of OCI servers
Category Version Control
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 Security0
- 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.Unverified
- 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.Unverified
- Install-script risk not yet assessed.Unverified
- 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.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 51 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 958 tokens (~79/item across 12 items; 8 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 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 (100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
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.
- 15 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +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.
- 9 Oct 26 +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.
- 6 Oct 26 +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.
- 4 Oct 26 +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.
- 3 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 16 Oct 2026 · Analysed oci/ghcr.io/neprel/git-a2a:1.7.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
doctor ~42
Report Git and ecosystem tool prerequisites without installing anything.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | – | repository root; must be inside an allowed root (startup dir, --roots, client roots) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
explain ~33
Read the normative generated reference entry for one manifest field.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | manifest field path such as agents.contacts.kind |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
fetch ~77
Restore disposable dependency cache content from exact lock coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
show ~75
Read this module or a locked dependency and optionally its published surface.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
status ~85
Check dependency, wiring, card, trust, and roster health.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
usage ~32
Read the compact or full deterministic briefing for a coding agent.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | boolean | – | include the full fresh-agent briefing |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
validate ~64
Validate manifest and lock files against the git-a2a standard.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
who ~85
Resolve an intent to the owning agents and their declared contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | structured command result for read tools |
| diagnostics | null|array | – | ordered stderr verdict and advisory lines |
| exitCode | integer | yes | git-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input |
| records | null|array | – | ordered stdout records for write tools |
No examples provided.
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.
oci · ghcr.io/neprel/git-a2a:1.7.1
claude mcp add neprel-git-a2a -- docker run --rm -i ghcr.io/neprel/git-a2a:1.7.1
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.