Emailable MCP by usefulapi
io.usefulapi/emailableusefulapi.iostreamable-httpv1.27.4Scanned
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.
- Reads private data · 2
- Reads text others write · 4
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Emailable MCP by usefulapi can do
The Emailable MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (2 tools: emailable_verify_email and emailable_create_batch). 2 tools only read.
2 tools read private data (emailable_get_account and emailable_get_batch); 4 tools bring in text other people can write (emailable_get_account, emailable_verify_email, emailable_create_batch and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.27.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Deletes or cancels 2Claude Code: deny
emailable_create_batchSPENDS CREDITS: starts a bulk verification of up to 5000 email addresses.Reads text others writeNo 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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).Reads text others writeNo 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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 2Show 2 read-only tools
emailable_get_accountThe Emailable account behind this API key: the owner's email and available_credits.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "emailable_get_account" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
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).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "emailable_get_batch" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "status" and "message": it reads messages.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "status" and "message": it reads messages, which other people can write.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://emailable.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://emailable.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://emailable.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://emailable.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.27.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http emailable https://emailable.usefulapi.io/mcpclaude mcp add --transport http emailable https://emailable.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as emailable. Review it before you use it.
Capability tags behind 4 rules
- mcp__emailable__emailable_get_account private-data, untrusted-input
- mcp__emailable__emailable_verify_email untrusted-input
- mcp__emailable__emailable_create_batch untrusted-input
- mcp__emailable__emailable_get_batch private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/emailable/verify?hash=d355b181a0d55f81814a3bd6f389e64f46f7b6be421eaa532b8600e24baad182" | jq -e '.changed == false'Pinned hash d355b181a0d5, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/emailable/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/emailable)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Emailable MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Emailable MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Emailable MCP by usefulapi delete data?
- Yes. 2 tools can delete, cancel or revoke something: emailable_verify_email and emailable_create_batch.
Can the Emailable MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Emailable MCP by usefulapi have?
- 4 tools: 2 destructive, 2 read. emailable_verify_email, emailable_create_batch, emailable_get_account and emailable_get_batch.
Does the Emailable MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Emailable MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Emailable MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.