# BillionVerify (npm · billionverify-mcp)

Email verification for AI agents: verify single or bulk emails, check credits and history.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.billionverify.com`: 91/100, [markdown](https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp.md), [page](https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp)
- npm · `billionverify-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp.md), [page](https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp)

## Channel facts

- Registry: `npm`
- Package: `billionverify-mcp`
- Version: `1.1.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**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to BillionVerify/billionverify-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 22 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 678 tokens (~61/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_webhook" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 11 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 BillionVerify MCP server?

BillionVerify runs locally as an npm package, launched with npx -y billionverify-mcp. 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 billionverify-billionverify-mcp -- npx -y billionverify-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "billionverify-billionverify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "billionverify-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "billionverify-billionverify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "billionverify-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add billionverify-billionverify-mcp -- npx -y billionverify-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "billionverify-billionverify-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "billionverify-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add billionverify-billionverify-mcp --command npx --arg -y --arg billionverify-mcp
```

### Hermes

```yaml
mcp_servers:
  billionverify-billionverify-mcp:
    command: "npx"
    args: ["-y", "billionverify-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "billionverify-billionverify-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "billionverify-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add billionverify-billionverify-mcp -t stdio -c npx -a -y billionverify-mcp
```

### Other

```json
{
  "mcpServers": {
    "billionverify-billionverify-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "billionverify-mcp"
      ]
    }
  }
}
```

## 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-04 (score 83, +1)

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

### 2026-11-02 (score 82, +1)

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

### 2026-10-31 (score 81, +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.

### 2026-10-29 (score 80, +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.

### 2026-10-27 (score 79, +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.

### 2026-10-25 (score 78, +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.

### 2026-10-24 (score 77, −5)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-22 (score 82, +4)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (11)

### `health_check` (~17 tokens)

Check the BillionVerify MCP server health status

### `verify_single_email` (~77 tokens)

Verify a single email address

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `check_smtp` (boolean): Perform SMTP verification
- `email` (string, required): The email address to verify
- `force_refresh` (boolean): Bypass cache and force fresh verification

### `verify_batch_emails` (~72 tokens)

Verify multiple email addresses (up to 50)

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `check_smtp` (boolean): Perform SMTP verification
- `emails` (array, required): List of email addresses to verify (max 50)

### `get_account_balance` (~43 tokens)

Get the current credit balance for your BillionVerify account

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)

### `get_verification_history` (~70 tokens)

List verification history for your BillionVerify account

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `limit` (integer): The number of history records to return per page
- `page` (integer): The page number to retrieve

### `get_verification_stats` (~55 tokens)

Get aggregated verification statistics for your BillionVerify account

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `period` (string): The reporting period to query

### `get_task_status` (~61 tokens)

Get the status and progress of an async file verification job

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `task_id` (string, required): The job/task ID returned from a file upload

### `get_download_url` (~124 tokens)

Get the download URL for file verification results with optional status filters

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `catchall` (boolean): Include catch-all emails
- `disposable` (boolean): Include disposable emails
- `invalid` (boolean): Include invalid emails
- `job_id` (string, required): The job ID of the completed file verification
- `role` (boolean): Include role-based emails
- `unknown` (boolean): Include unknown emails
- `valid` (boolean): Include valid emails

### `create_webhook` (~66 tokens)

Create a webhook to receive file verification completion notifications

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `events` (array, required): Events to subscribe to
- `url` (string, required): HTTPS URL to receive webhook events

### `list_webhooks` (~42 tokens)

List all webhooks for your BillionVerify account

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)

### `delete_webhook` (~51 tokens)

Delete a webhook by ID

Input parameters:

- `api_key` (string): BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set)
- `webhook_id` (string, required): The webhook ID to delete

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 82
- 2026-10-22: 82
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 49

## Common questions

### What is the BillionVerify MCP server?

BillionVerify is an MCP server listed in the public MCP registry as io.github.BillionVerify/billionverify-mcp. Email verification for AI agents: verify single or bulk emails, check credits and history. This page covers its npm package (billionverify-mcp).

### Is the BillionVerify MCP server safe to use?

BillionVerify scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 BillionVerify MCP server expose?

BillionVerify exposes 11 tools: health_check, verify_single_email, verify_batch_emails, get_account_balance, get_verification_history, and 6 more. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.

### Is the BillionVerify MCP server still maintained?

BillionVerify 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 BillionVerify MCP server under?

BillionVerify declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the BillionVerify MCP server?

VerifyMCP ran 16 checks on BillionVerify, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/billionverify-mcp
- Socket report: https://socket.dev/npm/package/billionverify-mcp
- Repository: https://github.com/BillionVerify/billionverify-mcp
- Website: https://billionverify.com/
- Changelog RSS feed: https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp.json
- HTML version of this page: https://verifymcp.io/servers/billionverify-billionverify-mcp/billionverify-mcp