verifyDomain — email MCP Tool
verifyDomain
(verify domain) is one of 30 tools on the
email
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verifyDomain from your client
- Claude Code email verifyDomain run in your project directory
- Claude Desktop email verifyDomain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor email verifyDomain ~/.cursor/mcp.json
- VS Code email verifyDomain .vscode/mcp.json
- Zed email verifyDomain ~/.config/zed/settings.json
- Windsurf email verifyDomain ~/.codeium/windsurf/mcp_config.json
- Cline email verifyDomain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI email verifyDomain ~/.gemini/settings.json
- Grok email verifyDomain .mcp.json (in your project root)
- ChatGPT email verifyDomain Settings → Connectors → Advanced → Developer mode
- Claude.ai email verifyDomain Settings → Connectors → Add custom connector
- LangChain email verifyDomain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http email https://www.primitive.dev/mcpOther tools on this server
- listDomains
- addDomain
- downloadDomainZoneFile
- getAccount
- getInboxStatus
- getOutboundStatus
- listEmails
- searchEmails
- getEmail
- replyToEmail
- sendEmail
- sendEmailDemo
- listSentEmails
- getSentEmail
- cancelScheduledSend
- awaitReply
- getConversation
- getThread
- downloadEmailAttachments
- listEndpoints
- createEndpoint
- deleteEndpoint
- testEndpoint
- listFilters
- createFilter
- deleteFilter
- listWebhookDeliveries
- replayWebhookDelivery
- createEmailAddress
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.