Evaluation report

• Repository is reachable

  https://github.com/hangwin/mcp-chrome @ f48e717 — ★ 12,087 · TypeScript · MIT · last push 6 months ago

• Manifest detected

  kind=mcp slug=mcp-chrome-bridge · path=app/native-server · source=package.json

• Slug is URL-safe

  "mcp-chrome-bridge" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/mcp-chrome-bridge

• Version is semver

  1.0.29

• Description qualitywarn

  Only 4 words · 35 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  13,002 chars · 11 sections · 5 code blocks

• Tags / topics declared

  3 total — mcp, chrome, browser

• README has usage / example sections

  found: Installation · Usage

• Homepage / docs URL declared

  no homepage declared (registry will use the repo URL) — info-only, not blocking

• Dependencies: known vulnerabilitieswarn

  6 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+4)

  Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)

• LICENSE file at repo root

  LICENSE

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• MCP: ESM packagewarn

  package.json missing "type": "module"

  Modern MCP servers are ESM. Add `"type": "module"` unless you have a CJS-only reason.

• MCP: launch path

  bin: mcp-chrome-bridge, chrome-mcp-bridge, mcp-chrome-stdio

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.11.0"

• MCP: SDK version pinned

  pinned at "^1.11.0"

• MCP: server surface

  0 tools

• Recent activitywarn

  last push 6 months ago — looks slowing down

  Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).

• Tests detected

  1 test directory · 39 test files

• CI configuration detected

  GitHub Actions (1 workflows)

This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.