Desktop Commander — the complete, unedited output of the deterministic mcptrustchecker engine v1.5.0, scanned . Every finding, capability tag and score component below is exactly what the engine produced — no AI, no post-processing.
{
"tool": {
"name": "mcptrustchecker",
"version": "1.5.0",
"methodologyVersion": "mcptrustchecker-1.4"
},
"target": {
"id": "@wonderwhy-er/desktop-commander",
"source": {
"kind": "package",
"origin": "@wonderwhy-er/desktop-commander"
},
"server": {
"name": "@wonderwhy-er/desktop-commander"
}
},
"grade": "B",
"score": {
"score": 83,
"grade": "B",
"band": "B",
"categorySubtotals": {
"injection": 11.03,
"exfiltration": 0,
"permissions": 0,
"supply-chain": 6.3,
"network": 0,
"hygiene": 0
},
"vector": [
{
"ruleId": "MTC-SRC-009",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"rawWeight": 9,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 6.3
},
{
"ruleId": "MTC-SRC-009",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"rawWeight": 9,
"confidenceMult": 0.7,
"diminishingFactor": 0.5,
"appliedPenalty": 3.15
},
{
"ruleId": "MTC-SRC-009",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"rawWeight": 9,
"confidenceMult": 0.7,
"diminishingFactor": 0.25,
"appliedPenalty": 1.58
},
{
"ruleId": "MTC-SUP-010",
"category": "supply-chain",
"severity": "medium",
"confidence": "strong",
"rawWeight": 9,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 6.3
}
],
"gatesFired": [],
"methodologyVersion": "mcptrustchecker-1.4"
},
"capability": {
"level": "high",
"reasons": [
"can execute shell commands or code"
],
"tags": [
"code-exec"
]
},
"coverage": {
"level": "source",
"inputs": {
"toolSurface": false,
"implementationSource": true,
"packageMetadata": true,
"liveTransport": false
},
"caveats": [
"No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command \"npx -y <package>\"."
]
},
"findings": [
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (dist/ui/config-editor/config-editor-runtime.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/ui/config-editor/config-editor-runtime.js:26`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/ui/config-editor/config-editor-runtime.js"
},
"evidence": "new Function(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "dist/ui/config-editor/config-editor-runtime.js",
"line": 26
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/remote-device/desktop-commander-integration.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/remote-device/desktop-commander-integration.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.",
"remediation": "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": {
"kind": "server",
"name": "dist/remote-device/desktop-commander-integration.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/remote-device/desktop-commander-integration.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/remote-device/remote-channel.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/remote-device/remote-channel.js:473`): 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.",
"remediation": "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": {
"kind": "server",
"name": "dist/remote-device/remote-channel.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/remote-device/remote-channel.js",
"line": 473
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/search-manager.d.ts)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/search-manager.d.ts: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.",
"remediation": "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": {
"kind": "server",
"name": "dist/search-manager.d.ts"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/search-manager.d.ts",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/search-manager.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/search-manager.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.",
"remediation": "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": {
"kind": "server",
"name": "dist/search-manager.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/search-manager.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/setup-claude-server.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/setup-claude-server.js:8`): 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.",
"remediation": "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": {
"kind": "server",
"name": "dist/setup-claude-server.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/setup-claude-server.js",
"line": 8
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/terminal-manager.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/terminal-manager.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.",
"remediation": "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": {
"kind": "server",
"name": "dist/terminal-manager.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/terminal-manager.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/tools/feedback.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/tools/feedback.js:4`): 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.",
"remediation": "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": {
"kind": "server",
"name": "dist/tools/feedback.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/tools/feedback.js",
"line": 4
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/tools/filesystem.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/tools/filesystem.js:5`): 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.",
"remediation": "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": {
"kind": "server",
"name": "dist/tools/filesystem.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/tools/filesystem.js",
"line": 5
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/tools/improved-process-tools.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/tools/improved-process-tools.js:8`): 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.",
"remediation": "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": {
"kind": "server",
"name": "dist/tools/improved-process-tools.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/tools/improved-process-tools.js",
"line": 8
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (dist/tools/process.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`dist/tools/process.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.",
"remediation": "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": {
"kind": "server",
"name": "dist/tools/process.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "dist/tools/process.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (dist/track-installation.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`dist/track-installation.js:109`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/track-installation.js"
},
"evidence": "execSync(`ps -p ${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "dist/track-installation.js",
"line": 109
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (dist/utils/ripgrep-resolver.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`dist/utils/ripgrep-resolver.js:38`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/utils/ripgrep-resolver.js"
},
"evidence": "execSync(`${whichCmd} ${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "dist/utils/ripgrep-resolver.js",
"line": 38
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (dist/utils/system-info.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`dist/utils/system-info.js:374`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/utils/system-info.js"
},
"evidence": "execSync(`${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "dist/utils/system-info.js",
"line": 374
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (dist/npm-scripts/setup.js)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`dist/npm-scripts/setup.js:31`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/npm-scripts/setup.js"
},
"evidence": "import(setupScriptUrl.href)",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "dist/npm-scripts/setup.js",
"line": 31
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (dist/npm-scripts/uninstall.js)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`dist/npm-scripts/uninstall.js:31`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/npm-scripts/uninstall.js"
},
"evidence": "import(uninstallScriptUrl.href)",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "dist/npm-scripts/uninstall.js",
"line": 31
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (dist/setup-claude-server.js)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`dist/setup-claude-server.js:149`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/setup-claude-server.js"
},
"evidence": "import(versionPath)",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "dist/setup-claude-server.js",
"line": 149
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (dist/tools/fuzzySearch.js)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`dist/tools/fuzzySearch.js:16`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/tools/fuzzySearch.js"
},
"evidence": "import(workerData.moduleUrl)",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "dist/tools/fuzzySearch.js",
"line": 16
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (dist/uninstall-claude-server.js)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`dist/uninstall-claude-server.js:108`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.",
"remediation": "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": {
"kind": "server",
"name": "dist/uninstall-claude-server.js"
},
"evidence": "import(versionPath)",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "dist/uninstall-claude-server.js",
"line": 108
}
},
{
"ruleId": "MTC-SUP-010",
"title": "Package runs install-time scripts (postinstall)",
"category": "supply-chain",
"severity": "medium",
"confidence": "strong",
"description": "\"@wonderwhy-er/desktop-commander\" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.",
"remediation": "Review the scripts; install with --ignore-scripts where possible and vet what they do.",
"location": {
"kind": "package",
"name": "@wonderwhy-er/desktop-commander"
},
"owasp": "LLM03:2025 Supply Chain",
"references": [
"https://github.com/ossf/package-analysis",
"https://owasp.org/www-project-top-10-ci-cd-security-risks/"
],
"data": {
"scripts": [
"postinstall"
]
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "2eaaa10172383cf5e9646b69c33032464abc3c36ca99e763d72219fc0a6631e9",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 11,
"medium": 9,
"low": 0,
"info": 0
}
}
}