Evaluation report
Warningsyex-trader · mcp58619a2· 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/Nunchi-trade/agent-cli @ 58619a2 — ★ 521 · Python · MIT · last push 3 days ago
Manifest detected
kind=mcp slug=yex-trader · source=pyproject.toml
Slug is URL-safe
"yex-trader" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/yex-trader
Version is semver
0.1.0
Documentation
4 passed1 warningTags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
Description quality
15 words · 106 chars — "Autonomous Hyperliquid trading CLI — deterministic and LLM-powered strategies fo…"
README is present and substantial
30,878 chars · 14 sections · 30 code blocks
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Safety
2 passedLICENSE 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
4 passedMCP: launch path
launch declared in pyproject.toml
MCP: @modelcontextprotocol/sdk in dependencies
non-Node server (pyproject.toml) — uses its language's MCP SDK
MCP: ESM package
non-Node server (pyproject.toml) — n/a
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 3 days ago
Tests detected
1 test directory · 112 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.