Evaluation report
Warningsmikrotik-mcp · mcp07a664a· 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
4 passed1 warningVersion is semverwarn
"0.7.1.0" doesn't match MAJOR.MINOR.PATCH
Use semver — e.g. `0.1.0`, `1.2.3-beta.1`. The CLI sorts updates by semver.
Repository is reachable
https://github.com/jeff-nasseri/mikrotik-mcp @ 07a664a — ★ 218 · Python · MIT · last push today
Manifest detected
kind=mcp slug=mikrotik-mcp · source=server.json
Slug is URL-safe
"mikrotik-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/mikrotik-mcp
Documentation
4 passed1 warningREADME has usage / example sectionswarn
README has no Usage / Example / Quick start / Installation heading at any level
Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.
Description quality
15 words · 95 chars — "MCP server for MikroTik routers: firewall, NAT, routing, DHCP, DNS, WireGuard an…"
README is present and substantial
3,020 chars · 4 sections
Tags / topics declared
13 total — ai, ai-agents, ai-assistant, ai-tools, llms, mcp (+7)
Homepage / docs URL declared
https://github.com/jeff-nasseri/mikrotik-mcp
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 server.json
MCP: @modelcontextprotocol/sdk in dependencies
non-Node server (server.json) — uses its language's MCP SDK
MCP: ESM package
non-Node server (server.json) — n/a
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push today
Tests detected
1 test directory · 12 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.