RegistryCompare › Chrome DevTools MCP vs Composio

Chrome DevTools MCP vs Composio

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

Composio leads on trust — 75.7/100 (Grade B) vs 70.9/100 (Grade B), a 4.8-point gap. Full breakdown below.
Signal Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp Composiocomposiohq/composio
HVTrust score 70.9 75.7
Evidence grade B B
Coverage grade C A
Overall rank #99 #75
Rank in Protocols & Tool Integration #8 #6
GitHub stars 48.5k 29.5k
Last updated today today
Build provenance No No
OSSF Scorecard 7.7 / 10 6.9 / 10
License Apache-2.0 MIT
Downloads 103k/wk
Trust dimensions (points earned)
Safety / integrity / 25 14.6 13.0
Identity & provenance / 18 10.8 10.8
Transparency / 17 15.0 14.4
Maintenance / 20 19.7 20.0
Adoption / 20 11.2 17.4
Runtime capability surface (full matrix)
MCP server Implemented Declared
External providers 2 — Google Gemini, OpenAI 3 — Anthropic, Google Gemini, OpenAI
Requires API keys No No
Plugin surface marketplace plugins
Provenance drift Partial
Open in the live compare tool → Chrome DevTools MCP profile Composio 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 →