Verify email in Claude Code
Claude Code takes remote MCP servers over HTTP transport. One command adds Qualisend, and from then on the agent can verify addresses, clean lists and check a sending domain without leaving the terminal.
- MCP endpoint
- https://app.qualisend.com/api/mcp
- Authentication
- Sign-in or API key
- Available on
- Any Claude Code install. Adding an MCP server is not plan-gated.
Connect it to Claude Code
You need a Qualisend account - the free plan includes 100 verification credits that never expire - and Claude Code itself. Steps checked against Anthropic's documentation in September 2026.
- 1
Add the server
HTTP transport, one command. Add --scope user to make it available in every project, or --scope project to write a shared .mcp.json.
claude mcp add --transport http qualisend https://app.qualisend.com/api/mcp - 2
Sign in
Start Claude Code, run /mcp, select qualisend and finish in the browser. Over SSH use claude mcp login qualisend --no-browser and paste the callback URL back at the prompt.
/mcp - 3
Or use an API key instead
Prefer a static credential? Create one under Verification API -> API keys in your Qualisend dashboard and pass it as a header when you add the server.
claude mcp add --transport http qualisend https://app.qualisend.com/api/mcp \ --header "Authorization: Bearer qs_live_…" - 4
Check it
Run /mcp inside a session - qualisend should read connected. Outside a session, claude mcp list and claude mcp get qualisend do the same.
Sign-in or API key
Either. Sign in over OAuth from the /mcp menu, or pass a Qualisend API key as a bearer header. Pick one - setting a header yourself disables the sign-in fallback.
Check that it worked
Ask "how many Qualisend credits do I have left?". A number back means you are connected - that tool is free, so it costs nothing to test.
Config file
.mcp.jsonProject scope writes this file. The token is expanded at runtime, so the key itself never lands in the repo.
{
"mcpServers": {
"qualisend": {
"type": "http",
"url": "https://app.qualisend.com/api/mcp",
"headers": {
"Authorization": "Bearer ${QUALISEND_API_KEY}"
}
}
}
}Worth knowing
- If you set the Authorization header yourself, a 401 will not fall back to the sign-in flow - Claude Code just marks the server failed. Remove the header to use OAuth.
- claude mcp add does not validate the credential. A wrong key is saved silently and only shows up as failed in /mcp.
- "type": "http" is required in .mcp.json. A url with no type is a configuration error.
- Environment variable names that look like credentials (ANTHROPIC_API_KEY and similar) deliberately read as empty inside .mcp.json. Use your own name, such as QUALISEND_API_KEY.
- Shell expansion happens at add time, so --header writes the literal token into your config. Prefer the .mcp.json form above if that matters.
What to ask once it is connected
There are no commands to learn. Ask in your own words and Claude Code picks the right tool - there are twelve, covering verification, sending-domain deliverability and blacklist checks.
What Claude Code can reach
Only the verification tools, scoped to the single workspace you connect. It cannot reach another customer's data, your billing, or any admin function, and it never sees how a check is performed - just the verdict and the score. Authentication is an explicit token in a request header, never a cookie, so there is no session for a malicious page to borrow. Revoke it from Claude Code or from your Qualisend dashboard at any time; sign-in access also expires on its own within an hour. Full detail is on the MCP documentation page.
Claude Code FAQ
Anthropic's own reference: Claude Code MCP docs
Using something else?
It is the same endpoint everywhere. Pick your client:
Any other MCP-compatible client works too - Cline, JetBrains AI Assistant and the rest all take the same Streamable HTTP endpoint. The MCP documentation has the transport and authentication details.
Start free with 100 credits that never expire, then paste the endpoint.