Raw scan report

For Splunk — 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.

← Back to the scan page
{
  "tool": {
    "name": "mcptrustchecker",
    "version": "1.13.0",
    "methodologyVersion": "mcptrustchecker-1.13"
  },
  "target": {
    "id": "mcp-server-for-splunk",
    "source": {
      "kind": "package",
      "origin": "mcp-server-for-splunk"
    },
    "server": {
      "name": "mcp-server-for-splunk"
    }
  },
  "grade": "A",
  "score": {
    "score": 92,
    "threatScore": 99,
    "grade": "A",
    "band": "A",
    "categorySubtotals": {
      "injection": 0,
      "exfiltration": 1.2,
      "permissions": 0,
      "supply-chain": 0,
      "network": 0,
      "hygiene": 0
    },
    "vector": [
      {
        "kind": "threat",
        "ruleId": "MTC-SRC-008",
        "category": "exfiltration",
        "severity": "low",
        "confidence": "heuristic",
        "rawWeight": 3,
        "confidenceMult": 0.4,
        "diminishingFactor": 1,
        "appliedPenalty": 1.2
      },
      {
        "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": true,
      "implementationSource": true,
      "packageMetadata": true,
      "liveTransport": false
    },
    "caveats": [
      "Tools were statically extracted from the published source (2 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command \"npx -y <package>\"."
    ]
  },
  "findings": [
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (src/resources/processors/html_processor.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`src/resources/processors/html_processor.py:315`): 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": "src/resources/processors/html_processor.py"
      },
      "evidence": "e to match, format X as eval(field=\"value\"). | | **dc(X)** | Returns the count of distinct values of the field X. | | **",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "src/resources/processors/html_processor.py",
        "line": 315,
        "nonRuntime": false
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (src/cli/build_and_run.py)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`src/cli/build_and_run.py:172`): 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": "src/cli/build_and_run.py"
      },
      "evidence": "nd works code = subprocess.run( # nosec B603 B607 [\"docker\", \"compose\", \"version\"], std",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "src/cli/build_and_run.py",
        "line": 172,
        "nonRuntime": false
      }
    },
    {
      "ruleId": "MTC-SRC-003",
      "title": "Hardcoded egress to an external endpoint in packaging/dev tooling (tests/test_token_auth.py)",
      "category": "exfiltration",
      "severity": "low",
      "confidence": "heuristic",
      "description": "In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_token_auth.py:105`): 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": "tests/test_token_auth.py"
      },
      "evidence": "}) service.http.request(\"https://splunk.example.com:8089/services/server/info\", {\"headers\": []}) a",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "rule": "MTC-SRC-003",
        "file": "tests/test_token_auth.py",
        "line": 105,
        "nonRuntime": true
      }
    },
    {
      "ruleId": "MTC-SRC-008",
      "title": "Hardcoded JSON Web Token in test/example/packaging (tests/security/test_credentials_handling.py)",
      "category": "exfiltration",
      "severity": "low",
      "confidence": "heuristic",
      "description": "A hardcoded JSON Web Token (an embedded JSON Web Token (often an example or expired token)) appears in `tests/security/test_credentials_handling.py:123`. Verify whether this is a real credential; if so, remove and rotate it.",
      "remediation": "Remove the secret, rotate it, and load credentials from the environment or a secret store.",
      "location": {
        "kind": "server",
        "name": "tests/security/test_credentials_handling.py"
      },
      "evidence": "JSON Web Token: eyJh…(redacted)",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "secretType": "jwt",
        "file": "tests/security/test_credentials_handling.py",
        "line": 123
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in packaging/dev tooling (tests/security/test_http_surface.py)",
      "category": "permissions",
      "severity": "low",
      "confidence": "heuristic",
      "description": "In a packaging/dev/install script (shipped, but not the server runtime) (`tests/security/test_http_surface.py:206`): 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/security/test_http_surface.py"
      },
      "evidence": "\"index=main\\\"; exec('rm -rf /')\", \"index=main` && cat /etc/passwd`\", \"index=main | $(wh",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "tests/security/test_http_surface.py",
        "line": 206,
        "nonRuntime": true
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in packaging/dev tooling (tests/test_mcp_server_comprehensive.py)",
      "category": "permissions",
      "severity": "low",
      "confidence": "heuristic",
      "description": "In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_mcp_server_comprehensive.py:1107`): 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/test_mcp_server_comprehensive.py"
      },
      "evidence": "requested result = subprocess.run( [\"uv\", \"run\", \"pytest\", __file__, \"-v\", \"--tb=short\"], cwd=os.pa",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "tests/test_mcp_server_comprehensive.py",
        "line": 1107,
        "nonRuntime": true
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in packaging/dev tooling (tests/test_server_dotenv_loading.py)",
      "category": "permissions",
      "severity": "low",
      "confidence": "heuristic",
      "description": "In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_server_dotenv_loading.py:38`): 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/test_server_dotenv_loading.py"
      },
      "evidence": "), })) \"\"\" result = subprocess.run( [sys.executable, \"-c\", script], cwd=cwd, env=env,",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "tests/test_server_dotenv_loading.py",
        "line": 38,
        "nonRuntime": true
      }
    }
  ],
  "toxicFlows": [],
  "capabilities": [
    {
      "tool": "sentry_test",
      "tags": [],
      "reasons": {}
    },
    {
      "tool": "user_agent_info",
      "tags": [],
      "reasons": {}
    }
  ],
  "surfaceDigest": "f4b372f30c2a1865223728871b69ff65f22dba84cdc2ad1081481b7d6d79ed53",
  "stats": {
    "tools": 2,
    "prompts": 0,
    "resources": 0,
    "findingsBySeverity": {
      "critical": 0,
      "high": 2,
      "medium": 0,
      "low": 5,
      "info": 0
    }
  }
}