Evaluation report

• Repository is reachable

  https://github.com/hanzili/comet-mcp @ 6f10c86 — ★ 160 · TypeScript · MIT · last push 5 months ago

• Manifest detected

  kind=mcp slug=comet-mcp · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/comet-mcp

• Version is semver

  2.3.0

• Description quality

  20 words · 139 chars — "MCP Server that gives Claude Code superpowers with Perplexity Comet browser - ag…"

• README is present and substantial

  4,732 chars · 8 sections · 4 code blocks

• Tags / topics declared

  15 total — mcp, model-context-protocol, claude, claude-code, comet, perplexity (+9)

• README has usage / example sections

  found: Quick Start

• Homepage / docs URL declared

  https://github.com/hanzili/comet-mcp#readme

• Dependencies: known vulnerabilitieswarn

  2 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) · @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w)

  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: launch path

  bin: comet-mcp · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.0.0"

• MCP: SDK version pinned

  pinned at "^1.0.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activitywarn

  last push 5 months ago — looks slowing down

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

• Tests detectedwarn

  no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files

  Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.

• CI configuration detectedwarn

  no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)

  Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.

Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.