SMTPing Email Verification
NPM · @SMTPING/MCP · 2 COMPONENTS
Verify email addresses, clean lists and check spamtrap, disposable, spambot and complainer lists.
Available components
Last scanned (23 hours ago)
Scores higher than 93% of npm servers
Category Marketing and SEO
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to smtping/smtping-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 294 tokens (~58/item across 5 items; 5 tools + 0 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 26 Oct 26 −4
- Malware scan: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: smtping/smtping-mcp security
- Package version: 1.0.0 → 1.0.1 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ 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/@smtping/mcp@1.0.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 | smtping/smtping-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/smtping/smtping-mcp/.github/workflows/publish.yml@refs/tags/v1.0.1 |
| Rekor log index | 3492940298 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9207af62bbe414b0c6a9a8f6e4f28814ac076564b6d3fdedbb218ce40f24667334cd41475280448d160a63dac15b106a45330e1a36cdd16e3e50348a0 |
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_threat Check a threat list ~56
Looks up one address in a single SMTPing threat list: spamtrap, disposable, spambot or complainer.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to check | |
| list | string | yes | Which list to check |
No output schema declared.
No examples provided.
get_bulk_job Get a bulk job ~42
Returns the progress of a SMTPing bulk job, and its results once it has succeeded.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by verify_list |
No output schema declared.
No examples provided.
get_credits Get remaining credits ~21
Returns the remaining SMTPing credit balance and plan. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_email Verify an email address ~70
Verifies one email address with SMTPing. Returns a status (valid, invalid, catch_all, spamtrap, disposable, etc.) and a band: safe (send), avoid (remove) or judgement (your call). Costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The email address to verify |
No output schema declared.
No examples provided.
verify_list Verify a list of email addresses ~105
Verifies a list of addresses as one SMTPing bulk job (deduplicated, up to 100,000). Waits up to 120 seconds; if the job is still running, returns a job_id to pass to get_bulk_job later. Costs 1 credit per unique address.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | Email addresses to verify |
| wait_seconds | integer | – | How long to wait for results. Default 120. Use 0 to only start the job. |
No output schema declared.
No examples provided.
How do I install the SMTPing Email Verification MCP server?
SMTPing Email Verification runs locally as an npm package, launched with npx -y @smtping/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 · @smtping/mcp
claude mcp add smtping-smtping-mcp -- npx -y @smtping/mcp
What is the SMTPing Email Verification MCP server?
SMTPing Email Verification is an MCP server listed in the public MCP registry as io.github.smtping/smtping-mcp. Verify email addresses, clean lists and check spamtrap, disposable, spambot and complainer lists. This page covers its npm package (@smtping/mcp).
Is the SMTPing Email Verification MCP server safe to use?
SMTPing Email Verification scores 89 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. 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 SMTPing Email Verification MCP server expose?
SMTPing Email Verification exposes 5 tools: verify_email, verify_list, get_bulk_job, check_threat, get_credits. Their descriptions and schemas cost roughly 294 tokens of context every time the server is loaded.
Is the SMTPing Email Verification MCP server still maintained?
SMTPing Email Verification 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 SMTPing Email Verification MCP server under?
SMTPing Email Verification declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.