Evaluation report
Warnings@1mcp/agent · mcpf27f6cf· 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/1mcp-app/agent @ f27f6cf — ★ 458 · TypeScript · Apache-2.0 · last push 5 days ago
Manifest detected
kind=mcp slug=1mcp-agent · source=package.json
Slug is URL-safe
"1mcp-agent" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/1mcp-agent
Version is semver
0.32.2
Documentation
5 passedDescription quality
15 words · 93 chars — "One MCP server to aggregate them all - A unified Model Context Protocol server i…"
README is present and substantial
7,778 chars · 8 sections · 6 code blocks
Tags / topics declared
15 total — mcp, mcp-server, mcp-client, model-context-protocol, agent, proxy (+9)
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
https://github.com/1mcp-app/agent
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
20 high/critical advisories — @modelcontextprotocol/[email protected] (HIGH: GHSA-345p-7cg4-v4c7) · @modelcontextprotocol/[email protected] (HIGH: GHSA-8r9q-7v3j-jr4g) (+18)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE 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
5 passedMCP: launch path
bin: 1mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.25.1"
MCP: SDK version pinned
pinned at "^1.25.1"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 5 days ago
Tests detected
315 test files
CI configuration detected
GitHub Actions (8 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.