RegistryCompare › Chrome DevTools MCP vs MCP Apps

Chrome DevTools MCP vs MCP Apps

An independent, evidence-based trust comparison of Chrome DevTools MCP and MCP Apps, 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 Apps leads on trust — 73.4/100 (Grade B) vs 70.9/100 (Grade B), a 2.5-point gap. Full breakdown below.
Signal Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp MCP Appsmodelcontextprotocol/ext-apps
HVTrust score 70.9 73.4
Evidence grade B B
Coverage grade C B
Overall rank #99 #87
Rank in Protocols & Tool Integration #8 #7
GitHub stars 48.5k 2.7k
Last updated today 12d ago
Build provenance No Yes
OSSF Scorecard 7.7 / 10
License Apache-2.0 NOASSERTION
Downloads 1.6M/wk
Trust dimensions (points earned)
Safety / integrity / 25 14.6 12.5
Identity & provenance / 18 10.8 18.0
Transparency / 17 15.0 8.5
Maintenance / 20 19.7 13.2
Adoption / 20 11.2 16.5
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 2 — Google Gemini, OpenAI
Requires API keys No No
Plugin surface marketplace marketplace
Provenance drift Match
Open in the live compare tool → Chrome DevTools MCP profile MCP Apps 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 →