MailProbe
NPM · MAILPROBE-MCP · 2 COMPONENTS
Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.
Available components
Last scanned (21 hours ago)
Scores higher than 95% of npm servers
Category CRM and Sales
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MailProbe/mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 290 tokens (~145/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- The attested source repository moved: jamalofski/mailprobe-mcp → MailProbe/mcp security
- Package version: 1.1.1 → 1.1.2 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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/mailprobe-mcp@1.1.2
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 | MailProbe/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MailProbe/mcp/.github/workflows/publish.yml@refs/tags/1.1.2 |
| Rekor log index | 3638315307 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b47217b7a374d73be4d53116f134755b6bb125a0f56e09cd0c3aa190aefe7bba9a64fc3d23cf25a5aa68b1de990ca457e38c7215755ac7da2d9e77172 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
get_credits Get Credit Balance ~34
Returns the number of verification credits left on the MailProbe account that owns the API key. Reading the balance uses no credit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_emails Verify Email Addresses ~176
Checks whether email addresses exist and can receive mail, in real time and without sending anything. Returns one result per address, in input order. Act on `status`: `valid` is safe to send, `invalid` must not be used, `risky` is accepted but uncertain (catch-all domain, role or disposable address, provider that blocks probing) and `unknown` could not be determined. `score` is a 0-100 confidence value, `reason` explains a verdict that is not plainly deliverable and `did_you_mean` suggests a fix for a likely typo. One credit per address actually probed: duplicates and malformed addresses are free. At most 20 addresses per call: split a longer list into several calls.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify, 1 to 20. |
No output schema declared.
No examples provided.
How do I install the MailProbe MCP server?
MailProbe runs locally as an npm package, launched with npx -y mailprobe-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 · mailprobe-mcp
claude mcp add dev-mailprobe-mailprobe -- npx -y mailprobe-mcp
What is the MailProbe MCP server?
MailProbe is an MCP server listed in the public MCP registry as dev.mailprobe/mailprobe. Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes. This page covers its npm package (mailprobe-mcp).
Is the MailProbe MCP server safe to use?
MailProbe scores 92 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 MailProbe MCP server expose?
MailProbe exposes 2 tools: verify_emails, get_credits. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.
Is the MailProbe MCP server still maintained?
MailProbe 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 MailProbe MCP server under?
MailProbe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.