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.

git-a2a

NPM · GIT-A2A · 3 COMPONENTS · SCANNED AUG 23

Git module dependencies and owning-agent routing for coding agents

71 Trust /100
Trust breakdown (6 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 →

Supply Chain Security63
  • No malware found by supply-chain analysis.Pass
  • Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
  • No install/post-install scripts declared.Pass
  • Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
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 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 857 tokens (~71/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.

Install

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

# add to Claude Code
claude mcp add neprel-git-a2a -- npx -y git-a2a
// .cursor/mcp.json
{
  "mcpServers": {
    "neprel-git-a2a": {
      "command": "npx",
      "args": [
        "-y",
        "git-a2a"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "neprel-git-a2a": {
      "command": "npx",
      "args": [
        "-y",
        "git-a2a"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add neprel-git-a2a -- npx -y git-a2a
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "neprel-git-a2a": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "git-a2a"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add neprel-git-a2a --command npx --arg -y --arg git-a2a
# ~/.hermes/config.yaml
mcp_servers:
  neprel-git-a2a:
    command: "npx"
    args: ["-y", "git-a2a"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "neprel-git-a2a": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "git-a2a"
      ]
    }
  }
}
# add to Vellum
assistant mcp add neprel-git-a2a -t stdio -c npx -a -y git-a2a
// mcp.json
{
  "mcpServers": {
    "neprel-git-a2a": {
      "command": "npx",
      "args": [
        "-y",
        "git-a2a"
      ]
    }
  }
}
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.

  • 23 Aug 26 71

    First indexed and scored.

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 23 Aug 2026 · Analysed npm/git-a2a@1.2.0

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.2.0
Rekor log index 2575049001
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:a553cc64e183024df317e63f3950a8f73c754657f457a3e9e5f454330240f0bd623111e0626e6db99c91e0b9f6fa380120d2386554808515ee4407bef
MCP tools · 8 exposed · ~439 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.

Tool Tokens
doctor ~33

Report Git and ecosystem tool prerequisites without installing anything.

NameTypeReqDescription
rootstringrepository root; defaults to the server startup directory
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

explain ~33

Read the normative generated reference entry for one manifest field.

NameTypeReqDescription
pathstringyesmanifest field path such as agents.contacts.kind
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

fetch ~68

Restore disposable dependency cache content from exact lock coordinates.

NameTypeReqDescription
idsnull|arraydependency ids; omit for all locked dependencies
rootstringrepository root; defaults to the server startup directory
surfacebooleanalso restore the owner-published surface recorded in the lock
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

show ~66

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

NameTypeReqDescription
idstringmodule dependency id; omit for this module
rootstringrepository root; defaults to the server startup directory
surfacebooleanfetch and list the owner-published surface
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

status ~76

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

NameTypeReqDescription
idsnull|arraydependency ids; omit for all
offlinebooleando not contact remotes or card URLs
rootstringrepository root; defaults to the server startup directory
verbosebooleaninclude detailed findings
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

usage ~32

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

NameTypeReqDescription
promptbooleaninclude the full fresh-agent briefing
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

validate ~55

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

NameTypeReqDescription
filesnull|arraymanifest or lock paths; omit for current module files
rootstringrepository root; defaults to the server startup directory
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

who ~76

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

NameTypeReqDescription
idstringmodule dependency id; omit for this module
intentstringrouting intent; defaults to question
pathstringoptional repository path for scope matching
rootstringrepository root; defaults to the server startup directory
NameTypeReqDescription
datastructured command result for read tools
diagnosticsnull|arrayordered stderr verdict and advisory lines
exitCodeintegeryesgit-a2a exit code: 0 success, 1 failure or drift, 2 invalid or unresolved input
recordsnull|arrayordered stdout records for write tools

No examples provided.

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 npm package (git-a2a).

Is the git-a2a MCP server safe to use?

git-a2a scores 71 out of 100 on VerifyMCP. 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 439 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 23 August 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.