Deploycheck — 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": "@deploycheck/deploycheck-mcp",
"source": {
"kind": "package",
"origin": "@deploycheck/deploycheck-mcp"
},
"server": {
"name": "@deploycheck/deploycheck-mcp"
}
},
"grade": "F",
"score": {
"score": 28,
"grade": "F",
"band": "F",
"gateCap": "C",
"categorySubtotals": {
"injection": 47.95,
"exfiltration": 22,
"permissions": 0,
"supply-chain": 2.1,
"network": 0,
"hygiene": 0
},
"vector": [
{
"ruleId": "MTC-SRC-008",
"category": "exfiltration",
"severity": "high",
"confidence": "confirmed",
"rawWeight": 22,
"confidenceMult": 1,
"diminishingFactor": 1,
"appliedPenalty": 22
},
{
"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-010",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 15.4
},
{
"ruleId": "MTC-SRC-010",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 0.5,
"appliedPenalty": 7.7
},
{
"ruleId": "MTC-SRC-011",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 15.4
},
{
"ruleId": "MTC-SUP-011",
"category": "supply-chain",
"severity": "low",
"confidence": "strong",
"rawWeight": 3,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 2.1
}
],
"gatesFired": [
"1 confirmed high finding → grade capped at C"
],
"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-008",
"title": "Hardcoded Slack token in server code (utils/testPhase3.js)",
"category": "exfiltration",
"severity": "high",
"confidence": "confirmed",
"description": "A live-looking Slack token is hardcoded in `utils/testPhase3.js:74`. Secrets in source ship to everyone who installs the package and are a direct credential leak.",
"remediation": "Remove the secret, rotate it, and load credentials from the environment or a secret store.",
"location": {
"kind": "server",
"name": "utils/testPhase3.js"
},
"evidence": "Slack token: xoxb…(redacted)",
"owasp": "LLM02:2025 Sensitive Information Disclosure",
"data": {
"secretType": "slack-token",
"file": "utils/testPhase3.js",
"line": 74
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (detectors/securityDetector.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`detectors/securityDetector.js:181`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate 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": "detectors/securityDetector.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "detectors/securityDetector.js",
"line": 181
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (utils/testPhase12.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`utils/testPhase12.js:30`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate 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": "utils/testPhase12.js"
},
"evidence": "eval (",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "utils/testPhase12.js",
"line": 30
}
},
{
"ruleId": "MTC-SRC-011",
"title": "Assembled command execution and dynamic evaluation in the same server",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "The implementation builds shell commands out of runtime values AND evaluates runtime values as code. Each is a separate arbitrary-execution primitive; a server exposing both gives anything that reaches either one a direct path to running attacker-chosen code.",
"remediation": "Remove the dynamic eval, and pass command arguments as an argv array instead of building a shell string. If both are genuinely required, constrain and validate every value that can reach them.",
"location": {
"kind": "server",
"name": "implementation"
},
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rules": [
"MTC-SRC-009",
"MTC-SRC-010"
]
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (detectors/securityDetector.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`detectors/securityDetector.js:171`): 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": "detectors/securityDetector.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "detectors/securityDetector.js",
"line": 171
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (scoring/complianceEngine.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`scoring/complianceEngine.js:76`): 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": "scoring/complianceEngine.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "scoring/complianceEngine.js",
"line": 76
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (utils/testPhase12.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`utils/testPhase12.js:30`): 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": "utils/testPhase12.js"
},
"evidence": "eval (",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "utils/testPhase12.js",
"line": 30
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (utils/testPhase4.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`utils/testPhase4.js:80`): 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": "utils/testPhase4.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "utils/testPhase4.js",
"line": 80
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (deployers/netlifyDeployer.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`deployers/netlifyDeployer.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": "deployers/netlifyDeployer.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "deployers/netlifyDeployer.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (deployers/railwayDeployer.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`deployers/railwayDeployer.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": "deployers/railwayDeployer.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "deployers/railwayDeployer.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (deployers/vercelDeployer.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`deployers/vercelDeployer.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": "deployers/vercelDeployer.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "deployers/vercelDeployer.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (detectors/depDetector.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`detectors/depDetector.js:11`): 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": "detectors/depDetector.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "detectors/depDetector.js",
"line": 11
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (detectors/pythonAstEngine.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`detectors/pythonAstEngine.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": "detectors/pythonAstEngine.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "detectors/pythonAstEngine.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (utils/logAnalyzer.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`utils/logAnalyzer.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": "utils/logAnalyzer.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "utils/logAnalyzer.js",
"line": 1
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (detectors/pythonAstEngine.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`detectors/pythonAstEngine.js:65`): 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": "detectors/pythonAstEngine.js"
},
"evidence": "execSync(`\"${pythonCmd}\" \"${parserPath}\" \"${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "detectors/pythonAstEngine.js",
"line": 65
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (utils/logAnalyzer.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`utils/logAnalyzer.js:27`): 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": "utils/logAnalyzer.js"
},
"evidence": "execSync(`git diff HEAD~${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "utils/logAnalyzer.js",
"line": 27
}
},
{
"ruleId": "MTC-SUP-011",
"title": "Package has no source repository",
"category": "supply-chain",
"severity": "low",
"confidence": "strong",
"description": "\"@deploycheck/deploycheck-mcp\" declares no repository URL, so its published artifact cannot be compared against reviewable source.",
"remediation": "Prefer packages that link to public, reviewable source.",
"location": {
"kind": "package",
"name": "@deploycheck/deploycheck-mcp"
}
},
{
"ruleId": "MTC-SUP-012",
"title": "Package has no license",
"category": "hygiene",
"severity": "info",
"confidence": "strong",
"description": "\"@deploycheck/deploycheck-mcp\" has no declared license. This is a legal/reuse concern, not a security finding.",
"location": {
"kind": "package",
"name": "@deploycheck/deploycheck-mcp"
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "9f4a5bdbbac347061dbe5126ea3f97a08d319733667aff858de72a0cc54ed432",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 14,
"medium": 2,
"low": 1,
"info": 1
}
}
}