Evaluation report
Warnings@pv-bhat/vibe-check-mcp · mcpecac9cc· 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/PV-Bhat/vibe-check-mcp-server @ ecac9cc — ★ 492 · TypeScript · MIT · last push 8 days ago
Manifest detected
kind=mcp slug=pv-bhat-vibe-check-mcp · source=package.json
Slug is URL-safe
"pv-bhat-vibe-check-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/pv-bhat-vibe-check-mcp
Version is semver
2.8.1
Documentation
5 passedDescription quality
12 words · 94 chars — OK but more detail helps
README is present and substantial
18,253 chars · 19 sections · 8 code blocks
Tags / topics declared
21 total — mcp, mcp-server, vibe-check, vibe-coding, metacognition, ai-alignment (+15)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://github.com/PV-Bhat/vibe-check-mcp-server#readme
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
12 high/critical advisories — [email protected] (HIGH: GHSA-35jp-ww65-95wh) · [email protected] (HIGH: GHSA-3g43-6gmg-66jw) (+10)
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: vibe-check-mcp · scripts.start
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
3 passedRecent activity
last push 8 days ago
Tests detected
1 test directory · 23 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.