RegistryCompare › Composio vs mcp-proxy

Composio vs mcp-proxy

An independent, evidence-based trust comparison of Composio 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.

mcp-proxy leads on trust — 75.6/100 (Grade B) vs 74.4/100 (Grade B), a 1.2-point gap. Note: mcp-proxy's evidence coverage is thinner (coverage B vs A) — its score rests on fewer independent signal types. Full breakdown below.
Signal Composiocomposiohq/composio mcp-proxysparfenyuk/mcp-proxy
HVTrust score 74.4 75.6
Evidence grade B B
Coverage grade A B
Overall rank #236 #211
Rank in Protocols & Tool Integration #8 #7
GitHub stars 30.3k 2.8k
Last updated 3d ago 63d ago
Build provenance No Yes
OSSF Scorecard 7.5 / 10 5.2 / 10
License MIT MIT
Downloads 42k/wk 211k/wk
Trust dimensions (points earned)
Safety / integrity / 25 11.3 16.5
Identity & provenance / 18 10.8 18.0
Transparency / 17 14.9 12.9
Maintenance / 20 19.8 7.8
Adoption / 20 16.9 15.4
Runtime capability surface (full matrix)
MCP server Declared Implemented
External providers 1 — OpenAI
Requires API keys Yes Yes
Plugin surface plugins
Provenance drift Partial Match
Open in the live compare tool → Composio 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 →