Emailable MCP by usefulapi
by usefulapi.io · remote · no sign-in to list tools · v1.3.3 · published by io.usefulapi
Verify email addresses with Emailable one by one or in batches, and read credits and batch results.
4 tools: 2 can delete or cancel things and 2 only read.
Scanned Oct 21, 2026
- Deletes or cancels2Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads2Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http emailable https://emailable.usefulapi.io/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
4 tools
Deletes or cancels 2Claude Code: deny
emailable_create_batchSPENDS CREDITS: starts a bulk verification of up to 5000 email addresses.No findings
Why it is in this group
- The name "emailable_create_batch" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a batch verification
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
emailable_verify_emailSPENDS CREDITS: verifies one email address and uses 1 Emailable credit (a test_ API key spends none).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify one email address
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 2Claude Code: allow
emailable_get_accountThe Emailable account behind this API key: the owner's email and available_credits.No findings
Why it is in this group
- The name "emailable_get_account" says "get": a word for reading.
Description, as the server wrote it The Emailable account behind this API key: the owner's email and available_credits. Check it before a large batch. GET /v1/account.
Annotations the server declares
- title: Get account and credits
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
emailable_get_batchStatus and results of a batch made with emailable_create_batch: message, progress (processed/total), reason_counts and total_counts (deliverable, undeliverable, risky, unknown).No findings
Why it is in this group
- The name "emailable_get_batch" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get a batch verification
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.3.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http emailable https://emailable.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__emailable__emailable_get_account",
"mcp__emailable__emailable_get_batch"
],
"ask": [],
"deny": [
"mcp__emailable__emailable_verify_email",
"mcp__emailable__emailable_create_batch"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as emailable. Review it before you use it.