Evaluation report

• Repository is reachable

  https://github.com/cjo4m06/mcp-shrimp-task-manager @ 8a3be6b — ★ 2,117 · JavaScript · MIT · last push 10 months ago

• Manifest detected

  kind=mcp slug=mcp-shrimp-task-manager · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/mcp-shrimp-task-manager

• Version is semver

  1.0.21

• Description quality

  39 words · 289 chars — "Shrimp Task Manager is a task tool built for AI Agents, emphasizing chain-of-tho…"

• README is present and substantial

  7,490 chars · 9 sections · 11 code blocks

• Tags / topics declared

  16 total — mcp, task-manager, agent, workflow, ai, codeagent (+10)

• README has usage / example sections

  found: Installation

• Homepage / docs URL declared

  https://cjo4m06.github.io/mcp-shrimp-task-manager

• 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: mcp-shrimp-task-manager · 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 10 months ago — looks slowing down

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

• Tests detected

  2 test directories · 14 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.