Evaluation report

• Repository is reachable

  https://github.com/formulahendry/mcp-server-spec-driven-development @ 8a0532a — ★ 430 · TypeScript · MIT · last push 9 months ago

• Manifest detected

  kind=mcp slug=mcp-server-spec-driven-development · source=package.json

• Slug is URL-safe

  "mcp-server-spec-driven-development" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/mcp-server-spec-driven-development

• Version is semver

  0.1.1

• Description qualitywarn

  Only 4 words · 34 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  5,433 chars · 6 sections · 2 code blocks

• Tags / topics declared

  4 total — mcp, mcp-server, spec-driven-development, vibe-coding

• README has usage / example sections

  found: Installation

• Homepage / docs URL declared

  https://www.npmjs.com/package/mcp-server-spec-driven-development

• 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: mcp-server-spec-driven-development · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.17.0"

• MCP: SDK version pinned

  pinned at "^1.17.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools · 3 prompts

• Recent activitywarn

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