Evaluation report
Warnings@metapowers/figma-mcp · mcp7aee5d1· 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/bromso/metapowers @ 7aee5d1 — ★ 1 · MDX · MIT · last push 3 months ago
Manifest detected
kind=mcp slug=metapowers-figma-mcp · path=packages/figma-mcp · source=package.json
Slug is URL-safe
"metapowers-figma-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/metapowers-figma-mcp
Version is semver
0.1.0
Documentation
4 passed1 warningDescription qualitywarn
Only 3 words · 32 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
6,775 chars · 10 sections · 7 code blocks
Tags / topics declared
16 total — agents, claude-agent, claude-code, claude-code-plugin, claude-skills, codex (+10)
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
https://bromso.github.io/metapowers/
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
3 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) · @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w) (+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: metapowers-figma-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.0.0"
MCP: SDK version pinned
pinned at "^1.0.0"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 3 months ago
Tests detected
2 test directories · 17 test files
CI configuration detected
GitHub Actions (4 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.