Evaluation report
Warningskompl-mcp · mcp865d320· 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/tuirk/Kompl @ 865d320 — ★ 74 · TypeScript · Apache-2.0 · last push today
Manifest detected
kind=mcp slug=kompl-mcp · path=mcp-server · source=package.json
Slug is URL-safe
"kompl-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/kompl-mcp
Version is semver
1.0.0
Documentation
4 passed1 warningDescription qualitywarn
Only 3 words · 20 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
15,174 chars · 12 sections · 12 code blocks
Tags / topics declared
16 total — docker-compose, fastapi, gemini, knowledge-management, llm, llm-wiki (+10)
README has usage / example sections
no labeled section but 12 code blocks document usage
Homepage / docs URL declared
https://github.com/tuirk/Kompl
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
6 passedMCP: launch path
scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.12.0"
MCP: SDK version pinned
pinned at "^1.12.0"
MCP: ESM package
"type": "module"
MCP: 4 tools declared
search_wiki, read_page, list_pages, wiki_stats
MCP: server surface
4 tools
Maintenance
3 passedRecent activity
last push today
Tests detected
5 test directories · 86 test files
CI configuration detected
GitHub Actions (2 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.