Evaluation report
Warningsvulnerable-mcp-server-secrets-pii · mcp47b7f20· last month
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/appsecco/vulnerable-mcp-servers-lab @ 47b7f20 — ★ 276 · JavaScript · MIT · last push 8 months ago
Manifest detected
kind=mcp slug=vulnerable-mcp-server-secrets-pii · path=vulnerable-mcp-server-secrets-pii · source=package.json
Slug is URL-safe
"vulnerable-mcp-server-secrets-pii" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/vulnerable-mcp-server-secrets-pii
Version is semver
1.0.3
Documentation
5 passedDescription quality
10 words · 52 chars — OK but more detail helps
README is present and substantial
5,166 chars · 7 sections
Tags / topics declared
13 total — mcp, server, tools, ai-red-teaming, ai-research, appsecco (+7)
README has usage / example sections
found: Getting started
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
1 high/critical advisory — @modelcontextprotocol/[email protected] (HIGH: GHSA-w48q-cv73-mx4w)
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: vulnerable-mcp-server-secrets-pii · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.0.4"
MCP: SDK version pinned
pinned at "^1.0.4"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 warningsRecent activitywarn
last push 8 months ago — looks slowing down
Consumers prefer artifacts that are actively maintained (threshold: 90 days, configurable via EVAL_RECENCY_PASS_DAYS).
Tests 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.