Chrome DevTools MCP vs MCP Inspector
An independent, evidence-based trust comparison of Chrome DevTools MCP and MCP Inspector, 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.0/100 (Grade A) vs 73.0/100 (Grade B), a 17.0-point gap. Full breakdown below.
| Signal | Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp | MCP Inspectormodelcontextprotocol/inspector |
|---|---|---|
| HVTrust score | 73.0 | 90.0 |
| Evidence grade | B | A |
| Coverage grade | C | B |
| Overall rank | #103 | #12 |
| Rank in Protocols & Tool Integration | #8 | #1 |
| GitHub stars | 48.7k | 10.6k |
| Last updated | 1d ago | 1d ago |
| Build provenance | No | Yes |
| OSSF Scorecard | 8.0 / 10 | 6.2 / 10 |
| License | Apache-2.0 | NOASSERTION |
| Downloads | — | 185k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 15.0 | 18.8 |
| Identity & provenance / 18 | 10.8 | 18.0 |
| Transparency / 17 | 15.3 | 13.8 |
| Maintenance / 20 | 19.7 | 19.9 |
| Adoption / 20 | 11.3 | 16.7 |
| 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 Inspector 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 →