Evaluation report
Warningsauq-mcp-server · mcp7d41b1b· 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/paulp-o/ask-user-questions-mcp @ 7d41b1b — ★ 114 · TypeScript · MIT · last push 3 months ago
Manifest detected
kind=mcp slug=auq-mcp-server · source=package.json
Slug is URL-safe
"auq-mcp-server" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/auq-mcp-server
Version is semver
3.4.0
Documentation
5 passedDescription quality
15 words · 75 chars — "An MCP server that provides a tool to ask a user questions via the terminal"
README is present and substantial
29,281 chars · 7 sections · 33 code blocks
Tags / topics declared
14 total — fastmcp, mcp, ask-user-questions, tui, terminal, agent-skills (+8)
README has usage / example sections
no labeled section but 33 code blocks document usage
Homepage / docs URL declared
https://github.com/paulp-o/ask-user-questions-mcp
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: auq · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "1.17.2"
MCP: SDK version pinned
pinned at "1.17.2"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 3 months ago
Tests detected
14 test directories · 50 test files
CI configuration detected
GitHub Actions (3 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.