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