Evaluation report

• Repository is reachable

  https://github.com/ttommyth/interactive-mcp @ 691b030 — ★ 351 · TypeScript · MIT · last push 8 months ago

• Manifest detected

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

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/interactive-mcp

• Version is semver

  1.0.0

• Description quality

  19 words · 124 chars — "Vibe coding should have human in the loop! interactive-mcp: Local, cross-platfor…" — manifest description is empty; graded the GitHub repo description instead

• README is present and substantial

  9,270 chars · 9 sections · 7 code blocks

• Tags / topics declared

  4 total — mcp, mcp-server, vibe-coding, vibecoding

• README has usage / example sections

  found: Usage · Usage · Usage (+1)

• Homepage / docs URL declared

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

• Dependencies: known vulnerabilitieswarn

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

  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: interactive-mcp · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.10.2"

• MCP: SDK version pinned

  pinned at "^1.10.2"

• MCP: ESM package

  "type": "module"

• MCP: 5 tools declared

  request_user_input, message_complete_notification, start_intensive_chat, ask_intensive_chat

• MCP: server surface

  5 tools

• Recent activitywarn

  last push 8 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 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.