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 — 76.0/100 (Grade B) vs 74.6/100 (Grade B), a 1.4-point gap. Full breakdown below.
Signal Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp Composiocomposiohq/composio
HVTrust score 74.6 76.0
Evidence grade B B
Coverage grade C A
Overall rank #97 #85
Rank in Protocols & Tool Integration #8 #7
GitHub stars 49.2k 29.7k
Last updated today today
Build provenance No No
OSSF Scorecard 8.6 / 10 6.8 / 10
License Apache-2.0 MIT
Downloads 103k/wk
Trust dimensions (points earned)
Safety / integrity / 25 15.8 12.8
Identity & provenance / 18 10.8 10.8
Transparency / 17 15.8 14.3
Maintenance / 20 20.0 20.0
Adoption / 20 11.3 17.4
Runtime capability surface (full matrix)
MCP server Implemented Declared
External providers 2 — Anthropic, Google Gemini 1 — OpenAI
Requires API keys No Yes
Plugin surface plugins 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.3 →