Community Gmail server with auto-auth: search, read and send email via MCP.
Emailable MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Verify email addresses with Emailable one by one or in batches, and read credits and batch results.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http emailable-mcp-by-usefulapi https://emailable.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# emailable_get_account, emailable_verify_email, emailable_create_batch and 1 more
Emailable MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http emailable-mcp-by-usefulapi https://emailable.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The Emailable account behind this API key: the owner's email and available_credits. Check it before a large batch. GET /v1/account.
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The email address to verify. | |
| smtp | boolean | no | Run the SMTP step (default true). false is faster but much less accurate. |
| accept_all | boolean | no | Run the accept-all check (default false). It slows the reply. |
| timeout | integer | no | Seconds to wait for the result, 2-10 (default 5). |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| emails | array | yes | The email addresses to verify, 1-5000. |
| confirm | boolean | yes | Must be true. It confirms the user agreed to spend 1 credit per email (and a possible card charge for missing credits). |
| response_fields | array | no | Only these fields in each result (default: all). |
| retries | boolean | no | Retry mail-server answers for accuracy (default true). false is faster but gives more unknown results. |
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 bi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The batch id. |
| partial | boolean | no | Include the results so far while the batch is still running (only for batches of up to 1,000 emails). |
| include_emails | boolean | no | Include per-email results (default true). false returns the counts only. |
| offset | integer | no | First result to return (default 0). |
| limit | integer | no | Most results per call, 1-1000 (default 100). A reply can hold fewer; use emails_page.next_offset for the next page. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Emailable MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Emailable MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.