check_domain — Email Deliverability Checker MCP Tool Read-only
check_domain
(check domain) is one of 3 tools on the
Email Deliverability Checker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_domain from your client
- Claude Code Email Deliverability Checker check_domain run in your project directory
- Claude Desktop Email Deliverability Checker check_domain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Email Deliverability Checker check_domain ~/.cursor/mcp.json
- VS Code Email Deliverability Checker check_domain .vscode/mcp.json
- Zed Email Deliverability Checker check_domain ~/.config/zed/settings.json
- Windsurf Email Deliverability Checker check_domain ~/.codeium/windsurf/mcp_config.json
- Cline Email Deliverability Checker check_domain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Email Deliverability Checker check_domain ~/.gemini/settings.json
- Grok Email Deliverability Checker check_domain .mcp.json (in your project root)
- ChatGPT Email Deliverability Checker check_domain Settings → Connectors → Advanced → Developer mode
- Claude.ai Email Deliverability Checker check_domain Settings → Connectors → Add custom connector
- LangChain Email Deliverability Checker check_domain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email-deliverability-mcp https://api.ownmailserver.com/tools/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 27 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.