updated 2026-11-05 12:09 UTC

Chrome DevTools MCP

Repository Website

Chrome DevTools for coding agents

Protocols & Tool Integration TypeScript Listed Apache-2.0

Is Chrome DevTools MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 8.3 / 10
Provenance None
Signed commits 100%
Last push today
Compare Chrome DevTools MCP

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

Pick any agent to compare →
Suggest a correction

In detail: Chrome DevTools MCP scores 74.1/100 (Grade B), ranked #284 of 1374 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.3/10; 100% of recent commits are signed; last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Chrome DevTools MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Chrome DevTools MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/ChromeDevTools/chrome-devtools-mcp, Apache-2.0, last pushed 2026-11-05. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 8.3/10 (scanned Nov 1, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions9
    • Pinned Dependencies8
    All 18 Scorecard checks
    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 8
    SAST 7
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 9
    Vulnerabilities 7

  3. Published packages None

    No registry package. Chrome DevTools MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Chrome DevTools MCP.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Chrome DevTools MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Chrome DevTools MCP compares in Protocols & Tool Integration

  1. #11 Jevgrep 78.1 +4.0
  2. #12 CLI-Anything 74.2 +0.1
  3. #13 Chrome DevTools MCP 74.1 this agent
  4. #14 Pi MCP Adapter 73.8 −0.3
  5. #15 Treg 72.5 −1.6

Bars show each HVTrust score; the tick marks Chrome DevTools MCP’s 74.1.

Where the 74.1 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

74.1 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.4 / 25
4.3 above avg 11.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
15.6 / 17
2.6 above avg 13.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.5 above avg 14.5
AdoptionLog-scaled stars · package downloads
11.4 / 20
in line with avg 11.1

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 another agent
View Protocols & Tool Integration Report missing data
95.7
Activity sub-score · out of 100
#13
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 →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
54.8k
Forks
5.2k
Last Push
2026-11-05
today
Commits (4 wk)
237
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
84
Rank Change
▼6
was #278

Analysis

Activity Inputs

95.7 / 100
StarsRepository reach
28.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.3 / 20

Common questions about Chrome DevTools MCP

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.3/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.

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
Declared
Declared plugin/integration surface detected.
  • browser
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
Rank 6
2026-09-23
Rank Moved
Rank dropped 142 spots (#96 → #238)
2026-09-21
Rank Moved
Rank rose 155 spots (#250 → #95)
2026-09-07
Rank Moved
Rank dropped 15 spots (#213 → #228)
2026-09-05
Rank Moved
Rank dropped 46 spots (#166 → #212)
2026-08-31
Rank Moved
Rank dropped 17 spots (#124 → #141)
2026-08-26
Rank Moved
Rank dropped 12 spots (#104 → #116)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.1 Grade B
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.4 · Raw JSON