Independent trust grade F (55/100). Prompt-injection / hidden-instruction markup found in package source. wmcp.sh continuously watches npm:cleaner-code for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
What it offers — 6 tools · Developer Tools
scan_file
Scan a single file for hidden malicious code patterns (invisible chars, BiDi, homoglyphs, steganography, obfuscation, etc.)
scan_directory
Recursively scan a directory for hidden malicious code patterns across all source files
scan_rules_file
Scan an AI configuration/rules file for prompt injection and Rules File Backdoor attacks
check_dependencies
Check package.json for typosquatting, suspicious install scripts, and dependency risks
ai_analyze
Deep AI analysis of code using the trained CodeBERT model. Classifies code chunks as malicious or benign with confidence scores. Detects obfuscated pa
explain_finding
Get detailed explanation of a specific threat category including attack scenarios, real-world examples, and remediation steps
Spec / packaging20%100
✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 6 tool(s) detected in source
Security (OWASP MCP)30%15
⚠ prompt-injection / hidden-instruction markup in source
⚠ references sensitive file paths / env secrets
uses eval/exec/child_process (review for unsanitized input)
scanned 6 source files
Maintenance / popularity20%92
published within 90 days
2 published versions
Tool hygiene15%95
✓ ships TypeScript types
3 runtime deps
Transparency / provenance15%90
✓ public repository linked
✓ ISC license
17 weekly downloads
Findings
FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.
INFO Static analysis of npm package cleaner-code@1.0.1 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:cleaner-code on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
<a href="https://wmcp.sh/mcp/grade/npm%3Acleaner-code"><img src="https://wmcp.sh/mcp/grade/npm%3Acleaner-code/badge.svg" alt="MCP Trust Grade F · wmcp.sh"></a>
Agents: check this before connecting
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.