VerifyAnyEmail
NPM · VERIFYANYEMAIL-MCP · 2 COMPONENTS
Real-time email verification and deliverability diagnostics (MX, SPF, DKIM, DMARC).
Available components
Last scanned (18 hours ago)
Scores higher than 34% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 711 tokens (~79/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/verifyanyemail-mcp@1.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_dkim ~68
Check a domain's DKIM signing record for a given selector. Free — no verification credits.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to inspect, e.g. example.com |
| selector | string | – | The DKIM selector, e.g. 'google' or 'mail'. Optional. |
No output schema declared.
No examples provided.
check_dmarc ~50
Check a domain's DMARC policy (none | quarantine | reject) and alignment. Free — no verification credits.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to inspect, e.g. example.com |
No output schema declared.
No examples provided.
check_domain_health ~67
Run an overall email-deliverability health check for a domain — combines MX, SPF, DKIM, DMARC and related signals into a single graded summary with actionable findings. Free — no verification credits.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to inspect, e.g. example.com |
No output schema declared.
No examples provided.
check_mx ~50
Look up a domain's MX (mail exchanger) records and whether it can receive email. Free — no verification credits.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to inspect, e.g. example.com |
No output schema declared.
No examples provided.
check_spf ~45
Check a domain's SPF record and flag common misconfigurations. Free — no verification credits.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to inspect, e.g. example.com |
No output schema declared.
No examples provided.
get_batch_results ~83
Fetch a page of results for a bulk verification batch. Paginated — use page and pageSize for large batches.
| Name | Type | Req | Description |
|---|---|---|---|
| batchId | string | yes | The batchId returned by verify_batch. |
| page | integer | – | 1-based page number. Default 1. |
| pageSize | integer | – | Rows per page (1–1000). Default 100. |
No output schema declared.
No examples provided.
get_batch_status ~54
Check the progress of a bulk verification batch: lifecycle state (queued | processing | completed | failed), addresses processed, and per-status counts once available.
| Name | Type | Req | Description |
|---|---|---|---|
| batchId | string | yes | The batchId returned by verify_batch. |
No output schema declared.
No examples provided.
verify_batch ~107
Submit many email addresses for asynchronous bulk verification. Returns a batchId immediately; the job runs in the background. Poll get_batch_status until status is 'completed', then call get_batch_results. Reserves 1 credit per address. Prefer verify_email for one-off checks.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Array of email addresses to verify. |
| name | string | – | Optional human-friendly label for the batch. |
| webhookUrl | string | – | Optional HTTPS URL to receive a signed batch.completed callback. |
No output schema declared.
No examples provided.
verify_email ~187
Verify whether a single email address is real and safe to send to, in real time. Returns a deliverability verdict (deliverable | undeliverable | risky | unknown), a 0–100 confidence score, a safeToSend flag, and signals (catch-all, disposable, role-based, free provider, likely typo). Spends 1 verification credit per call. Tip: addresses at the test.verifyany.email domain (e.g. deliverable@test.verifyany.email, undeliverable@…, risky@…, unknown@…) return canned results and cost 0 credits.
| Name | Type | Req | Description |
|---|---|---|---|
| catchAllDetection | boolean | – | Set false to skip catch-all detection. Default true. |
| string | yes | The email address to verify, e.g. name@example.com | |
| smtpProbe | boolean | – | Set false to skip the live SMTP mailbox probe (DNS-only). Default true. |
No output schema declared.
No examples provided.
How do I install the VerifyAnyEmail MCP server?
VerifyAnyEmail runs locally as an npm package, launched with npx -y verifyanyemail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · verifyanyemail-mcp
claude mcp add verifyanyemail-verifyanyemail-mcp -- npx -y verifyanyemail-mcp
What is the VerifyAnyEmail MCP server?
VerifyAnyEmail is an MCP server listed in the public MCP registry as io.github.verifyanyemail/verifyanyemail-mcp. Real-time email verification and deliverability diagnostics (MX, SPF, DKIM, DMARC). This page covers its npm package (verifyanyemail-mcp).
Is the VerifyAnyEmail MCP server safe to use?
VerifyAnyEmail scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the VerifyAnyEmail MCP server expose?
VerifyAnyEmail exposes 9 tools: verify_email, verify_batch, get_batch_status, get_batch_results, check_mx, and 4 more. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.
Is the VerifyAnyEmail MCP server still maintained?
VerifyAnyEmail is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the VerifyAnyEmail MCP server under?
VerifyAnyEmail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.