Evaluation report

• Repository is reachable

  https://github.com/unmodeled-tyler/vessel-browser @ 75c44bf — ★ 109 · TypeScript · MIT · last push today

• Manifest detected

  kind=mcp slug=quanta-intellect-vessel-browser · source=package.json

• Slug is URL-safe

  "quanta-intellect-vessel-browser" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/quanta-intellect-vessel-browser

• Version is semver

  0.1.0

• Description quality

  10 words · 74 chars — OK but more detail helps

• README is present and substantial

  31,605 chars · 11 sections · 17 code blocks

• Tags / topics declared

  27 total — agent-browser, ai-agent, browser-automation, electron, human-in-the-loop, linux (+21)

• README has usage / example sections

  found: Quick Start · Getting Started

• Homepage / docs URL declared

  https://quantaintellect.com

• Dependencies: known vulnerabilities

  OSV.dev clean — 0 high/critical across 7 deps

• 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: vessel-browser

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.29.0"

• MCP: SDK version pinned

  pinned at "^1.29.0"

• MCP: server surface

  0 tools

• Recent activity

  last push today

• Tests detected

  1 test directory · 45 test files

• CI configuration detected

  GitHub Actions (7 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.