Evaluation report

• Repository is reachable

  https://github.com/VectifyAI/pageindex-mcp @ f6e9ac7 — ★ 371 · TypeScript · MIT · last push 6 weeks ago

• Manifest detected

  kind=mcp slug=pageindex-mcp · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/pageindex-mcp

• Version is semver

  1.8.1

• Description qualitywarn

  Only 4 words · 24 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  5,329 chars · 1 section · 3 code blocks

• Tags / topics declared

  4 total — mcp, model-context-protocol, pageindex, document-processing

• README has usage / example sections

  no labeled section but 3 code blocks document usage

• Homepage / docs URL declared

  https://github.com/VectifyAI/pageindex-mcp

• Dependencies: known vulnerabilitieswarn

  4 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+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: pageindex-mcp · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.17.3"

• MCP: SDK version pinned

  pinned at "^1.17.3"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Tests detectedwarn

  no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files

  Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.

• Recent activity

  last push 6 weeks ago

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