RegistryCompare › A2A / Agent2Agent Protocol vs mcp-proxy

A2A / Agent2Agent Protocol vs mcp-proxy

An independent, evidence-based trust comparison of A2A / Agent2Agent Protocol and mcp-proxy, two Protocols & Tool Integration projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

A2A / Agent2Agent Protocol leads on trust — 89.0/100 (Grade A) vs 75.6/100 (Grade B), a 13.4-point gap. Full breakdown below.
Signal A2A / Agent2Agent Protocolgoogle/A2A mcp-proxysparfenyuk/mcp-proxy
HVTrust score 89.0 75.6
Evidence grade A B
Coverage grade A B
Overall rank #27 #214
Rank in Protocols & Tool Integration #1 #8
GitHub stars 25.8k 2.8k
Last updated 3d ago 61d ago
Build provenance Yes Yes
OSSF Scorecard 7.1 / 10 5.2 / 10
License Apache-2.0 MIT
Downloads 2.4M/wk 207k/wk
Trust dimensions (points earned)
Safety / integrity / 25 21.3 16.5
Identity & provenance / 18 18.0 18.0
Transparency / 17 14.5 12.9
Maintenance / 20 16.7 7.9
Adoption / 20 19.1 15.3
Runtime capability surface (full matrix)
MCP server Implemented
External providers
Requires API keys No Yes
Plugin surface extensions
Provenance drift Unknown Match
Open in the live compare tool → A2A / Agent2Agent Protocol profile mcp-proxy profile More Protocols & Tool Integration →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →