Email-Phishing-Detection-MCP

The server uses Express with 'morgan' for logging and handles JSON input. It implements an MCP server with a single tool for phishing detection. The core logic involves loading an ONNX model and performing inference. There are no obvious 'eval' calls, obfuscated code, or hardcoded secrets found in the provided snippets. The input 'emailText' is passed to 'onnxruntime-node' as a string tensor, which is generally safe against command injection for the ONNX runtime itself. Network risks are typical for any exposed API endpoint, but no specific vulnerabilities are introduced by the code itself beyond standard web server concerns (e.g., DoS, input validation where applicable, though 'z.string()' provides basic type validation). The server correctly handles unsupported HTTP methods (GET, DELETE) with a 405 response.