Evaluation report
Warningsmcp_remote_macos_use · mcp58c13c7· 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/baryhuang/mcp-remote-macos-use @ 58c13c7 — ★ 489 · Python · MIT · last push 1 year ago
Manifest detected
kind=mcp slug=mcp-remote-macos-use · source=pyproject.toml
Slug is URL-safe
"mcp-remote-macos-use" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/mcp-remote-macos-use
Version is semver
0.1.0
Documentation
4 passed1 warningDescription qualitywarn
Only 7 words · 37 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
9,341 chars · 11 sections · 3 code blocks
Tags / topics declared
6 total — claude-desktop, computer-use, general-agent, macos, macos-use, mcp-server
README has usage / example sections
found: Installation · Usage
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 warningRecent activitywarn
last push 1 year ago — looks slowing down
Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).
Tests detected
1 test directory · 7 test files
CI configuration detected
GitHub Actions (2 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.