Registry › Compare › Composio vs mcp-proxy

Composio vs mcp-proxy

Both are Grade A and 1.8 points apart, so choose on what you weigh most. Composio leads on maintenance and adoption, and rests on broader evidence.

A Composio 89.5

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

composiohq/composio · #40 overall · #4 Protocols & Tool Integration · coverage A (4/5)

Choose Composio if maintenance and adoption matter most.

  • +2.4Adoption: 31.2k GitHub stars against 2.8k
  • +2.2Maintenance: last push today, against 6d ago
  • +1.1Safety / Integrity: 77% of recent commits signed, against 63%
  • A vs BEvidence coverage: 4 of 5 independent signal types, against 3
A mcp-proxy 87.7

A bridge between Streamable HTTP and stdio MCP transports

sparfenyuk/mcp-proxy · #64 overall · #8 Protocols & Tool Integration · coverage B (3/5)

mcp-proxy doesn't lead on any scored dimension in this pair.

Where they differ

20.1
Safety / IntegrityComposio +1.1
19.0
14.4
TransparencyComposio +0.2
14.2
20.0
MaintenanceComposio +2.2
17.8
17.3
AdoptionComposio +2.4
14.9
-0.3
Runtime calibrationmcp-proxy +4.1
+3.8

1 dimension identical: Identity 18.0 · Full evidence table

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.

Full evidence

Signal Composiocomposiohq/composio mcp-proxysparfenyuk/mcp-proxy
HVTrust score 89.5 87.7
Evidence grade A A
Coverage grade A B
Overall rank #40 #64
Rank in Protocols & Tool Integration #4 #8
GitHub stars 31.2k 2.8k
Last updated today 6d ago
Build provenance Yes Yes
OSSF Scorecard 7.0 / 10 6.7 / 10
License MIT MIT
Downloads 74k/wk 93k/wk
Trust dimensions (points earned)
Safety / integrity / 25 20.1 19.0
Identity & provenance / 18 18.0 18.0
Transparency / 17 14.4 14.2
Maintenance / 20 20.0 17.8
Adoption / 20 17.3 14.9
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.4 →