RegistryCompare › Chrome DevTools MCP vs mcp-proxy

Chrome DevTools MCP vs mcp-proxy

An independent, evidence-based trust comparison of Chrome DevTools MCP 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.7/100 (Grade B) vs 73.8/100 (Grade B), a 1.9-point gap. Full breakdown below.
Signal Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp mcp-proxysparfenyuk/mcp-proxy
HVTrust score 73.8 75.7
Evidence grade B B
Coverage grade C B
Overall rank #249 #209
Rank in Protocols & Tool Integration #9 #7
GitHub stars 52.4k 2.8k
Last updated today 62d ago
Build provenance No Yes
OSSF Scorecard 8.3 / 10 5.2 / 10
License Apache-2.0 MIT
Downloads 211k/wk
Trust dimensions (points earned)
Safety / integrity / 25 15.4 16.5
Identity & provenance / 18 10.8 18.0
Transparency / 17 15.6 12.9
Maintenance / 20 19.8 7.9
Adoption / 20 11.3 15.4
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 2 — Anthropic, Google Gemini
Requires API keys No Yes
Plugin surface plugins
Provenance drift Match
Open in the live compare tool → Chrome DevTools MCP 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 →