Verify email addresses with Emailable one by one or in batches, and read credits and batch results. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"emailable": {
"url": "https://emailable.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"emailable": {
"type": "http",
"url": "https://emailable.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Emailable private API key.
Find it in Emailable → API → your API keys (create a private key; do not restrict it to trusted IP addresses, because Cloudflare's IPs change). Use a test_ key to try it without spending credits. A live_ key spends your Emailable credits (1 per verified email), and a bulk batch may charge your saved card if credits run short. Your key is used only to call the Emailable API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Emailable private API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
emailable_get_account | read | Get account and credits The Emailable account behind this API key: the owner's email and available_credits. Check it before a large batch. GET /v1/account. |
emailable_verify_email | write | Verify one email address SPENDS CREDITS: verifies one email address and uses 1 Emailable credit (a test_ API key spends none). Returns state (deliverable, undeliverable, risky, unknown), reason, score (0-100), and flags: disposable, free, role, accept_all, no_reply, mailbox_full, plus did_you_mean (a typo fix), the detected user/domain/tag, mx_record and smtp_provider. A credit is returned for an unknown result. The call is never retried automatically. If the reply is {status: "try_again"}, the check took longer than the timeout: call again with the same email; repeats within 5 minutes are not charged. Emailable's terms allow verification of opt-in subscribers' addresses. GET /v1/verify. |
emailable_create_batch | write | Create a batch verification SPENDS CREDITS: starts a bulk verification of up to 5000 email addresses. Emailable takes 1 credit per email when the batch is created, and if the account has too few credits it may charge the account's saved card to buy more. A test_ API key spends nothing. The batch cannot be cancelled here, and the call is never retried: if it fails or times out, check emailable_get_account before trying again, because a retry can charge twice. Returns the batch id; poll it with emailable_get_batch. Emailable's terms allow verification of opt-in subscribers' addresses. POST /v1/batch. |
emailable_get_batch | read | Get a batch verification Status and results of a batch made with emailable_create_batch: message, progress (processed/total), reason_counts and total_counts (deliverable, undeliverable, risky, unknown). Batches of up to 1,000 emails also return the results inline in `emails` (30 days). They come in pages: up to `limit` results, fewer if the reply would get too long; ask for the next page with emails_page.next_offset. A bigger batch returns download_file, a temporary link (5 days) to a ZIP of a CSV: share it only with the account owner. Free to call. GET /v1/batch. |
emailable_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
emailable_request_feature | Request a missing feature Tell usefulapi that the user needs something the Emailable tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
emailable_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Emailable tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
emailable_cancel_subscription | Cancel the Pro subscription Cancel the caller's Emailable Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run emailable_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Emailable server only. Subscribe with emailable_upgrade (it returns a Stripe Checkout link). Cancel any time with emailable_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running emailable_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Emailable. The server calls the Emailable API with your own Emailable access, so it sees only the data that your account can see.
The login page asks for your Emailable private API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Emailable private API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Emailable API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Emailable.
Yes, if you approve it. 2 of the 4 Emailable tools can create or change data. The other 2 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Emailable server only. Run emailable_usage_status to see how many calls you used.
Ask the AI to run emailable_upgrade: it returns a Stripe Checkout link. To cancel, run emailable_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with emailable_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.