Evaluation report

• Repository is reachable

  https://github.com/apify/apify-mcp-server @ ec3ccfe — ★ 1,361 · TypeScript · MIT · last push today

• Manifest detected

  kind=mcp slug=apify-actors-mcp-server · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/apify-actors-mcp-server

• Version is semver

  0.11.3

• Description qualitywarn

  Only 3 words · 16 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  29,502 chars · 13 sections · 19 code blocks

• Tags / topics declared

  8 total — apify, mcp, server, actors, model context protocol, agents (+2)

• README has usage / example sections

  found: Example · Example · Example

• Homepage / docs URL declared

  https://mcp.apify.com

• Dependencies: known vulnerabilities

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

• LICENSE file at repo root

  LICENSE.md

• No sensitive files in the repo

  scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found

• MCP: launch path

  bin: actors-mcp-server · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "1.29.0"

• MCP: SDK version pinned

  pinned at "1.29.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activity

  last push today

• Tests detected

  1 test directory · 69 test files

• CI configuration detected

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