RegistryCompare › Chrome DevTools MCP vs ToolHive

Chrome DevTools MCP vs ToolHive

An independent, evidence-based trust comparison of Chrome DevTools MCP and ToolHive, 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.

Chrome DevTools MCP leads on trust — 73.8/100 (Grade B) vs 71.5/100 (Grade B), a 2.3-point gap. Full breakdown below.
Signal Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp ToolHivestacklok/toolhive
HVTrust score 73.8 71.5
Evidence grade B B
Coverage grade C C
Overall rank #245 #293
Rank in Protocols & Tool Integration #11 #12
GitHub stars 51.8k 2.2k
Last updated today 2d ago
Build provenance No No
OSSF Scorecard 8.3 / 10 8.4 / 10
License Apache-2.0 Apache-2.0
Downloads
Trust dimensions (points earned)
Safety / integrity / 25 15.4 15.5
Identity & provenance / 18 10.8 10.8
Transparency / 17 15.6 15.6
Maintenance / 20 19.8 19.9
Adoption / 20 11.3 8.0
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 2 — Anthropic, Google Gemini
Requires API keys No No
Plugin surface plugins plugins
Provenance drift
Open in the live compare tool → Chrome DevTools MCP profile ToolHive 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 →