RegistryCompare › MCP Inspector vs mcp-proxy

MCP Inspector vs mcp-proxy

An independent, evidence-based trust comparison of MCP Inspector 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 Inspector leads on trust — 90.4/100 (Grade A) vs 81.1/100 (Grade A), a 9.3-point gap. Full breakdown below.
Signal MCP Inspectormodelcontextprotocol/inspector mcp-proxysparfenyuk/mcp-proxy
HVTrust score 90.4 81.1
Evidence grade A A
Coverage grade B B
Overall rank #9 #58
Rank in Protocols & Tool Integration #1 #4
GitHub stars 10.6k 2.7k
Last updated 1d ago 15d ago
Build provenance Yes Yes
OSSF Scorecard 6.2 / 10 5.8 / 10
License NOASSERTION MIT
Downloads 185k/wk 292k/wk
Trust dimensions (points earned)
Safety / integrity / 25 18.8 17.2
Identity & provenance / 18 18.0 18.0
Transparency / 17 13.8 13.4
Maintenance / 20 19.9 11.0
Adoption / 20 16.7 15.5
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers
Requires API keys No No
Plugin surface plugins
Provenance drift Match Match
Open in the live compare tool → MCP Inspector 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 →