Mail7 Email Validation
NPM · MAIL7-MCP
Verify email addresses, clean lists, and audit a domain SPF, DKIM, DMARC and MX setup.
Available components
Last scanned (19 hours ago)
Scores higher than 98% of npm servers
Category Security
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dvlop/mail7-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 83 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 560 tokens (~140/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 11 Oct 26 −16
- Malware scan: pass → unverified ▼ security
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/mail7-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dvlop/mail7-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dvlop/mail7-mcp/.github/workflows/publish-npm.yml@refs/heads/main |
| Rekor log index | 2443470715 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:18fbbf04e7dcabf9cc03dac9a842795917c03af3b0a3da58e59635a180bdda76ec5d03818dec191d1e53b582abeb64c974756b8633af7bd200b9344ed |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| 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_domain Check a domain mail configuration ~179
Audit a domain's email setup in one call: MX records, SPF, DKIM, DMARC, MTA-STS, TLS-RPT, DNSSEC and BIMI, graded A-F with a fix for every problem found. Use this to answer "can this domain send and receive mail" or "why do our messages land in spam". Takes a domain (example.com), not an email address. The default answer summarises every section; pass `section` to get the full records and findings of one of them.
| Name | Type | Req | Description |
|---|---|---|---|
| dkim_selector | string | – | Optional DKIM selector to look up, e.g. "google" or "s1". Omit if unknown. |
| domain | string | yes | Domain to check, e.g. example.com |
| section | string | – | Drill into a single section instead of the whole summary |
No output schema declared.
No examples provided.
check_spf Check a domain SPF record ~67
Fetch and analyse the SPF record of a domain: the raw record, its mechanisms, lookup count and common misconfigurations. Use check_domain instead when the question is about overall deliverability rather than SPF specifically.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check, e.g. example.com |
No output schema declared.
No examples provided.
validate_email Validate one email address ~128
Check whether a single email address is deliverable: syntax, domain MX records, disposable-domain database and a live SMTP mailbox probe. Status is one of "Valid", "Not Valid", "Unknown". Unknown means the mailbox could NOT be checked (catch-all domain, greylisting, blocked SMTP port) - it is NOT a bad address. Never delete, reject or report Unknown addresses as invalid; present them separately and let the user decide. Use validate_emails instead when you have more than one address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to check, e.g. user@example.com |
| Name | Type | Req | Description |
|---|---|---|---|
| details | string|null | – | – |
| string | yes | – | |
| formatValid | boolean | yes | – |
| is_disposable | boolean|null | – | – |
| mxValid | boolean | yes | – |
| smtpValid | boolean | yes | – |
| status | string | yes | – |
| valid | boolean|null | yes | true = deliverable, false = does not exist, null = Unknown |
No examples provided.
validate_emails Validate a list of email addresses ~186
Check up to 50 email addresses in one call and get a per-address verdict plus a summary. Status is one of "Valid", "Not Valid", "Unknown". Unknown means the mailbox could NOT be checked (catch-all domain, greylisting, blocked SMTP port) - it is NOT a bad address. Never delete, reject or report Unknown addresses as invalid; present them separately and let the user decide. Requires MAIL7_API_KEY (anonymous callers get a 25-address free sample only). Each address takes a few seconds of real SMTP work, so this call is slow by nature: for a longer list, split it and call this tool repeatedly with the next 50 addresses. Never run two calls in parallel - the API serialises one bulk job per client and the second call fails.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | The addresses to check, at most 50 per call |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| partial | boolean | yes | true when the list was cut short (free anonymous sample or a limit was hit) |
| results | array | yes | – |
| summary | object | yes | – |
No examples provided.
How do I install the Mail7 Email Validation MCP server?
Mail7 Email Validation runs locally as an npm package, launched with npx -y mail7-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 · mail7-mcp
claude mcp add net-mail7-email-validation -- npx -y mail7-mcp
What is the Mail7 Email Validation MCP server?
Mail7 Email Validation is an MCP server listed in the public MCP registry as net.mail7/email-validation. Verify email addresses, clean lists, and audit a domain SPF, DKIM, DMARC and MX setup. This page covers its npm package (mail7-mcp).
Is the Mail7 Email Validation MCP server safe to use?
Mail7 Email Validation scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mail7 Email Validation MCP server expose?
Mail7 Email Validation exposes 4 tools: validate_email, validate_emails, check_domain, check_spf. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.
Is the Mail7 Email Validation MCP server still maintained?
Mail7 Email Validation 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 Mail7 Email Validation MCP server under?
Mail7 Email Validation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.