Registry › Compare › Chrome DevTools MCP vs Composio

Chrome DevTools MCP vs Composio

Composio leads on trust: 89.3/100 (Grade A) against 74.0/100 (Grade B), a 15.3-point gap. Chrome DevTools MCP leads on transparency; Composio leads on provenance and adoption, and rests on broader evidence.

B Chrome DevTools MCP 74.0

Chrome DevTools for coding agents

ChromeDevTools/chrome-devtools-mcp · #283 overall · #13 Protocols & Tool Integration · coverage C (2/5)

Choose Chrome DevTools MCP if transparency matters most.

+1.0Transparency: OSSF Scorecard 8.3 against 7.2

A Composio 89.3

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

composiohq/composio · #34 overall · #5 Protocols & Tool Integration · coverage A (4/5)

Choose Composio if provenance and adoption matter most.

+7.2Identity / Provenance: package provenance attested, against none
+5.7Adoption
+4.6Safety / Integrity: package provenance attested, against none
A vs CEvidence coverage: 4 of 5 independent signal types, against 2

Where they differ

15.4

Safety / IntegrityComposio +4.6

20.0

10.8

Identity / ProvenanceComposio +7.2

18.0

15.6

TransparencyChrome DevTools MCP +1.0

14.6

11.4

AdoptionComposio +5.7

17.1

+0.9

Runtime calibrationChrome DevTools MCP +1.2

-0.3

1 dimension identical: Maintenance 19.9 · Full evidence table

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.

Full evidence

Signal	Chrome DevTools MCPChromeDevTools/chrome-devtools-mcp	Composiocomposiohq/composio
HVTrust score	74.0	89.3
Evidence grade	B	A
Coverage grade	C	A
Overall rank	#283	#34
Rank in Protocols & Tool Integration	#13	#5
GitHub stars	54.7k	30.9k
Last updated	1d ago	1d ago
Build provenance	No	Yes
OSSF Scorecard	8.3 / 10	7.2 / 10
License	Apache-2.0	MIT
Downloads	—	56k/wk
Trust dimensions (points earned)
Safety / integrity / 25	15.4	20.0
Identity & provenance / 18	10.8	18.0
Transparency / 17	15.6	14.6
Maintenance / 20	19.9	19.9
Adoption / 20	11.4	17.1
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.4 →