Raw scan report

Totem — 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": "@mmnto/totem",
    "source": {
      "kind": "package",
      "origin": "@mmnto/totem"
    },
    "server": {
      "name": "@mmnto/totem"
    }
  },
  "grade": "D",
  "score": {
    "score": 63,
    "grade": "D",
    "band": "D",
    "gateCap": "C",
    "categorySubtotals": {
      "injection": 15.4,
      "exfiltration": 22,
      "permissions": 0,
      "supply-chain": 0,
      "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-010",
        "category": "injection",
        "severity": "high",
        "confidence": "strong",
        "rawWeight": 22,
        "confidenceMult": 0.7,
        "diminishingFactor": 1,
        "appliedPenalty": 15.4
      }
    ],
    "gatesFired": [
      "1 confirmed high finding → grade capped at C"
    ],
    "methodologyVersion": "mcptrustchecker-1.4"
  },
  "capability": {
    "level": "high",
    "reasons": [
      "reads sensitive or local data",
      "has a read → egress path (a data-exfiltration surface)",
      "can execute shell commands or code"
    ],
    "tags": [
      "sensitive-source",
      "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-006",
      "title": "Reads a sensitive credential path or dumps the environment (dist/ingest/file-resolver.js)",
      "category": "exfiltration",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/ingest/file-resolver.js:73`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. 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/ingest/file-resolver.js"
      },
      "evidence": "~/.ssh",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "rule": "MTC-SRC-006",
        "file": "dist/ingest/file-resolver.js",
        "line": 73
      }
    },
    {
      "ruleId": "MTC-SRC-008",
      "title": "Hardcoded AWS access key id in server code (dist/sanitize.test.js)",
      "category": "exfiltration",
      "severity": "high",
      "confidence": "confirmed",
      "description": "A live-looking AWS access key id is hardcoded in `dist/sanitize.test.js:181`. 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": "dist/sanitize.test.js"
      },
      "evidence": "AWS access key id: AKIA…(redacted)",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "secretType": "aws-access-key",
        "file": "dist/sanitize.test.js",
        "line": 181
      }
    },
    {
      "ruleId": "MTC-SRC-010",
      "title": "Dynamic evaluation of a non-literal value (dist/semgrep-adapter.js)",
      "category": "injection",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/semgrep-adapter.js:66`): 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/semgrep-adapter.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-010",
        "file": "dist/semgrep-adapter.js",
        "line": 66
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/pipeline-observation.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/pipeline-observation.test.js:170`): 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/pipeline-observation.test.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/pipeline-observation.test.js",
        "line": 170
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/retired-lessons.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/retired-lessons.test.js:27`): 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/retired-lessons.test.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/retired-lessons.test.js",
        "line": 27
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/rule-tester.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/rule-tester.test.js:8`): 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/rule-tester.test.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/rule-tester.test.js",
        "line": 8
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/semgrep-adapter.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/semgrep-adapter.js:66`): 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/semgrep-adapter.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/semgrep-adapter.js",
        "line": 66
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/semgrep-adapter.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/semgrep-adapter.test.js:9`): 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/semgrep-adapter.test.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/semgrep-adapter.test.js",
        "line": 9
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (dist/spine/windtunnel-firing.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/spine/windtunnel-firing.test.js:20`): 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/spine/windtunnel-firing.test.js"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "dist/spine/windtunnel-firing.test.js",
        "line": 20
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/ast-query.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/ast-query.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": "dist/ast-query.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/ast-query.js",
        "line": 1
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/compile-lesson.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/compile-lesson.test.js:2333`): 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/compile-lesson.test.js"
      },
      "evidence": "spawn(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/compile-lesson.test.js",
        "line": 2333
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/compiler.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/compiler.test.js:1173`): 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/compiler.test.js"
      },
      "evidence": "spawn(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/compiler.test.js",
        "line": 1173
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/packaged-exports.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/packaged-exports.test.js:45`): 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/packaged-exports.test.js"
      },
      "evidence": "spawnSync(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/packaged-exports.test.js",
        "line": 45
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/parity-detect.test.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/parity-detect.test.js:905`): 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/parity-detect.test.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/parity-detect.test.js",
        "line": 905
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/sys/exec.d.ts)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/sys/exec.d.ts:18`): 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/sys/exec.d.ts"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/sys/exec.d.ts",
        "line": 18
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/sys/exec.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/sys/exec.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": "dist/sys/exec.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/sys/exec.js",
        "line": 6
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/sys/git.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/sys/git.js:111`): 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/sys/git.js"
      },
      "evidence": "spawn (",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/sys/git.js",
        "line": 111
      }
    },
    {
      "ruleId": "MTC-SRC-002",
      "title": "Shell/command execution in server code (dist/sys/helpers.js)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`dist/sys/helpers.js:12`): 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/sys/helpers.js"
      },
      "evidence": "child_process",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-002",
        "file": "dist/sys/helpers.js",
        "line": 12
      }
    },
    {
      "ruleId": "MTC-SRC-005",
      "title": "Dynamic module load from a non-literal (dist/ast-grep-wasm-shim.test.js)",
      "category": "permissions",
      "severity": "medium",
      "confidence": "heuristic",
      "description": "In the server's implementation (`dist/ast-grep-wasm-shim.test.js:19`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. 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/ast-grep-wasm-shim.test.js"
      },
      "evidence": "import(shimPath)",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-005",
        "file": "dist/ast-grep-wasm-shim.test.js",
        "line": 19
      }
    },
    {
      "ruleId": "MTC-SRC-005",
      "title": "Dynamic module load from a non-literal (dist/pack-discovery.js)",
      "category": "permissions",
      "severity": "medium",
      "confidence": "heuristic",
      "description": "In the server's implementation (`dist/pack-discovery.js:272`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. 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/pack-discovery.js"
      },
      "evidence": "require(resolvedPath)",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-005",
        "file": "dist/pack-discovery.js",
        "line": 272
      }
    }
  ],
  "toxicFlows": [],
  "capabilities": [],
  "surfaceDigest": "facf306581f084adfe5ad7812c616924012e7dd19830deb90caa82594c36f6f2",
  "stats": {
    "tools": 0,
    "prompts": 0,
    "resources": 0,
    "findingsBySeverity": {
      "critical": 0,
      "high": 18,
      "medium": 2,
      "low": 0,
      "info": 0
    }
  }
}