Evaluation report

• Repository is reachable

  https://github.com/sharpdeveye/maestro @ 00f9115 — ★ 402 · TypeScript · MIT · last push 2 months ago

• Manifest detected

  kind=mcp slug=maestro-workflow-mcp · path=mcp-server · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/maestro-workflow-mcp

• Version is semver

  2.0.1

• Description quality

  19 words · 117 chars — "MCP server for Maestro — exposes 25 workflow skills as tools, prompts, and resou…"

• README is present and substantial

  13,398 chars · 12 sections · 11 code blocks

• Tags / topics declared

  18 total — mcp, maestro, ai, workflow, skills, agents (+12)

• README has usage / example sections

  found: Quick Start · Example · Example

• Homepage / docs URL declared

  https://github.com/sharpdeveye/maestro

• 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: maestro-workflow-mcp · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.12.0"

• MCP: SDK version pinned

  pinned at "^1.12.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activity

  last push 2 months ago

• Tests detected

  2 test directories · 6 test files

• CI configuration detected

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