Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-email-verifier

NPM · @MAMBALABSDEV/MCP-EMAIL-VERIFIER

Verify email lists on your own ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon key.

71 Trust /100

Last scanned (10 hours ago)

Scores higher than 40% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 & Transparency48
  • 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
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 383 tokens (~383/item across 1 items; 1 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 Management13
  • Stability observed for 4 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Changelog

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.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 69

    First indexed and scored.

Diagnostics

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/@mambalabsdev/mcp-email-verifier@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 →

MCP tools · 1 exposed · ~383 tokens

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 →

Tool Tokens
verify_emails ~383

Check whether email addresses will deliver, using the caller's own ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon account. Give emails (1 to 5,000 addresses) and provider (zerobounce by default). The service API key is read from this server's environment (EMAIL_VERIFIER_API_KEY), never from the tool arguments, and the service bills each check to the key owner. Returns one flat row per address: verdict (valid, invalid, catch_all, risky, or unknown), provider_status, provider_sub_status, is_role, is_free_email, is_disposable, did_you_mean, row_status, and error_reason. Addresses with broken syntax are not sent; repeats are checked once. If the key is missing the call is refused before any run starts. Bad input returns one free row whose error_reason starts with input_invalid. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per address the service answered valid, invalid, catch all, or risky.

NameTypeReqDescription
concurrencystring–How many addresses are checked at the same time, 1 to 20. Default 5. Lower it if the service plan has a tight rate limit.
emailstring–One more address, added to emails.
emailsarrayyesThe addresses to verify, 1 to 5,000 per run. A repeat of an address is verified and charged once.
max_charge_usdstring–Optional. The run stops before an actor charge that would pass this amount. The verification service bills separately.
providerstring–The service the key in EMAIL_VERIFIER_API_KEY belongs to: zerobounce, neverbounce, millionverifier, bounceban, or reoon. Default zerobounce.

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-email-verifier server?

com.mambabuilt/mcp-email-verifier runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-email-verifier. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mambalabsdev/mcp-email-verifier

# add to Claude Code
claude mcp add com-mambabuilt-mcp-email-verifier -- npx -y @mambalabsdev/mcp-email-verifier
Common questions

What is the com.mambabuilt/mcp-email-verifier server?

com.mambabuilt/mcp-email-verifier is listed in the public MCP registry as com.mambabuilt/mcp-email-verifier. Verify email lists on your own ZeroBounce, NeverBounce, MillionVerifier, BounceBan, or Reoon key. This page covers its npm package (@mambalabsdev/mcp-email-verifier).

Is the com.mambabuilt/mcp-email-verifier server safe to use?

com.mambabuilt/mcp-email-verifier scores 71 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 com.mambabuilt/mcp-email-verifier server expose?

com.mambabuilt/mcp-email-verifier exposes 1 tool: verify_emails. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-email-verifier server still maintained?

com.mambabuilt/mcp-email-verifier 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 com.mambabuilt/mcp-email-verifier server under?

com.mambabuilt/mcp-email-verifier declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.