Evaluation report

• Repository is reachable

  https://github.com/etsd-tech/mcp-pointer @ 59601d1 — ★ 583 · TypeScript · MIT · last push 7 months ago

• Manifest detected

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

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/mcp-pointer-server

• Version is semver

  0.6.0

• README has usage / example sectionswarn

  README has no Usage / Example / Quick start / Installation heading at any level

  Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.

• Description quality

  12 words · 76 chars — OK but more detail helps

• README is present and substantial

  8,486 chars · 11 sections · 2 code blocks

• Tags / topics declared

  14 total — mcp, ai, pointer, websocket, element-targeting, agentic-coding (+8)

• Homepage / docs URL declared

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

• Dependencies: known vulnerabilitieswarn

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

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

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^0.5.0"

• MCP: SDK version pinned

  pinned at "^0.5.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activitywarn

  last push 7 months ago — looks slowing down

  Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).

• Tests detected

  1 test directory · 3 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.