mailtrap-mcp

The server follows good security practices: sensitive credentials (Mailtrap API token) are expected from environment variables and marked as 'sensitive' in the manifest. Input validation is performed using JSON schemas (though Zod is used internally for schema definition). No direct 'eval' or obvious malicious patterns were found. Network communication is handled by `axios` to the Mailtrap API, and the MCP server uses standard I/O, minimizing direct network exposure from the server itself. The code includes error handling for missing environment variables. The sandbox client explicitly checks for the `MAILTRAP_TEST_INBOX_ID` environment variable.