run.chromeflow/chromeflow

MCPcommunity
v0.9.8run.chromeflowUnknownUpdated 4mo ago

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorrun.chromeflow
LicenseUnknown
Version0.9.8
Sourcemcp-registry
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

Source not readable3mo ago

The repository archive could not be read at scan time (tarball fetch returned 406), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.

About

Lets Claude Code or Codex CLI drive your real Chrome — sessions intact, 28 browser tools.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.