Evaluation report

• Version is semverwarn

  "0.42.58.0" doesn't match MAJOR.MINOR.PATCH

  Use semver — e.g. `0.1.0`, `1.2.3-beta.1`. The CLI sorts updates by semver.

• Repository is reachable

  https://github.com/garrytan/gbrain @ a25209b — ★ 25,857 · TypeScript · MIT · last push yesterday

• Manifest detected

  kind=mcp slug=gbrain · source=package.json

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/gbrain

• Tags / topics declaredwarn

  No manifest tags and no GitHub repo topics

  Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.

• Description quality

  8 words · 63 chars — OK but more detail helps

• README is present and substantial

  37,713 chars · 14 sections · 17 code blocks

• README has usage / example sections

  found: Quick start

• Homepage / docs URL declared

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

• Dependencies: known vulnerabilities

  OSV.dev clean — 0 high/critical across 20 deps

• 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: gbrain

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "1.29.0"

• MCP: SDK version pinned

  pinned at "1.29.0"

• MCP: ESM package

  "type": "module"

• MCP: server surface

  0 tools

• Recent activity

  last push yesterday

• Tests detected

  2 test directories · 1201 test files

• CI configuration detected

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