Evaluation report
Warningsbackend · mcpff4ff2d· 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/metatool-ai/metamcp @ ff4ff2d — ★ 2,515 · TypeScript · MIT · last push 3 weeks ago
Manifest detected
kind=mcp slug=backend · path=apps/backend · source=package.json
Slug is URL-safe
"backend" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/backend
Version is semver
1.0.0
Documentation
4 passed1 warningDescription qualitywarn
Only 7 words · 48 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
24,640 chars · 19 sections · 12 code blocks
Tags / topics declared
15 total — mcp, mcp-gateway, mcp-host, mcp-middleware, mcp-server, mcp-servers (+9)
README has usage / example sections
no labeled section but 12 code blocks document usage
Homepage / docs URL declared
https://docs.metamcp.com
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
10 high/critical advisories — @trpc/[email protected] (HIGH: GHSA-43p4-m455-4f4j) · [email protected] (HIGH: GHSA-392p-2q2v-4372) (+8)
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
scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "1.29.0"
MCP: SDK version pinned
pinned at "1.29.0"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 3 weeks ago
Tests detected
1 test directory · 14 test files
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.