mcp-proxy vs MCP Python SDK
An independent, evidence-based trust comparison of mcp-proxy and MCP Python SDK, 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 — 77.1/100 (Grade B) vs 68.8/100 (Grade B), a 8.3-point gap. Full breakdown below.
| Signal | mcp-proxysparfenyuk/mcp-proxy | MCP Python SDKmodelcontextprotocol/python-sdk |
|---|---|---|
| HVTrust score | 77.1 | 68.8 |
| Evidence grade | B | B |
| Coverage grade | B | C |
| Overall rank | #119 | #219 |
| Rank in Protocols & Tool Integration | #5 | #8 |
| GitHub stars | 2.7k | 24.2k |
| Last updated | 45d ago | 1d ago |
| Build provenance | Yes | No |
| OSSF Scorecard | 5.2 / 10 | 7.1 / 10 |
| License | MIT | MIT |
| Downloads | 406k/wk | — |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 16.5 | 13.9 |
| Identity & provenance / 18 | 18.0 | 10.8 |
| Transparency / 17 | 12.9 | 14.5 |
| Maintenance / 20 | 9.0 | 17.7 |
| Adoption / 20 | 15.7 | 10.5 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | — | — |
| Requires API keys | Yes | No |
| Plugin surface | — | extensions |
| Provenance drift | Match | — |
Open in the live compare tool →
mcp-proxy profile
MCP Python SDK 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 →