Evaluation report

• Repository is reachable

  https://github.com/BiboyQG/WeChat-MCP @ cc47036 — ★ 212 · Python · MIT · last push 3 months ago

• Manifest detected

  kind=mcp slug=wechat-mcp-server · source=pyproject.toml

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/wechat-mcp-server

• Version is semver

  0.2.0

• Description quality

  13 words · 83 chars — OK but more detail helps

• README is present and substantial

  4,342 chars · 9 sections · 6 code blocks

• Tags / topics declared

  3 total — mcp, mcp-server, wechat

• README has usage / example sections

  found: Quick Start · Installation · Usage

• Homepage / docs URL declared

  https://biboyqg.github.io/WeChat-MCP/

• 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

• Recent activitywarn

  last push 3 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 · 4 test files

• CI configuration detected

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