check_domain_email_security — Mail Security Tools MCP Tool Read-only
check_domain_email_security
(check domain email security) is one of 5 tools on the
Mail Security Tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_domain_email_security from your client
- Claude Code Mail Security Tools check_domain_email_security run in your project directory
- Claude Desktop Mail Security Tools check_domain_email_security ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mail Security Tools check_domain_email_security ~/.cursor/mcp.json
- VS Code Mail Security Tools check_domain_email_security .vscode/mcp.json
- Zed Mail Security Tools check_domain_email_security ~/.config/zed/settings.json
- Windsurf Mail Security Tools check_domain_email_security ~/.codeium/windsurf/mcp_config.json
- Cline Mail Security Tools check_domain_email_security ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mail Security Tools check_domain_email_security ~/.gemini/settings.json
- Grok Mail Security Tools check_domain_email_security .mcp.json (in your project root)
- ChatGPT Mail Security Tools check_domain_email_security Settings → Connectors → Advanced → Developer mode
- Claude.ai Mail Security Tools check_domain_email_security Settings → Connectors → Add custom connector
- LangChain Mail Security Tools check_domain_email_security pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email-security https://api.mailsecuritytools.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.