Evaluation report
Warnings@butterbase/mcp · mcp5bbee97· 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/butterbase-ai/butterbase @ 5bbee97 — ★ 2,529 · TypeScript · Apache-2.0 · last push today
Manifest detected
kind=mcp slug=butterbase-mcp · path=services/mcp-server · source=package.json
Slug is URL-safe
"butterbase-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/butterbase-mcp
Version is semver
1.1.1
Documentation
5 passedDescription quality
19 words · 135 chars — "Butterbase MCP server — manage schemas, auth, functions, storage, RAG, realtime,…"
README is present and substantial
14,680 chars · 14 sections · 10 code blocks
Tags / topics declared
14 total — mcp, model-context-protocol, butterbase, backend, database, auth (+8)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://butterbase.ai
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
5 passedMCP: launch path
bin: butterbase-mcp · 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: server surface
0 tools
Maintenance
2 passed1 warningCI 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.
Recent activity
last push today
Tests detected
11 test directories · 369 test files
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.