Evaluation report
Warningsbetter-chatbot · mcp489596f· 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/keinsaasforever/better-chatbot @ 489596f — ★ 1,133 · TypeScript · MIT · last push 9 days ago
Manifest detected
kind=mcp slug=better-chatbot · source=package.json
Slug is URL-safe
"better-chatbot" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/better-chatbot
Version is semver
1.26.0
Documentation
4 passed1 warningDescription qualitywarn
Only 3 words · 25 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
18,370 chars · 10 sections · 6 code blocks
Tags / topics declared
20 total — agent, ai, ai-chatbot, automation, chatbot, claude (+14)
README has usage / example sections
found: Quick Start · Getting Started · Quick Start (+2)
Homepage / docs URL declared
https://app.keinsaas.com/
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
2 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g)
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.25.1"
MCP: SDK version pinned
pinned at "^1.25.1"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 9 days ago
Tests detected
1 test directory · 52 test files
CI configuration detected
GitHub Actions (5 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.