Is Chrome DevTools MCP safe to use?

Chrome DevTools MCP has an HVTrust score of 71.9/100 (Grade B), ranked #95 of 468 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Chrome DevTools MCP?

Chrome DevTools MCP scores 71.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 48.6k GitHub stars and is categorized under Protocols & Tool Integration.

Chrome DevTools MCP

ChromeDevTools/chrome-devtools-mcp

Chrome DevTools for coding agents

Protocols & Tool Integration TypeScript Grade B Listed Apache-2.0

71.9/100

Rank #95 of 468

Compare Chrome DevTools MCP

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-05 · 1d ago

Recent change

No recent signal change

Is Chrome DevTools MCP safe? Chrome DevTools MCP scores 71.9/100 (Grade B), ranked #95 of 468 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 8.2/10; 100% of recent commits are signed; last pushed 2026-08-05. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#6 Composio — 75.0 (B) → #7 MCP Apps — 73.3 (B) → #9 MCP Python SDK — 68.1 (B) → #10 MCP Specification — 68.0 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with MCP Inspector Get email alerts for Chrome DevTools MCP View Protocols & Tool Integration Report missing data

93.4

Activity sub-score · out of 100

In 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. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars

48.6k

Forks

3.4k

Last Push

2026-08-05

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #95

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

71.9 / 100 · 100.0% confidence

Chrome DevTools MCP Protocols & Tool Integration average (35 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

15.2 / 25

3.7 above avg 11.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

1.2 below avg 12.0

Transparency50% declared license · 50% OSSF Scorecard

15.5 / 17

2.7 above avg 12.8

Maintenance60% last-push freshness · 40% commit activity

19.6 / 20

4.3 above avg 15.3

AdoptionLog-scaled stars · package downloads

11.2 / 20

in line with avg 11.3

Activity Inputs

93.4 / 100

StarsRepository reach

28.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

23.9 / 25

CommunityFork signal

16.4 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

8.2 / 10

OpenSSF Scorecard · scanned Aug 6, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 7

SAST 7

Security-Policy 10

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 6

Is Chrome DevTools MCP safe?

Chrome DevTools MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Chrome DevTools MCP publish package provenance?

No published build provenance is currently detected for Chrome DevTools MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Chrome DevTools MCP have an OpenSSF Scorecard?

Chrome DevTools MCP has an OpenSSF Scorecard score of 8.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Chrome DevTools MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Chrome DevTools MCP use?

Chrome DevTools MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Chrome DevTools MCP's commits signed?

100% of the last 100 commits to Chrome DevTools MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Chrome DevTools MCP head-to-head

Chrome DevTools MCP vs MCP Inspector → Chrome DevTools MCP vs A2A / Agent2Agent Protocol → Chrome DevTools MCP vs FastMCP (TypeScript) →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Chrome DevTools MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Marketplace

Marketplace plugin/integration surface detected.

browser
code
search

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Chrome DevTools MCP?

For maintainers

HVTrust scores Chrome DevTools MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-06-22

Scorecard Added

OSSF Scorecard: 8.1/10

2026-06-22

Grade Changed

Trust grade D → B

2026-06-22

Rank Moved

Rank rose 172 spots (#246 → #74)

2026-06-22

HVTrust Changed

HVTrust up 43.9pts (26.9 → 70.8)

2026-06-21

Rank Moved

Rank dropped 19 spots (#227 → #246)

2026-06-20

Newly Listed

First tracked at rank #227

2026-05-25

Removed From Active Tracking

Removed from active tracking

2026-05-24

Newly Listed

First tracked at rank #24

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/chrome-devtools-mcp.svg)](https://hvtracker.net/agents/chrome-devtools-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/chrome-devtools-mcp"><img src="https://hvtracker.net/badge/chrome-devtools-mcp.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON