Evaluation report
Warningscomfyui-mcp · mcp90ebf1d· 3 months ago
Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.
Structural
5 passedRepository is reachable
https://github.com/artokun/comfyui-mcp @ 90ebf1d — ★ 167 · TypeScript · MIT · last push yesterday
Manifest detected
kind=mcp slug=comfyui-mcp · source=package.json
Slug is URL-safe
"comfyui-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/comfyui-mcp
Version is semver
0.16.0
Documentation
5 passedDescription quality
37 words · 216 chars — "Claude Code plugin + MCP server for ComfyUI - 96 tools, 16 AI skills (Flux, WAN,…"
README is present and substantial
41,444 chars · 12 sections · 27 code blocks
Tags / topics declared
18 total — comfyui, mcp, mcp-server, model-context-protocol, claude-code, claude-plugin (+12)
README has usage / example sections
found: Quick Start · Example
Homepage / docs URL declared
https://comfyui-mcp.artokun.io/docs
Safety
2 passed1 warningDependencies: 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
Kind-specific
5 passedMCP: launch path
bin: comfyui-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.12.1"
MCP: SDK version pinned
pinned at "^1.12.1"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push yesterday
Tests detected
1 test directory · 62 test files
CI configuration detected
GitHub Actions (3 workflows)
Behavioral
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.