Evaluation report
Warningsandroid-mcp · mcp3557d6d· 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/CursorTouch/Android-MCP @ 3557d6d — ★ 686 · Python · MIT · last push today
Manifest detected
kind=mcp slug=android-mcp · source=pyproject.toml
Slug is URL-safe
"android-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/android-mcp
Version is semver
0.2.0
Documentation
4 passed1 warningDescription qualitywarn
Only 7 words · 51 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
8,835 chars · 8 sections · 3 code blocks
Tags / topics declared
4 total — ai, android, automation, mcp-server
README has usage / example sections
found: Installation
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
1 passed2 warningsTests detectedwarn
no test/tests/__tests__/spec/t/ dirs, no JVM src/test/, and no JS/TS/Python/Go/Ruby/Elixir test files
Add tests (even a smoke test). Consumers gauge maintenance quality by their presence.
CI 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
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.