git-a2a
NPM · GIT-A2A · 3 COMPONENTS
Git module dependencies and owning-agent routing for coding agents
Available components
Last scanned (22 hours ago)
Scores higher than 97% of npm 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 Security100
- 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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to neprel/git-a2a). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 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 Management80
- Stability observed for 24 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
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −4
- Stability: pass → 0.77 functional
- 14 Oct 26 +1
- Stability: 0.97 → pass security
- 12 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 11 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 4 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.
- 2 Oct 26 −3
- Stability: pass → 0.80 functional
- 1 Oct 26 +1
- Stability: 0.97 → pass security
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 npm/git-a2a@1.7.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 | neprel/git-a2a |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/neprel/git-a2a/.github/workflows/release.yml@refs/tags/v1.7.1 |
| Rekor log index | 2583238478 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7951156bb9fbc7afcee6df3a3b4c130cc5d8f877953b39bb40cf8237b5132f799d5265a90715858c7b49e92604d6002c7cf0a05e84324b56236756812 |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 an npm package, launched with npx -y git-a2a. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · git-a2a
claude mcp add neprel-git-a2a -- npx -y git-a2a
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 npm package (git-a2a).
Is the git-a2a MCP server safe to use?
git-a2a scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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 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.
What licence is the git-a2a MCP server under?
git-a2a declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.