Raw scan report

Data Science — 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": "data-science-mcp",
    "source": {
      "kind": "package",
      "origin": "data-science-mcp"
    },
    "server": {
      "name": "data-science-mcp"
    }
  },
  "grade": "C",
  "score": {
    "score": 75,
    "grade": "C",
    "band": "C",
    "categorySubtotals": {
      "injection": 23.1,
      "exfiltration": 0,
      "permissions": 0,
      "supply-chain": 2.1,
      "network": 0,
      "hygiene": 0
    },
    "vector": [
      {
        "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-SUP-011",
        "category": "supply-chain",
        "severity": "low",
        "confidence": "strong",
        "rawWeight": 3,
        "confidenceMult": 0.7,
        "diminishingFactor": 1,
        "appliedPenalty": 2.1
      }
    ],
    "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 (data_science_mcp/inference/base.py)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/inference/base.py:6`): 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": "data_science_mcp/inference/base.py"
      },
      "evidence": "eval (",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "data_science_mcp/inference/base.py",
        "line": 6
      }
    },
    {
      "ruleId": "MTC-SRC-010",
      "title": "Dynamic evaluation of a non-literal value (data_science_mcp/training_pipeline.py)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/training_pipeline.py:238`): 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": "data_science_mcp/training_pipeline.py"
      },
      "evidence": "eval (",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "data_science_mcp/training_pipeline.py",
        "line": 238
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/inference/base.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/inference/base.py:6`): 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": "data_science_mcp/inference/base.py"
      },
      "evidence": "eval (",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/inference/base.py",
        "line": 6
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/kernels/_runner.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/kernels/_runner.py:49`): 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": "data_science_mcp/kernels/_runner.py"
      },
      "evidence": "exec(compile(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/kernels/_runner.py",
        "line": 49
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/trainers/dpo_trainer.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/trainers/dpo_trainer.py:70`): 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": "data_science_mcp/trainers/dpo_trainer.py"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/trainers/dpo_trainer.py",
        "line": 70
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/trainers/grpo_trainer.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/trainers/grpo_trainer.py:79`): 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": "data_science_mcp/trainers/grpo_trainer.py"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/trainers/grpo_trainer.py",
        "line": 79
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/trainers/ppo_trainer.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/trainers/ppo_trainer.py:93`): 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": "data_science_mcp/trainers/ppo_trainer.py"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/trainers/ppo_trainer.py",
        "line": 93
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/training/deep_delegate.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/training/deep_delegate.py:127`): 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": "data_science_mcp/training/deep_delegate.py"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/training/deep_delegate.py",
        "line": 127
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/training/trading_lstm.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/training/trading_lstm.py:190`): 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": "data_science_mcp/training/trading_lstm.py"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/training/trading_lstm.py",
        "line": 190
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (data_science_mcp/training_pipeline.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/training_pipeline.py:238`): 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": "data_science_mcp/training_pipeline.py"
      },
      "evidence": "eval (",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "data_science_mcp/training_pipeline.py",
        "line": 238
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (tests/test_launch.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`tests/test_launch.py:2`): 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": "tests/test_launch.py"
      },
      "evidence": "eval (",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "tests/test_launch.py",
        "line": 2
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (data_science_mcp/kernels/_runner.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/kernels/_runner.py:49`): 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": "data_science_mcp/kernels/_runner.py"
      },
      "evidence": "exec(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "data_science_mcp/kernels/_runner.py",
        "line": 49
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (data_science_mcp/kernels/kernel_verifier.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`data_science_mcp/kernels/kernel_verifier.py:53`): 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": "data_science_mcp/kernels/kernel_verifier.py"
      },
      "evidence": "subprocess.run(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "data_science_mcp/kernels/kernel_verifier.py",
        "line": 53
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (scripts/security_sanitizer.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`scripts/security_sanitizer.py:136`): 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": "scripts/security_sanitizer.py"
      },
      "evidence": "subprocess.run(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "scripts/security_sanitizer.py",
        "line": 136
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (tests/conftest.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`tests/conftest.py:81`): 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": "tests/conftest.py"
      },
      "evidence": "subprocess.Popen(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "tests/conftest.py",
        "line": 81
      }
    },
    {
      "ruleId": "MTC-SUP-011",
      "title": "Package has no source repository",
      "category": "supply-chain",
      "severity": "low",
      "confidence": "strong",
      "description": "\"data-science-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": "data-science-mcp"
      }
    }
  ],
  "toxicFlows": [],
  "capabilities": [],
  "surfaceDigest": "456f8b276c2a4acb2f17bbdabbebf12911f2cd475cae0588467cf6d59071b0e3",
  "stats": {
    "tools": 0,
    "prompts": 0,
    "resources": 0,
    "findingsBySeverity": {
      "critical": 0,
      "high": 15,
      "medium": 0,
      "low": 1,
      "info": 0
    }
  }
}