Is Chrome MCP Server safe to use?

Chrome MCP Server has an HVTrust score of 33.7/100 (Grade D), ranked #1258 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Chrome MCP Server?

Chrome MCP Server scores 33.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 12.5k GitHub stars and is categorized under MCP Servers.

Chrome MCP Server

hangwin/mcp-chrome

Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser functionality to AI assistants like Claude, enabling complex browser automation, content analysis, and semantic search.

MCP Servers TypeScript Listed MIT

Is Chrome MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.3 / 10

Provenance None

Signed commits 3%

Last push 263d ago

Compare Chrome MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Chrome MCP Server scores 33.7/100 (Grade D), ranked #1258 of 1325 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 1.3/10; 3% of recent commits are signed; last pushed 2026-01-06. Every point is earned from checkable signals — never paid placement. How scoring works →

How Chrome MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Chrome MCP Server’s 33.7.

Where the 33.7 comes from

HVTrust dimensions vs the MCP Servers average

33.7 / 100 · 100.0% confidence

Chrome MCP Server MCP Servers average (775 agents)

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

1.8 / 25

8.5 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

9.6 / 17

2.6 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

9.8 / 20

2.6 above avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 1.3/10. Tighten the weakest checks to improve public safety evidence.

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

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Refresh maintenance signals The repo was last pushed 263 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Chrome MCP Server View MCP Servers Report missing data

38.8

Activity sub-score · out of 100

#753

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D 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-08-11 2026-09-26

Activity & Reach

Stars

12.5k

Forks

1.1k

Last Push

2026-01-06

263 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

202

Rank Change

▲2

was #1260

Analysis

Activity Inputs

38.8 / 100

StarsRepository reach

24.6 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

14.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

1.3 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 7

Branch-Protection 3

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions -1

Vulnerabilities 0

Common questions about Chrome MCP Server

Public trust evidence for Chrome MCP Server is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Chrome MCP Server publish package provenance?

No published build provenance is currently detected for Chrome MCP Server. 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 MCP Server have an OpenSSF Scorecard?

Chrome MCP Server has an OpenSSF Scorecard score of 1.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 MCP Server actively maintained?

Stale. The repository has not been pushed to in 263 days. Consider whether the project is still being maintained.

What license does Chrome MCP Server use?

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

Are Chrome MCP Server's commits signed?

3% of the last 100 commits to Chrome MCP Server 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 MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

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

How this surface has changed

Detected changes to Chrome MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

Maintain Chrome MCP Server?

For maintainers

HVTrust scores Chrome MCP Server 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-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 203 spots (#1055 → #1258)

2026-09-23

HVTrust Changed

HVTrust up 10.4pts (23.3 → 33.7)

2026-09-22

Newly Listed

First tracked at rank #1055

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-08

Rank Moved

Rank dropped 11 spots (#1232 → #1243)

2026-09-07

Rank Moved

Rank dropped 11 spots (#1221 → #1232)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1205 → #1221)

2026-09-05

Rank Moved

Rank dropped 31 spots (#1174 → #1205)

2026-09-04

Rank Moved

Rank dropped 16 spots (#1158 → #1174)

2026-09-03

Rank Moved

Rank dropped 41 spots (#1117 → #1158)

2026-09-02

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-09-02

Rank Moved

Rank dropped 37 spots (#1080 → #1117)

2026-09-01

Rank Moved

Rank dropped 42 spots (#1038 → #1080)

2026-08-31

Rank Moved

Rank dropped 35 spots (#1003 → #1038)

2026-08-30

Rank Moved

Rank dropped 52 spots (#951 → #1003)

2026-08-29

Rank Moved

Rank dropped 46 spots (#905 → #951)

2026-08-28

Rank Moved

Rank dropped 33 spots (#872 → #905)

2026-08-27

Scorecard Added

OSSF Scorecard: 1.3/10

2026-08-27

Rank Moved

Rank rose 393 spots (#1265 → #872)

2026-08-27

HVTrust Changed

HVTrust up 17.4pts (16.0 → 33.4)

2026-08-26

Rank Moved

Rank dropped 21 spots (#1244 → #1265)

2026-08-16

Rank Moved

Rank dropped 24 spots (#1220 → #1244)

2026-08-10

Newly Listed

First tracked at rank #1218

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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.3 · Raw JSON