Evaluation report

• Repository is reachable

  https://github.com/jau123/MeiGen-AI-Design-MCP @ f5a5322 — ★ 1,468 · TypeScript · MIT · last push 5 weeks ago

• Manifest detected

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

• Slug is URL-safe

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

• Slug is unique within kind

  No collision found for mcp/meigen

• Version is semver

  1.3.2

• Description quality

  17 words · 131 chars — "Visual creative expert plugin — search inspiration, enhance prompts, and generat…"

• README is present and substantial

  16,301 chars · 6 sections · 15 code blocks

• Tags / topics declared

  13 total — mcp, ai, image-generation, claude, meigen, prompt-engineering (+7)

• README has usage / example sections

  found: Quick Start

• Homepage / docs URL declared

  https://github.com/jau123/MeiGen-AI-Design-MCP#readme

• Dependencies: known vulnerabilitieswarn

  3 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+1)

  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: ESM packagewarn

  package.json missing "type": "module"

  Modern MCP servers are ESM. Add `"type": "module"` unless you have a CJS-only reason.

• MCP: launch path

  bin: meigen, meigen-mcp

• MCP: @modelcontextprotocol/sdk in dependencies

  pinned at "^1.12.0"

• MCP: SDK version pinned

  pinned at "^1.12.0"

• 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 5 weeks ago

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