Evaluation report

• Repository is reachable

  https://github.com/pi22by7/In-Memoria @ 9cbed0d — ★ 169 · Rust · MIT · last push 6 months ago

• Manifest detected

  kind=mcp slug=in-memoria · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/in-memoria

• Version is semver

  0.6.0

• Description qualitywarn

  Only 6 words · 62 chars — more detail helps discovery

  Tell consumers what this artifact does in a full sentence.

• README is present and substantial

  20,547 chars · 18 sections · 13 code blocks

• Tags / topics declared

  16 total — mcp, mcp-server, model-context-protocol, ai, ai-assistant, codebase-intelligence (+10)

• README has usage / example sections

  found: Example · Quick Start · Installation (+1)

• 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-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: in-memoria · scripts.start

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.21.1"

• MCP: SDK version pinned

  pinned at "^1.21.1"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activitywarn

  last push 6 months ago — looks slowing down

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

• Tests detected

  2 test directories · 10 test files

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