updated 2026-08-12 05:02 UTC

Chrome MCP Server

hangwin/mcp-chrome

Chrome MCP Server is a Chrome extension-based Model Context Protocol (MCP) server that exposes your Chrome browser funct

MCP Servers TypeScript Grade D Listed MIT
16.0/100
Rank #1219 of 1283
Compare Chrome MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-01-06 · 218d ago
Recent change
New

Is Chrome MCP Server safe? Chrome MCP Server scores 16.0/100 (Grade D), ranked #1219 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 3% of recent commits are signed; last pushed 2026-01-06. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#713 A2asearch MCP — 16.2 (D) → #714 Skolverket MCP — 16.0 (D) → #716 Time MCP — 16.0 (D) → #717 MCP Funnel — 16.0 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #1218
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 218 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.7
Activity sub-score · out of 100
#715
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 218 days ago — may be stale

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
12.3k
Forks
1.1k
Last Push
2026-01-06
218 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
198
Rank Change
=
was #1219

Analysis

HVTrust Dimensions vs MCP Servers

16.0 / 100 · 50.0% confidence

Chrome MCP Server MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
4.9 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.4 below avg 12.4
AdoptionLog-scaled stars · package downloads
9.8 / 20
4.0 above avg 5.8

Activity Inputs

38.7 / 100
StarsRepository reach
24.5 / 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
—
Not available
Signed Commits
3%
of last 100 commits verified

Is Chrome MCP Server safe?

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?
No OpenSSF Scorecard data is currently published for Chrome MCP Server. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Chrome MCP Server actively maintained?
Stale. The repository has not been pushed to in 218 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.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Extensions
Extension based 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

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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #1218
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 16.0 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON