Evaluation report

• Repository is reachable

  https://github.com/Tiberriver256/mcp-server-azure-devops @ e781791 — ★ 375 · TypeScript · MIT · last push 11 days ago

• Manifest detected

  kind=mcp slug=tiberriver256-mcp-server-azure-devops · source=package.json

• Slug is URL-safe

  "tiberriver256-mcp-server-azure-devops" matches /^[a-z0-9][a-z0-9-]{0,62}$/

• Slug is unique within kind

  No collision found for mcp/tiberriver256-mcp-server-azure-devops

• Version is semver

  0.1.45

• Description quality

  10 words · 66 chars — OK but more detail helps

• README is present and substantial

  13,407 chars · 11 sections · 6 code blocks

• Tags / topics declared

  9 total — azure-devops, mcp, ai, automation, claude, copilot (+3)

• README has usage / example sections

  found: Getting Started · Usage

• Homepage / docs URL declared

  no homepage declared (registry will use the repo URL) — info-only, not blocking

• Dependencies: known vulnerabilitieswarn

  18 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) · @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w) (+16)

  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: ESM packagewarn

  package.json missing "type": "module"

  Modern MCP servers are ESM. Add `"type": "module"` unless you have a CJS-only reason.

• MCP: launch path

  bin: mcp-server-azure-devops · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.6.0"

• MCP: SDK version pinned

  pinned at "^1.6.0"

• MCP: server surface

  0 tools

• Recent activity

  last push 11 days ago

• Tests detected

  2 test directories

• CI configuration detected

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