BillionVerify
NPM · BILLIONVERIFY-MCP · 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 76% of npm servers
Category Communication
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to BillionVerify/billionverify-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 678 tokens (~61/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 11 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 4 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.
- 2 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.
- 31 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.
- 29 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.
- 27 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.
- 25 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.
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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/billionverify-mcp@1.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | BillionVerify/billionverify-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/BillionVerify/billionverify-mcp/.github/workflows/publish.yml@refs/tags/v1.1.1 |
| Rekor log index | 3244886225 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:87eacb55230418b19780a08738231843aeed5f77a3cb6ec832eef52cfe6e00fe8485c25b66095c8a04b863e1a71d80b87b2b0d2066cf43fe9073d7292 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~66
Create a webhook to receive file verification completion notifications
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
| events | array | yes | Events to subscribe to |
| url | string | yes | HTTPS URL to receive webhook events |
No output schema declared.
No examples provided.
delete_webhook ~51
Delete a webhook by ID
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
| webhook_id | string | yes | The webhook ID to delete |
No output schema declared.
No examples provided.
get_account_balance ~43
Get the current credit balance for your BillionVerify account
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
No output schema declared.
No examples provided.
get_download_url ~124
Get the download URL for file verification results with optional status filters
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The job ID of the completed file verification |
| role | boolean | – | Include role-based emails |
| unknown | boolean | – | Include unknown emails |
| valid | boolean | – | Include valid emails |
No output schema declared.
No examples provided.
get_task_status ~61
Get the status and progress of an async file verification job
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
| task_id | string | yes | The job/task ID returned from a file upload |
No output schema declared.
No examples provided.
get_verification_history ~70
List verification history for your BillionVerify account
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_verification_stats ~55
Get aggregated verification statistics for your BillionVerify account
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
| period | string | – | The reporting period to query |
No output schema declared.
No examples provided.
health_check ~17
Check the BillionVerify MCP server health status
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_webhooks ~42
List all webhooks for your BillionVerify account
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
No output schema declared.
No examples provided.
verify_batch_emails ~72
Verify multiple email addresses (up to 50)
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
| check_smtp | boolean | – | Perform SMTP verification |
| emails | array | yes | List of email addresses to verify (max 50) |
No output schema declared.
No examples provided.
verify_single_email ~77
Verify a single email address
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | BillionVerify API key (optional if BILLIONVERIFY_API_KEY env is set) |
| check_smtp | boolean | – | Perform SMTP verification |
| string | yes | The email address to verify | |
| force_refresh | boolean | – | Bypass cache and force fresh verification |
No output schema declared.
No examples provided.
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.
npm · billionverify-mcp
claude mcp add billionverify-billionverify-mcp -- npx -y billionverify-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 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.