Evaluation report
Warningsshopify-mcp · mcpc90faaf· 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/GeLi2001/shopify-mcp @ c90faaf — ★ 220 · TypeScript · MIT · last push 3 months ago
Manifest detected
kind=mcp slug=shopify-mcp · source=package.json
Slug is URL-safe
"shopify-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/shopify-mcp
Version is semver
1.0.8
Documentation
5 passedDescription quality
13 words · 84 chars — OK but more detail helps
README is present and substantial
22,577 chars · 6 sections · 7 code blocks
Tags / topics declared
9 total — shopify, mcp, model-context-protocol, graphql, ai, llm (+3)
README has usage / example sections
found: Usage · Usage
Homepage / docs URL declared
https://github.com/GeLi2001/shopify-mcp#readme
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: shopify-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.17.1"
MCP: SDK version pinned
pinned at "^1.17.1"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
2 passed1 warningTests 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 3 months ago
CI configuration detected
GitHub Actions (1 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.