Evaluation report
Warningstest-remote-server · mcpf443f7d· 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/MDalamin5/End-to-End-Agentic-Ai-Automation-Lab @ f443f7d — ★ 83 · Jupyter Notebook · MIT · last push 4 weeks ago
Manifest detected
kind=mcp slug=test-remote-server · path=11.5-Advanced-MCP-ownMCPs/01-Cloud-mcp-server · source=pyproject.toml
Slug is URL-safe
"test-remote-server" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/test-remote-server
Version is semver
0.1.0
Documentation
4 passed1 warningDescription qualitywarn
Only 4 words · 25 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
9,084 chars · 7 sections · 4 code blocks
Tags / topics declared
16 total — agentic-ai, agentic-rag, ambient-ai, autogen, deep-agents, docker (+10)
README has usage / example sections
no labeled section but 4 code blocks document usage
Homepage / docs URL declared
https://www.linkedin.com/in/mdalamin5/
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 4 weeks ago
Tests detected
3 test directories · 3 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.