Evaluation report

• Repository is reachable

  https://github.com/jnMetaCode/agency-orchestrator @ db87a1e — ★ 1,419 · TypeScript · Apache-2.0 · last push yesterday

• Manifest detected

  kind=mcp slug=agency-orchestrator · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/agency-orchestrator

• Version is semver

  0.7.5

• Description quality

  33 words · 191 chars — "Multi-agent YAML workflow engine — 211 AI roles, auto DAG parallelism, zero code…"

• README is present and substantial

  20,404 chars · 17 sections · 25 code blocks

• Tags / topics declared

  39 total — multi-agent, ai-agents, agent-orchestration, orchestrator, workflow, yaml-workflow (+33)

• README has usage / example sections

  no labeled section but 25 code blocks document usage

• Homepage / docs URL declared

  https://github.com/jnMetaCode/agency-orchestrator#readme

• Dependencies: known vulnerabilities

  OSV.dev clean — 0 high/critical across 5 deps

• 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: agency-orchestrator, ao

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.28.0"

• MCP: SDK version pinned

  pinned at "^1.28.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activity

  last push yesterday

• Tests detected

  1 test directory

• 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.