Evaluation report
Warningsoverture · mcp14c8929· 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/SixHq/Overture @ 14c8929 — ★ 621 · TypeScript · MIT · last push 4 months ago
Manifest detected
kind=mcp slug=overture · source=package.json
Slug is URL-safe
"overture" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/overture
Version is semver
0.1.0
Documentation
5 passedDescription quality
10 words · 58 chars — OK but more detail helps
README is present and substantial
22,276 chars · 19 sections · 10 code blocks
Tags / topics declared
24 total — mcp, ai, agent, visualization, planning, claude (+18)
README has usage / example sections
no labeled section but 10 code blocks document usage
Homepage / docs URL declared
https://github.com/sixth/overture#readme
Safety
2 passedLICENSE 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
3 passed1 warningMCP: @modelcontextprotocol/sdk in dependencieswarn
No @modelcontextprotocol/sdk dependency declared
Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.
MCP: launch path
scripts.start
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
1 passed2 warningsRecent activitywarn
last push 4 months ago — looks slowing down
Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).
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.
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.