Evaluation report
Warningsjscpd-server · mcp0d4af2a· 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/kucherenko/jscpd @ 0d4af2a — ★ 5,851 · TypeScript · MIT · last push yesterday
Manifest detected
kind=mcp slug=jscpd-server · path=apps/jscpd-server · source=package.json
Slug is URL-safe
"jscpd-server" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/jscpd-server
Version is semver
4.2.5
Documentation
4 passed1 warningDescription qualitywarn
Only 3 words · 24 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
10,869 chars · 12 sections · 2 code blocks
Tags / topics declared
15 total — ai, clones-detection, code-quality, coding-agents, copy-paste, copy-paste-detection (+9)
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
https://jscpd.dev
Safety
3 passedDependencies: known vulnerabilities
OSV.dev clean — 0 high/critical across 8 deps
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
4 passed1 warningMCP: ESM packagewarn
package.json missing "type": "module"
Modern MCP servers are ESM. Add `"type": "module"` unless you have a CJS-only reason.
MCP: launch path
bin: jscpd-server
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.29.0"
MCP: SDK version pinned
pinned at "^1.29.0"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push yesterday
Tests detected
9 test directories · 39 test files
CI configuration detected
GitHub Actions (6 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.