Raw scan report

Docs — 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": "@voltagent/docs-mcp",
    "source": {
      "kind": "package",
      "origin": "@voltagent/docs-mcp"
    },
    "server": {
      "name": "@voltagent/docs-mcp"
    }
  },
  "grade": "C",
  "score": {
    "score": 78,
    "grade": "C",
    "band": "C",
    "gateCap": "C",
    "categorySubtotals": {
      "injection": 0,
      "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
      }
    ],
    "gatesFired": [
      "1 confirmed high finding → grade capped at C"
    ],
    "methodologyVersion": "mcptrustchecker-1.4"
  },
  "capability": {
    "level": "high",
    "reasons": [
      "can send data / act on an external service",
      "can execute shell commands or code"
    ],
    "tags": [
      "code-exec",
      "external-sink"
    ]
  },
  "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-008",
      "title": "Hardcoded JSON Web Token in server code (examples/with-voltagent-actions/src/config.ts)",
      "category": "exfiltration",
      "severity": "high",
      "confidence": "confirmed",
      "description": "A live-looking JSON Web Token is hardcoded in `examples/with-voltagent-actions/src/config.ts:66`. 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": "examples/with-voltagent-actions/src/config.ts"
      },
      "evidence": "JSON Web Token: eyJh…(redacted)",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "secretType": "jwt",
        "file": "examples/with-voltagent-actions/src/config.ts",
        "line": 66
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (examples/next-js-chatbot-starter-template/lib/tools/calculator.ts)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`examples/next-js-chatbot-starter-template/lib/tools/calculator.ts:24`): 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": "examples/next-js-chatbot-starter-template/lib/tools/calculator.ts"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "examples/next-js-chatbot-starter-template/lib/tools/calculator.ts",
        "line": 24
      }
    },
    {
      "ruleId": "MTC-SRC-001",
      "title": "Dynamic code execution in server code (examples/with-playwright/src/tools/interactionTool.ts)",
      "category": "permissions",
      "severity": "high",
      "confidence": "strong",
      "description": "In the server's implementation (`examples/with-playwright/src/tools/interactionTool.ts:94`): 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": "examples/with-playwright/src/tools/interactionTool.ts"
      },
      "evidence": "eval(",
      "owasp": "LLM05:2025 Improper Output Handling",
      "data": {
        "rule": "MTC-SRC-001",
        "file": "examples/with-playwright/src/tools/interactionTool.ts",
        "line": 94
      }
    },
    {
      "ruleId": "MTC-SRC-003",
      "title": "Hardcoded egress to an external endpoint (examples/github-star-stories/src/tools.ts)",
      "category": "exfiltration",
      "severity": "medium",
      "confidence": "strong",
      "description": "In the server's implementation (`examples/github-star-stories/src/tools.ts:13`): 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": "examples/github-star-stories/src/tools.ts"
      },
      "evidence": "fetch(`https://api.github.com/users/${username}`",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "rule": "MTC-SRC-003",
        "file": "examples/github-star-stories/src/tools.ts",
        "line": 13
      }
    },
    {
      "ruleId": "MTC-SRC-003",
      "title": "Hardcoded egress to an external endpoint (examples/with-tavily-search/src/tools.ts)",
      "category": "exfiltration",
      "severity": "medium",
      "confidence": "strong",
      "description": "In the server's implementation (`examples/with-tavily-search/src/tools.ts:63`): 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": "examples/with-tavily-search/src/tools.ts"
      },
      "evidence": "fetch(\"https://api.tavily.com/search\"",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "rule": "MTC-SRC-003",
        "file": "examples/with-tavily-search/src/tools.ts",
        "line": 63
      }
    },
    {
      "ruleId": "MTC-SRC-003",
      "title": "Hardcoded egress to an external endpoint (examples/with-whatsapp/src/webhooks/whatsapp.ts)",
      "category": "exfiltration",
      "severity": "medium",
      "confidence": "strong",
      "description": "In the server's implementation (`examples/with-whatsapp/src/webhooks/whatsapp.ts:13`): 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": "examples/with-whatsapp/src/webhooks/whatsapp.ts"
      },
      "evidence": "fetch(`https://graph.facebook.com/v18.0/${phoneNumberId}/messages`",
      "owasp": "LLM02:2025 Sensitive Information Disclosure",
      "data": {
        "rule": "MTC-SRC-003",
        "file": "examples/with-whatsapp/src/webhooks/whatsapp.ts",
        "line": 13
      }
    }
  ],
  "toxicFlows": [],
  "capabilities": [],
  "surfaceDigest": "1bd01a06ca8474b8ddfe2d4ee7e3ba51f9535db7a3644dfd39113a10634e84d1",
  "stats": {
    "tools": 0,
    "prompts": 0,
    "resources": 0,
    "findingsBySeverity": {
      "critical": 0,
      "high": 3,
      "medium": 3,
      "low": 0,
      "info": 0
    }
  }
}