BillionVerify
REMOTE · MCP.BILLIONVERIFY.COM · 2 COMPONENTS
Email verification for AI agents: verify single or bulk emails, check credits and history.
Available components
Last scanned (20 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 608 tokens (~43/item across 14 items; 11 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 21 Oct 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.
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 · Probed https://mcp.billionverify.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=billionverify.com | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 2a20c389c9adb0190e65ba2ef13f3948 |
| SANs: billionverify.com, *.billionverify.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.billionverify.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| billionverify.com. | DS published | 2371 | 13 | Verified |
| mcp.billionverify.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="billionverify-mcp", resource_metadata="https://mcp.billionverify.com/.well-known/oauth-protected-resource", authorization_uri="https://billionverify.com", error="missing_token", error_description="missing bearer token"
Bearer realm="billionverify-mcp", resource_metadata="https://mcp.billionverify.com/.well-known/oauth-protected-resource", authorization_uri="https://billionverify.com", error="missing_token", error_description="missing bearer token"| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Protected resource metadata
| Document | https://mcp.billionverify.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.billionverify.com/mcp |
| Authorisation server | https://billionverify.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.billionverify.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.billionverify.com/mcp | HTTPS enforced | 301 | https://mcp.billionverify.com/mcp |
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 →
create_webhook ~47
Create a webhook endpoint for verification lifecycle notifications.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | yes | The webhook event types to subscribe to. |
| url | string | yes | The HTTPS endpoint that should receive webhook deliveries. |
No output schema declared.
No examples provided.
delete_webhook ~38
Permanently delete a webhook endpoint by identifier. The endpoint stops receiving notifications immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| webhook_id | string | yes | The webhook identifier to delete. |
No output schema declared.
No examples provided.
get_account_balance ~19
Get the current credit balance for the authenticated account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_download_url ~117
Get a signed download URL for completed results, or CSV content when filtered or rebuilt from history.
| Name | Type | Req | Description |
|---|---|---|---|
| catchall | boolean | – | Include results marked as catchall. |
| disposable | boolean | – | Include results marked as disposable. |
| invalid | boolean | – | Include results marked as invalid. |
| job_id | string | yes | 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. |
No output schema declared.
No examples provided.
get_task_status ~38
Get the current status of an asynchronous verification task.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task or job identifier returned by a previous verification request. |
No output schema declared.
No examples provided.
get_verification_history ~46
List verification history for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | The number of history records to return per page. |
| page | number | – | The page number to retrieve. |
No output schema declared.
No examples provided.
get_verification_stats ~31
Get aggregated verification statistics for the authenticated account.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | The reporting period to query. |
No output schema declared.
No examples provided.
health_check ~18
Check the health of the BillionVerify MCP server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks ~19
List all webhook endpoints configured for the authenticated account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_batch_emails ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_smtp | boolean | – | Whether to perform SMTP checks for each email address. |
| emails | array | yes | The email addresses to verify, with a minimum of 1 item and a maximum of 50 items. |
No output schema declared.
No examples provided.
verify_single_email ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| check_smtp | boolean | – | Whether to perform an SMTP check in addition to syntax and domain checks. |
| string | yes | The email address to verify. | |
| force_refresh | boolean | – | Whether to bypass cached results and force a fresh verification. |
No output schema declared.
No examples provided.
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.
remote · mcp.billionverify.com
claude mcp add --transport http billionverify-billionverify-mcp 'https://mcp.billionverify.com/mcp'
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.