RegistryCompare › Chrome DevTools MCP vs MCP Python SDK

Chrome DevTools MCP vs MCP Python SDK

An independent, evidence-based trust comparison of Chrome DevTools MCP and MCP Python SDK, 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 68.7/100 (Grade B), a 5.1-point gap. Full breakdown below.
Signal Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp MCP Python SDKmodelcontextprotocol/python-sdk
HVTrust score 73.8 68.7
Evidence grade B B
Coverage grade C C
Overall rank #249 #351
Rank in Protocols & Tool Integration #9 #14
GitHub stars 52.4k 24.4k
Last updated today 1d ago
Build provenance No No
OSSF Scorecard 8.3 / 10 7.1 / 10
License Apache-2.0 MIT
Downloads
Trust dimensions (points earned)
Safety / integrity / 25 15.4 13.9
Identity & provenance / 18 10.8 10.8
Transparency / 17 15.6 14.5
Maintenance / 20 19.8 17.6
Adoption / 20 11.3 10.5
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 2 — Anthropic, Google Gemini
Requires API keys No No
Plugin surface plugins extensions
Provenance drift
Open in the live compare tool → Chrome DevTools MCP profile MCP Python SDK 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 →