Getadvantage — the complete, unedited output of the deterministic mcptrustchecker engine v1.13.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.13.0",
"methodologyVersion": "mcptrustchecker-1.13"
},
"target": {
"id": "getadvantage",
"source": {
"kind": "package",
"origin": "getadvantage"
},
"server": {
"name": "getadvantage"
}
},
"grade": "A",
"score": {
"score": 93,
"threatScore": 100,
"grade": "A",
"band": "A",
"categorySubtotals": {
"injection": 0,
"exfiltration": 0,
"permissions": 0,
"supply-chain": 0,
"network": 0,
"hygiene": 0
},
"vector": [
{
"kind": "client",
"term": "capability-exposure",
"level": "high",
"label": "capability blast radius (high) — client exposure if the model is manipulated",
"appliedPenalty": 6
},
{
"kind": "client",
"term": "verification-discount",
"level": "repo",
"label": "publisher verification (public source) — no provenance, but the source is public and inspectable",
"appliedPenalty": 1
},
{
"kind": "client",
"term": "coverage-honesty",
"level": "source",
"label": "inspection depth (source) — how much of the target the scan could see",
"appliedPenalty": 0
}
],
"gatesFired": [],
"methodologyVersion": "mcptrustchecker-1.13"
},
"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-002",
"title": "Shell/command execution in server code (action/main.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`action/main.mjs:21`): 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": "action/main.mjs"
},
"evidence": "spawnSync } from \"node:child_process\"; import { appendFileSync, existsSync, readFileSync, statSync } from \"node:fs\"; im",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "action/main.mjs",
"line": 21,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (checks.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`checks.mjs:9`): 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": "checks.mjs"
},
"evidence": "ecFileSync } from \"node:child_process\"; import { closeSync, existsSync, openSync, readFileSync, readSync, statSync } fro",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "checks.mjs",
"line": 9,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (demo.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`demo.mjs:25`): 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": "demo.mjs"
},
"evidence": "ecFileSync } from \"node:child_process\"; import { tmpdir } from \"node:os\"; import path from \"node:path\"; import { c } fro",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "demo.mjs",
"line": 25,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (deploy.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`deploy.mjs:18`): 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": "deploy.mjs"
},
"evidence": "spawnSync } from \"node:child_process\"; import { cpSync, existsSync, mkdtempSync, rmSync } from \"node:fs\"; import { tmpd",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "deploy.mjs",
"line": 18,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (fanout.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`fanout.mjs:31`): 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": "fanout.mjs"
},
"evidence": "ecFileSync } from \"node:child_process\"; import path from \"node:path\"; import { c, git, gitSafe, gitRaw, relPath, pl } fr",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "fanout.mjs",
"line": 31,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (invisible-hook.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`invisible-hook.mjs:21`): 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": "invisible-hook.mjs"
},
"evidence": "spawnSync } from \"node:child_process\"; import { existsSync, mkdirSync, readFileSync, readSync, renameSync,",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "invisible-hook.mjs",
"line": 21,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (invisible.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`invisible.mjs:39`): 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": "invisible.mjs"
},
"evidence": "ecFileSync } from \"node:child_process\"; import { binName, c, cliVersion, gitSafe, MARKER_DIR, section, str",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "invisible.mjs",
"line": 39,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (util.mjs)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`util.mjs: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": "util.mjs"
},
"evidence": "ecFileSync } from \"node:child_process\"; import { existsSync, lstatSync, mkdirSync, readdirSync, readFileSync, statSync }",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "util.mjs",
"line": 5,
"nonRuntime": false
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in packaging/dev tooling (action/install.mjs)",
"category": "permissions",
"severity": "low",
"confidence": "heuristic",
"description": "In a packaging/dev/install script (shipped, but not the server runtime) (`action/install.mjs:13`): 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": "action/install.mjs"
},
"evidence": "spawnSync } from \"node:child_process\"; import { existsSync } from \"node:fs\"; import path from \"node:path\"; import { fil",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "action/install.mjs",
"line": 13,
"nonRuntime": true
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "4a3c4674204e7d48153037db84c9330cb149d4dfd32455ecad08b25f88ec99a0",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 8,
"medium": 0,
"low": 1,
"info": 0
}
}
}