Evaluation report

• Repository is reachable

  https://github.com/boshyxd/robloxstudio-mcp @ 2e4345d — ★ 472 · TypeScript · MIT · last push 2 weeks ago

• Manifest detected

  kind=mcp slug=robloxstudio-mcp · path=packages/robloxstudio-mcp · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/robloxstudio-mcp

• Version is semver

  2.7.0

• Description quality

  16 words · 100 chars — "MCP Server for Roblox Studio Integration - Access Studio data, scripts, and obje…"

• README is present and substantial

  4,234 chars · 3 sections · 10 code blocks

• Tags / topics declared

  12 total — mcp, roblox, studio, ai, model-context-protocol, game-development (+6)

• README has usage / example sections

  no labeled section but 10 code blocks document usage

• Homepage / docs URL declared

  https://github.com/boshyxd/robloxstudio-mcp#readme

• Dependencies: known vulnerabilitieswarn

  2 high/critical advisories — [email protected] (HIGH: GHSA-3h5v-q93c-6h6q) · [email protected] (HIGH: GHSA-96hv-2xvq-fx4p)

  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: robloxstudio-mcp

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.27.1"

• MCP: SDK version pinned

  pinned at "^1.27.1"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• CI configuration detectedwarn

  no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)

  Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.

• Recent activity

  repo is archived (last push 2 weeks ago) — intentionally read-only

• Tests detected

  1 test directory · 6 test files

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.