# com.mambabuilt/mcp-email-verifier (npm · @mambalabsdev/mcp-email-verifier)

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

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@mambalabsdev/mcp-email-verifier`: 56/100 (this document), [markdown](https://verifymcp.io/servers/com-mambabuilt-mcp-email-verifier/mambalabsdev-mcp-email-verifier.md), [page](https://verifymcp.io/servers/com-mambabuilt-mcp-email-verifier/mambalabsdev-mcp-email-verifier)

## Channel facts

- Registry: `npm`
- Package: `@mambalabsdev/mcp-email-verifier`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 48/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add com-mambabuilt-mcp-email-verifier -- npx -y @mambalabsdev/mcp-email-verifier
```

### Cursor

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-email-verifier": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-email-verifier"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mambabuilt-mcp-email-verifier": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-email-verifier"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mambabuilt-mcp-email-verifier -- npx -y @mambalabsdev/mcp-email-verifier
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-email-verifier": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-email-verifier"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mambabuilt-mcp-email-verifier --command npx --arg -y --arg @mambalabsdev/mcp-email-verifier
```

### Hermes

```yaml
mcp_servers:
  com-mambabuilt-mcp-email-verifier:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-email-verifier"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mambabuilt-mcp-email-verifier": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mambalabsdev/mcp-email-verifier"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mambabuilt-mcp-email-verifier -t stdio -c npx -a -y @mambalabsdev/mcp-email-verifier
```

### Other

```json
{
  "mcpServers": {
    "com-mambabuilt-mcp-email-verifier": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-email-verifier"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 56, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 1.0.0 → 1.0.1

### 2026-11-03 (score 70, +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.

### 2026-11-01 (score 69)

First indexed and scored.

## MCP tools (1)

### `verify_emails` (~383 tokens)

Verify email addresses on your own verification key

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.

Input parameters:

- `concurrency` (string): 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.
- `email` (string): One more address, added to emails.
- `emails` (array, required): The addresses to verify, 1 to 5,000 per run. A repeat of an address is verified and charged once.
- `max_charge_usd` (string): Optional. The run stops before an actor charge that would pass this amount. The verification service bills separately.
- `provider` (string): The service the key in EMAIL_VERIFIER_API_KEY belongs to: zerobounce, neverbounce, millionverifier, bounceban, or reoon. Default zerobounce.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mambabuilt-mcp-email-verifier/mambalabsdev-mcp-email-verifier#diagnostics

## Score history

- 2026-11-05: 56
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69

## 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 56 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.

## Links

- npm package: https://www.npmjs.com/package/@mambalabsdev/mcp-email-verifier
- Socket report: https://socket.dev/npm/package/@mambalabsdev/mcp-email-verifier
- Repository: https://github.com/mambalabsdev/mcp-email-verifier
- Changelog RSS feed: https://verifymcp.io/servers/com-mambabuilt-mcp-email-verifier/mambalabsdev-mcp-email-verifier.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mambabuilt-mcp-email-verifier/mambalabsdev-mcp-email-verifier.json
- HTML version of this page: https://verifymcp.io/servers/com-mambabuilt-mcp-email-verifier/mambalabsdev-mcp-email-verifier