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 — 81.1/100 (Grade A) vs 75.7/100 (Grade B), a 5.4-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 | 75.7 | 81.1 |
| Evidence grade | B | A |
| Coverage grade | A | B |
| Overall rank | #75 | #58 |
| Rank in Protocols & Tool Integration | #6 | #4 |
| GitHub stars | 29.5k | 2.7k |
| Last updated | today | 15d ago |
| Build provenance | No | Yes |
| OSSF Scorecard | 6.9 / 10 | 5.8 / 10 |
| License | MIT | MIT |
| Downloads | 103k/wk | 292k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 13.0 | 17.2 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 14.4 | 13.4 |
| Maintenance / 20 | 20.0 | 11.0 |
| Adoption / 20 | 17.4 | 15.5 |
| Runtime capability surface (full matrix) | ||
| MCP server | Declared | Implemented |
| External providers | 3 — Anthropic, Google Gemini, OpenAI | — |
| Requires API keys | No | No |
| 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.2 →