Email verification, built for your agents.
Connect Qualisend to Claude, ChatGPT, or any MCP-compatible client and your AI agent can verify addresses and clean lists in plain language — with a real mailbox check behind every verdict. No code, no CSV exports, no copy-pasting keys.
verify_email deliverablehttps://app.qualisend.com/api/mcpConnected in under a minute
The MCP server is a single endpoint. Add it once in your AI client and every chat can verify email from then on.
Add the endpoint
In your client's connector settings, paste the Qualisend MCP endpoint. That's the only URL you need.
Sign in or paste a key
Approve access with one-click sign-in (OAuth 2.1) or supply a Qualisend API key. The connection is scoped to the workspace you approve.
Just ask
“Verify this address”, “are these 50 leads deliverable?”, “how many credits are left?” The agent calls the right tool and hands back a clear verdict.
Why verify through the agent
Plain language, no code
Your agent verifies in the flow of the conversation. No SDK, no CSV export, no context-switching to a dashboard.
A real mailbox check
Every address comes back deliverable, risky, undeliverable, or unknown — an actual SMTP check with a 0–100 score, not a regex guess.
One address or a thousand
Verify a single email inline, a batch of 50 in one call, or kick off an async job for a list of up to 1,000.
One-click, scoped connect
OAuth 2.1 with PKCE — no keys to copy. Access is limited to the workspace you approve and revocable any time.
Credits you control
The agent uses the same credits and rate limits as the API. Ask “how many credits are left?” before a big job — reads are free.
Works everywhere MCP does
One endpoint for Claude, ChatGPT, Cursor, and any MCP-compatible client — the same verdict, wherever your agent runs.
What you can ask
No commands to learn — the agent maps everyday requests to the right tool.
Connect it
Two ways in. Sign in for a keyless connection, or use a static API key — both reuse the same authentication and scope as the REST API.
Sign in (OAuth 2.1)
RecommendedAdd the endpoint as a custom connector; your client opens a “Connect Qualisend” page where you log in and approve access. No keys to copy, and you can revoke it from your client any time.
- 1Open your client's connector settings (e.g. Claude → Settings → Connectors → Add custom connector).
- 2Paste the MCP endpoint above and click Connect.
- 3Approve access to your workspace — done.
Or use an API key
Prefer a static credential? Create a key under Settings → API keys in your dashboard and supply it as the bearer token when you add the connector (Authorization: Bearer qs_live_…).
https://app.qualisend.com/api/mcpScoped, private, revocable
The MCP grants exactly what you approve — nothing more. It reuses the same auth, scope, rate-limit, and credit checks as the public API.
Scoped to one workspace
Every tool call is authenticated and limited to the workspace you connected. There's no path to another customer's data, admin functions, or any internal system.
Public verdict only
Responses contain only the same public fields the REST API returns — never internal engine details, probe infrastructure, or raw SMTP transcripts.
No cookies, no CSRF
Auth is an explicit token or key in the Authorization header — never a session cookie — so the endpoint has no cross-site surface. OAuth uses PKCE and exact redirect-URI matching.
Revoke any time
Disconnect the connector in your AI client, or revoke the key in your dashboard. OAuth access tokens are short-lived (1 hour) and refreshes rotate.
Full detail on how we handle your data is in the Privacy Policy.
MCP FAQ
Give your agent a real deliverability check
Start free with 100 credits that never expire, connect the MCP endpoint to your AI client, and let it verify email the moment it needs to.