Ipykernel — 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": "ipykernel",
"source": {
"kind": "package",
"origin": "ipykernel"
},
"server": {
"name": "ipykernel"
}
},
"grade": "B",
"score": {
"score": 85,
"grade": "B",
"band": "B",
"categorySubtotals": {
"injection": 15.4,
"exfiltration": 0,
"permissions": 0,
"supply-chain": 0,
"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
}
],
"gatesFired": [],
"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 (tests/test_io.py)",
"category": "exfiltration",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`tests/test_io.py:206`): 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": "tests/test_io.py"
},
"evidence": "dict(os.environ)",
"owasp": "LLM02:2025 Sensitive Information Disclosure",
"data": {
"rule": "MTC-SRC-006",
"file": "tests/test_io.py",
"line": 206
}
},
{
"ruleId": "MTC-SRC-010",
"title": "Dynamic evaluation of a non-literal value (ipykernel/debugger.py)",
"category": "injection",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`ipykernel/debugger.py:663`): 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": "ipykernel/debugger.py"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-010",
"file": "ipykernel/debugger.py",
"line": 663
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (docs/conf.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`docs/conf.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": "docs/conf.py"
},
"evidence": "exec(compile(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "docs/conf.py",
"line": 79
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (ipykernel/debugger.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`ipykernel/debugger.py:663`): 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": "ipykernel/debugger.py"
},
"evidence": "eval(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "ipykernel/debugger.py",
"line": 663
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (docs/conf.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`docs/conf.py:79`): 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": "docs/conf.py"
},
"evidence": "exec(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "docs/conf.py",
"line": 79
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (ipykernel/ipkernel.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`ipykernel/ipkernel.py:694`): 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": "ipykernel/ipkernel.py"
},
"evidence": "exec(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "ipykernel/ipkernel.py",
"line": 694
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (ipykernel/zmqshell.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`ipykernel/zmqshell.py:775`): 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": "ipykernel/zmqshell.py"
},
"evidence": "os.system(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "ipykernel/zmqshell.py",
"line": 775
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (tests/inprocess/test_kernel.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`tests/inprocess/test_kernel.py:104`): 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/inprocess/test_kernel.py"
},
"evidence": "os.system(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "tests/inprocess/test_kernel.py",
"line": 104
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (tests/test_io.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`tests/test_io.py:210`): 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_io.py"
},
"evidence": "subprocess.run(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "tests/test_io.py",
"line": 210
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (tests/test_kernel.py)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`tests/test_kernel.py:290`): 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_kernel.py"
},
"evidence": "os.system(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "tests/test_kernel.py",
"line": 290
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (tests/test_async.py)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`tests/test_async.py:35`): 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": "tests/test_async.py"
},
"evidence": "__import__(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "tests/test_async.py",
"line": 35
}
},
{
"ruleId": "MTC-SRC-005",
"title": "Dynamic module load from a non-literal (tests/test_eventloop.py)",
"category": "permissions",
"severity": "medium",
"confidence": "heuristic",
"description": "In the server's implementation (`tests/test_eventloop.py:33`): 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": "tests/test_eventloop.py"
},
"evidence": "__import__(",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-005",
"file": "tests/test_eventloop.py",
"line": 33
}
},
{
"ruleId": "MTC-SUP-012",
"title": "Package has no license",
"category": "hygiene",
"severity": "info",
"confidence": "strong",
"description": "\"ipykernel\" has no declared license. This is a legal/reuse concern, not a security finding.",
"location": {
"kind": "package",
"name": "ipykernel"
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "c235cf3da74ab4534b156fc62fa1e0af35d1ccf5ca31588c91b1e3ae7b11a4b7",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 10,
"medium": 2,
"low": 0,
"info": 1
}
}
}