# BillionVerify (remote · mcp.billionverify.com)

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

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.billionverify.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 608 tokens (~43/item across 14 items; 11 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the BillionVerify MCP server?

BillionVerify is a hosted endpoint at https://mcp.billionverify.com/mcp, so there is nothing to install locally. 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 --transport http billionverify-billionverify-mcp 'https://mcp.billionverify.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "billionverify-billionverify-mcp": {
      "url": "https://mcp.billionverify.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "billionverify-billionverify-mcp": {
      "type": "http",
      "url": "https://mcp.billionverify.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.billionverify-billionverify-mcp]
url = "https://mcp.billionverify.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "billionverify-billionverify-mcp": {
      "type": "remote",
      "url": "https://mcp.billionverify.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add billionverify-billionverify-mcp --url 'https://mcp.billionverify.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  billionverify-billionverify-mcp:
    url: "https://mcp.billionverify.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "billionverify-billionverify-mcp": {
      "Transport": "http",
      "Url": "https://mcp.billionverify.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add billionverify-billionverify-mcp -t streamable-http -u 'https://mcp.billionverify.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "billionverify-billionverify-mcp": {
      "type": "http",
      "url": "https://mcp.billionverify.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 91, +1)

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

### 2026-11-03 (score 90, +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-01 (score 89, +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-30 (score 88, +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-28 (score 87, +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-26 (score 86, +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-24 (score 85, +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-21 (score 84, +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.

## MCP tools (11)

### `create_webhook` (~47 tokens)

Create a webhook endpoint for verification lifecycle notifications.

Input parameters:

- `events` (array, required): The webhook event types to subscribe to.
- `url` (string, required): The HTTPS endpoint that should receive webhook deliveries.

### `delete_webhook` (~38 tokens)

Permanently delete a webhook endpoint by identifier. The endpoint stops receiving notifications immediately.

Input parameters:

- `webhook_id` (string, required): The webhook identifier to delete.

### `get_account_balance` (~19 tokens)

Get the current credit balance for the authenticated account.

### `get_download_url` (~117 tokens)

Get a signed download URL for completed results, or CSV content when filtered or rebuilt from history.

Input parameters:

- `catchall` (boolean): Include results marked as catchall.
- `disposable` (boolean): Include results marked as disposable.
- `invalid` (boolean): Include results marked as invalid.
- `job_id` (string, required): The completed verification job identifier.
- `role` (boolean): Include results marked as role-based addresses.
- `unknown` (boolean): Include results marked as unknown.
- `valid` (boolean): Include results marked as valid.

### `get_task_status` (~38 tokens)

Get the current status of an asynchronous verification task.

Input parameters:

- `task_id` (string, required): The task or job identifier returned by a previous verification request.

### `get_verification_history` (~46 tokens)

List verification history for the authenticated account.

Input parameters:

- `limit` (number): The number of history records to return per page.
- `page` (number): The page number to retrieve.

### `get_verification_stats` (~31 tokens)

Get aggregated verification statistics for the authenticated account.

Input parameters:

- `period` (string): The reporting period to query.

### `health_check` (~18 tokens)

Check the health of the BillionVerify MCP server.

### `list_webhooks` (~19 tokens)

List all webhook endpoints configured for the authenticated account.

### `verify_batch_emails` (~91 tokens)

Verify 1 to 50 email addresses in one request and return a verdict for each. Split longer lists into chunks of 50. Uses credits from the connected BillionVerify account.

Input parameters:

- `check_smtp` (boolean): Whether to perform SMTP checks for each email address.
- `emails` (array, required): The email addresses to verify, with a minimum of 1 item and a maximum of 50 items.

### `verify_single_email` (~96 tokens)

Verify whether a single email address can receive mail. Checks syntax and the domain's mail servers, and optionally the mailbox over SMTP. Uses credits from the connected BillionVerify account.

Input parameters:

- `check_smtp` (boolean): Whether to perform an SMTP check in addition to syntax and domain checks.
- `email` (string, required): The email address to verify.
- `force_refresh` (boolean): Whether to bypass cached results and force a fresh verification.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp#diagnostics

## Score history

- 2026-11-05: 91
- 2026-11-04: 90
- 2026-11-03: 90
- 2026-11-02: 89
- 2026-11-01: 89
- 2026-10-31: 88
- 2026-10-30: 88
- 2026-10-29: 87
- 2026-10-28: 87
- 2026-10-27: 86
- 2026-10-26: 86
- 2026-10-25: 85
- 2026-10-24: 85
- 2026-10-23: 84
- 2026-10-22: 84
- 2026-10-21: 84
- 2026-10-20: 83
- 2026-10-19: 83
- 2026-10-18: 82
- 2026-10-17: 82
- 2026-10-16: 81
- 2026-10-15: 81
- 2026-10-14: 80
- 2026-10-13: 80

## 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 hosted endpoint (https://mcp.billionverify.com/mcp).

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

BillionVerify scores 91 out of 100 on VerifyMCP. 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: create_webhook, delete_webhook, get_account_balance, get_download_url, get_task_status, and 6 more. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

### Does the BillionVerify MCP server require authentication?

Yes. BillionVerify asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### 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 did VerifyMCP test on the BillionVerify MCP server?

VerifyMCP ran 13 checks on BillionVerify, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.billionverify.com/mcp
- Repository: https://github.com/BillionVerify/billionverify-mcp
- Website: https://billionverify.com/
- Changelog RSS feed: https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/billionverify-billionverify-mcp/mcp