Evaluation report
Warnings@tugcantopaloglu/godot-mcp · mcpb77dfc7· 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/tugcantopaloglu/godot-mcp @ b77dfc7 — ★ 286 · JavaScript · MIT · last push 4 months ago
Manifest detected
kind=mcp slug=tugcantopaloglu-godot-mcp · source=package.json
Slug is URL-safe
"tugcantopaloglu-godot-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/tugcantopaloglu-godot-mcp
Version is semver
1.0.0
Documentation
5 passedDescription quality
15 words · 87 chars — "MCP server for full Godot 4.x engine control — 165 tools for AI-driven game deve…"
README is present and substantial
28,238 chars · 13 sections · 6 code blocks
Tags / topics declared
14 total — godot, mcp, ai, claude, cline, game-engine (+8)
README has usage / example sections
found: Installation · Example
Homepage / docs URL declared
https://github.com/tugcantopaloglu/godot-mcp
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
11 high/critical advisories — [email protected] (HIGH: GHSA-35jp-ww65-95wh) · [email protected] (HIGH: GHSA-3g43-6gmg-66jw) (+9)
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: godot-mcp
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "1.26.0"
MCP: SDK version pinned
pinned at "1.26.0"
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).
CI configuration detectedwarn
no CI config found (looked for GitHub Actions, CircleCI, GitLab CI, etc.)
Add a simple workflow (lint + test on PR) — it tells consumers the artifact is built reproducibly.
Tests detected
1 test directory · 3 test files
Behavioral
Behavioral results aren't published for this artifact. The publisher sees the full report on their own dashboard.