Evaluation report

• Repository is reachable

  https://github.com/ergut/mcp-logseq @ 35cf104 — ★ 290 · Python · MIT · last push yesterday

• Manifest detected

  kind=mcp slug=mcp-logseq · source=pyproject.toml

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/mcp-logseq

• Version is semver

  1.8.0

• Description quality

  11 words · 56 chars — OK but more detail helps

• README is present and substantial

  14,678 chars · 11 sections · 24 code blocks

• Tags / topics declared

  6 total — knowledge-base, knowledge-management, logseq, mcp, mcp-server, second-brain

• README has usage / example sections

  no labeled section but 24 code blocks document usage

• Homepage / docs URL declared

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

• 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

  launch declared in pyproject.toml

• MCP: @modelcontextprotocol/sdk in dependencies

  non-Node server (pyproject.toml) — uses its language's MCP SDK

• MCP: ESM package

  non-Node server (pyproject.toml) — n/a

• 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

  last push yesterday

• Tests detected

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