Is the npm:@mcpware/claude-code-organizer MCP server safe to use?
Independent trust grade F (55/100). Prompt-injection / hidden-instruction markup found in package source. wmcp.sh continuously watches npm:@mcpware/claude-code-organizer for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.
What it offers — 5 tools · Finance & Crypto
scan_inventory
Scan all Claude Code configurations across Global and Project scopes. Returns memories, skills, MCP servers, hooks, configs, plugins, and plans with t
move_item
Move a Claude Code configuration item (memory, skill, MCP server) from one scope to another. Run scan_inventory first to see available items and scope
delete_item
Delete a Claude Code configuration item (memory, skill, MCP server entry). Run scan_inventory first to see available items and scope IDs.
list_destinations
List valid destination scopes for a specific item. Shows where this item can be moved to.
audit_security
Scan all MCP servers for security vulnerabilities. Connects to each server, retrieves tool definitions, and runs pattern-based detection for prompt in
Spec / packaging20%100
✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 5 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%100
published within 90 days
118 published versions
Tool hygiene15%70
no TypeScript types
1 runtime deps
Transparency / provenance15%90
✓ public repository linked
✓ MIT license
189 weekly downloads
Findings
FAILMCP01 Prompt-injection / hidden-instruction markup found in package source.
INFO Static analysis of npm package @mcpware/claude-code-organizer@0.18.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:@mcpware/claude-code-organizer 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%3A%40mcpware%2Fclaude-code-organizer"><img src="https://wmcp.sh/mcp/grade/npm%3A%40mcpware%2Fclaude-code-organizer/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.