Raw scan report

Puppeteer Real Browser — 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.

← Back to the scan page
{
  "tool": {
    "name": "mcptrustchecker",
    "version": "1.5.0",
    "methodologyVersion": "mcptrustchecker-1.4"
  },
  "target": {
    "id": "@eikaramba/puppeteer-real-browser-mcp-server",
    "source": {
      "kind": "package",
      "origin": "@eikaramba/puppeteer-real-browser-mcp-server"
    },
    "server": {
      "name": "@eikaramba/puppeteer-real-browser-mcp-server"
    }
  },
  "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-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 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-010",
      "title": "Dynamic evaluation of a non-literal value (dist/handlers/content-handlers.js)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/handlers/content-handlers.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": "dist/handlers/content-handlers.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "dist/handlers/content-handlers.js",
        "line": 22
      }
    },
    {
      "ruleId": "MTC-SRC-010",
      "title": "Dynamic evaluation of a non-literal value (dist/handlers/file-handlers.js)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/handlers/file-handlers.js:147`): 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": "dist/handlers/file-handlers.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "dist/handlers/file-handlers.js",
        "line": 147
      }
    },
    {
      "ruleId": "MTC-SRC-010",
      "title": "Dynamic evaluation of a non-literal value (dist/handlers/interaction-handlers.js)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/handlers/interaction-handlers.js:45`): 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": "dist/handlers/interaction-handlers.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "dist/handlers/interaction-handlers.js",
        "line": 45
      }
    },
    {
      "ruleId": "MTC-SRC-010",
      "title": "Dynamic evaluation of a non-literal value (dist/index-original.js)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/index-original.js:1604`): 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": "dist/index-original.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "dist/index-original.js",
        "line": 1604
      }
    },
    {
      "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 (dist/handlers/content-handlers.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/handlers/content-handlers.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": "dist/handlers/content-handlers.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/handlers/content-handlers.js",
        "line": 22
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/handlers/file-handlers.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/handlers/file-handlers.js:147`): 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/handlers/file-handlers.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/handlers/file-handlers.js",
        "line": 147
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/handlers/interaction-handlers.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/handlers/interaction-handlers.js:45`): 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/handlers/interaction-handlers.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/handlers/interaction-handlers.js",
        "line": 45
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/index-original.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/index-original.js:1604`): 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/index-original.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/index-original.js",
        "line": 1604
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/browser-manager.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/browser-manager.js:173`): 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/browser-manager.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/browser-manager.js",
        "line": 173
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/browser-manager.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/browser-manager.test.js:17`): 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/browser-manager.test.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/browser-manager.test.js",
        "line": 17
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/index-original.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/index-original.js:422`): 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/index-original.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/index-original.js",
        "line": 422
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/system-utils.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/system-utils.js:60`): 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/system-utils.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/system-utils.js",
        "line": 60
      }
    },
    {
      "ruleId": "MTC-SRC-009",
      "title": "Untrusted input concatenated into a command sink (dist/system-utils.js)",
      "category": "injection",
      "severity": "medium",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/system-utils.js:63`): 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/system-utils.js"
      },
      "evidence": "execSync(`${command} ${",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-009",
        "file": "dist/system-utils.js",
        "line": 63
      }
    }
  ],
  "toxicFlows": [],
  "capabilities": [],
  "surfaceDigest": "dbd071fb0c895f2bed5d4c17921dafc28d945a31fb5b8ea1233de508b18b6be6",
  "stats": {
    "tools": 0,
    "prompts": 0,
    "resources": 0,
    "findingsBySeverity": {
      "critical": 0,
      "high": 13,
      "medium": 1,
      "low": 0,
      "info": 0
    }
  }
}