io.github.mrfentmen/neverbounce-mcp
NPM · NEVERBOUNCE-MCP
NeverBounce email verification: single checks, bulk jobs and job results.
Available components
Last scanned (5 hours ago)
Scores higher than 35% 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 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 & 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 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 600 tokens (~50/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "nb_job_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +3
- Stability: unverified → 0.23 ▲ functional
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 49
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 5 Nov 2026 · Analysed npm/neverbounce-mcp@1.0.0
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 →
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 →
nb_account_info ~26
Raw NeverBounce account envelope: status, verification credits remaining, monthly usage and limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nb_account_usage ~23
Just the credit figures: credits remaining, monthly usage, monthly limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nb_job_create ~106
Create a bulk verification job from an email list file or folder that was already uploaded through the NeverBounce dashboard. auto_parse defaults to true; run_sample optionally verifies a sample first.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_parse | boolean | – | – |
| email_filename | string | – | file name uploaded via the dashboard |
| email_list_folder | string | – | folder name uploaded via the dashboard |
| job_name | string | – | – |
| run_sample | boolean | – | verify a small sample before the full run |
No output schema declared.
No examples provided.
nb_job_delete ~30
Delete a bulk verification job (destructive for that job only).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
nb_job_download ~41
Get the download payload for a finished job (file_format: json or csv).
| Name | Type | Req | Description |
|---|---|---|---|
| file_format | string | – | – |
| job_id | string | yes | – |
No output schema declared.
No examples provided.
nb_job_results ~56
Page through a finished job's per-email results: each row is an email with its verification result and flags.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | – |
| job_id | string | yes | – |
| start_page | integer | – | – |
No output schema declared.
No examples provided.
nb_job_results_summary ~74
One page of a job's results reduced to a per-result tally (valid/invalid/...) plus the query_info totals. For a quick health read of a finished job without pulling every row.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | – |
| job_id | string | yes | – |
| start_page | integer | – | – |
No output schema declared.
No examples provided.
nb_job_start ~27
Start a created (parsed) bulk verification job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
nb_job_status ~26
Poll the status of a bulk verification job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
nb_poe_confirm ~55
Confirm a Proof of Email (POE) token: pairs the transaction_id and token issued by the POE widget with the original single-check transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
| transaction_id | string | yes | – |
No output schema declared.
No examples provided.
nb_verify_email ~65
Verify ONE email address: result (valid / invalid / disposable / catchall / unknown), flags (free provider, role account, disposable host, spamtrap, bounce), and a suggested correction if any.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| timeout | integer | – | seconds |
No output schema declared.
No examples provided.
nb_verify_email_strict ~71
The same verification plus a verdict line computed here: safe (send), risky (catchall/disposable - judge first), dead (do not send), unknown (retry later). For deciding whether an agent should send at all.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| timeout | integer | – | seconds |
No output schema declared.
No examples provided.
How do I install the io.github.mrfentmen/neverbounce-mcp server?
io.github.mrfentmen/neverbounce-mcp runs locally as an npm package, launched with npx -y neverbounce-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 · neverbounce-mcp
claude mcp add mrfentmen-neverbounce-mcp -- npx -y neverbounce-mcp
What is the io.github.mrfentmen/neverbounce-mcp server?
io.github.mrfentmen/neverbounce-mcp is listed in the public MCP registry as io.github.mrfentmen/neverbounce-mcp. NeverBounce email verification: single checks, bulk jobs and job results. This page covers its npm package (neverbounce-mcp).
Is the io.github.mrfentmen/neverbounce-mcp server safe to use?
io.github.mrfentmen/neverbounce-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 io.github.mrfentmen/neverbounce-mcp server expose?
io.github.mrfentmen/neverbounce-mcp exposes 12 tools: nb_account_info, nb_account_usage, nb_verify_email, nb_verify_email_strict, nb_poe_confirm, and 7 more. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Is the io.github.mrfentmen/neverbounce-mcp server still maintained?
io.github.mrfentmen/neverbounce-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.mrfentmen/neverbounce-mcp server under?
io.github.mrfentmen/neverbounce-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.