uses eval/exec/child_process (review for unsanitized input)
scanned 6 source files
Maintenance / popularity20%75
last published ~8mo ago
4 published versions
Tool hygiene15%95
✓ ships TypeScript types
2 runtime deps
Transparency / provenance15%90
✓ public repository linked
✓ MIT license
11 weekly downloads
Findings
INFO Static analysis of npm package node-server-orchestrator@1.0.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:node-server-orchestrator 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%3Anode-server-orchestrator"><img src="https://wmcp.sh/mcp/grade/npm%3Anode-server-orchestrator/badge.svg" alt="MCP Trust Grade B · 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.