Petstore — 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": "petstore",
"source": {
"kind": "package",
"origin": "petstore"
},
"server": {
"name": "petstore"
}
},
"grade": "A",
"score": {
"score": 94,
"grade": "A",
"band": "A",
"categorySubtotals": {
"injection": 0,
"exfiltration": 0,
"permissions": 0,
"supply-chain": 6.3,
"network": 0,
"hygiene": 0
},
"vector": [
{
"ruleId": "MTC-SUP-010",
"category": "supply-chain",
"severity": "medium",
"confidence": "strong",
"rawWeight": 9,
"confidenceMult": 0.7,
"diminishingFactor": 1,
"appliedPenalty": 6.3
}
],
"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-001",
"title": "Dynamic code execution in server code (lib.swgg.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`lib.swgg.js:355`): 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": "lib.swgg.js"
},
"evidence": "Function(\"",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "lib.swgg.js",
"line": 355
}
},
{
"ruleId": "MTC-SRC-001",
"title": "Dynamic code execution in server code (test.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`test.js:345`): 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": "test.js"
},
"evidence": "Function(\"",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-001",
"file": "test.js",
"line": 345
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (lib.swgg.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`lib.swgg.js:224`): 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": "lib.swgg.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "lib.swgg.js",
"line": 224
}
},
{
"ruleId": "MTC-SRC-002",
"title": "Shell/command execution in server code (test.js)",
"category": "permissions",
"severity": "high",
"confidence": "strong",
"description": "In the server's implementation (`test.js:214`): 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": "test.js"
},
"evidence": "child_process",
"owasp": "LLM05:2025 Improper Output Handling",
"data": {
"rule": "MTC-SRC-002",
"file": "test.js",
"line": 214
}
},
{
"ruleId": "MTC-SUP-010",
"title": "Package runs install-time scripts (postinstall)",
"category": "supply-chain",
"severity": "medium",
"confidence": "strong",
"description": "\"petstore\" executes postinstall script(s) at install time. The large majority of malicious packages abuse install hooks to run code before you ever import them.",
"remediation": "Review the scripts; install with --ignore-scripts where possible and vet what they do.",
"location": {
"kind": "package",
"name": "petstore"
},
"owasp": "LLM03:2025 Supply Chain",
"references": [
"https://github.com/ossf/package-analysis",
"https://owasp.org/www-project-top-10-ci-cd-security-risks/"
],
"data": {
"scripts": [
"postinstall"
]
}
}
],
"toxicFlows": [],
"capabilities": [],
"surfaceDigest": "c74c5975b920c17ce8f74be1b56af6c9c5c1af1001e696966dffef82bc90b9b8",
"stats": {
"tools": 0,
"prompts": 0,
"resources": 0,
"findingsBySeverity": {
"critical": 0,
"high": 4,
"medium": 1,
"low": 0,
"info": 0
}
}
}