Universal Command MCP Server
universal-command-mcp
npm
v2.0.0
Published by moyangking — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 15.4 = 85. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −15.4 | Encoded-payload decode/execute instruction MTC-INJ-ENC-1 | injection |
2. Client adoption risk — 85 − 7 = 78. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 5
high Encoded-payload decode/execute instructionMTC-INJ-ENC-1
Encoded-payload decode/execute instruction detected in the description of tool "execute_base64_command". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.
Evidence: Base64 value as UTF-8 and execute
Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.
Location: tool execute_base64_command · description
high Tool "execute_command" exposes command/code executionMTC-CAP-001
Tool "execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool execute_command
high Shell/command execution in server code (dist/command.js)MTC-SRC-002
In the server's implementation (`dist/command.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import process from "node:process"; import { TextDecoder } from "node:util"; imp
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/command.js
medium Unconstrained command parameter "command" on "execute_command"MTC-CAP-006
Tool "execute_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool execute_command · inputSchema.properties.command
low Mutating tool "execute_command" declares no destructiveHintMTC-CAP-005
Tool "execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool execute_command
Tools 2
Each tool and what it can reach — statically extracted from the published source.
execute_commandruns code / shellexecute_base64_commandno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (2 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.0.0 latest |
C 78/100 | 5 | 1.9.0 | 2026-07-24 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan universal-command-mcp --onlineMore in Other
Security scan results for the Adapter MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ai MCP server.
Security scan results for the Airtable MCP server.
Security scan results for the Ani MCP server.
Security scan results for the Arango MCP server.