billionverify-mcp
OfficialThis server lets AI assistants verify email addresses and manage BillionVerify account operations.
Verify a single email in real time (with optional SMTP checks and cache bypass)
Verify up to 50 email addresses in one batch request
Check account credit balance
View paginated verification history
Get aggregated verification statistics for 7d / 30d / 90d / 1y periods
Poll status of async file verification jobs
Generate download URLs for verification results with filters (valid, invalid, unknown, catch-all, disposable, role-based)
Create, list, and delete webhooks for file completion/failure events
Check server health status
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@billionverify-mcp verify email john@example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BillionVerify MCP Server — TypeScript
Connect any AI assistant to BillionVerify email verification via the Model Context Protocol. Built with the official MCP TypeScript SDK.
Option 1 — Hosted Server (No Installation)
Use BillionVerify's hosted MCP server. There is nothing to install and no API key to paste: you sign in with your BillionVerify account over OAuth, and the connection is tied to that account.
Server URL |
|
Transport | Streamable HTTP |
Authentication | OAuth 2.1 (sign in with your BillionVerify account) |
The hosted server does not accept API keys (
?api_key=,BV-API-KEYorAuthorization: Bearer <api key>are all rejected). If you want to use an API key, use Option 2.
Detailed step-by-step guide: docs/connect-chatgpt-claude.md.
ChatGPT (web)
Settings → Apps & Connectors → Advanced settings → turn on Developer mode.
Settings → Apps & Connectors → Create.
Name
BillionVerify, MCP server URLhttps://mcp.billionverify.com/mcp, authentication OAuth → create.Sign in to BillionVerify in the window that opens and approve access.
In a new chat, click + → Developer mode → enable BillionVerify.
Claude (claude.ai / Claude Desktop)
Customize → Connectors → + → Add custom connector.
Name
BillionVerify, URLhttps://mcp.billionverify.com/mcp→ Add (leave Advanced settings empty).Click Connect, sign in to BillionVerify and approve access.
In a chat, click + → Connectors and make sure BillionVerify is on.
Team / Enterprise: an Owner adds the connector under Organization settings → Connectors, then each member clicks Connect.
Claude Code
claude mcp add --transport http billionverify https://mcp.billionverify.com/mcpThen run /mcp inside Claude Code, select billionverify and finish the sign-in in your browser.
Cursor
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project), then click Connect next to the server in Settings → MCP:
{
"mcpServers": {
"billionverify": {
"url": "https://mcp.billionverify.com/mcp"
}
}
}Related MCP server: Tratto MCP Server
Option 2 — Self-Hosted (TypeScript / Node.js)
Run your own MCP server using this TypeScript implementation.
Prerequisites
Node.js 18+
Run via npx (no install)
BILLIONVERIFY_API_KEY=your_api_key npx billionverify-mcpClaude Desktop config (self-hosted)
{
"mcpServers": {
"billionverify": {
"command": "npx",
"args": ["-y", "billionverify-mcp"],
"env": {
"BILLIONVERIFY_API_KEY": "your_api_key_here"
}
}
}
}Install globally
npm install -g billionverify-mcp
billionverify-mcpInstall from source
git clone https://github.com/BillionVerify/billionverify-mcp.git
cd billionverify-mcp
npm install
npm run build
npm startEnvironment Variables
Variable | Description | Default |
| Your BillionVerify API key | — |
| API base URL override |
|
Available Tools
Tool | Description |
| Verify a single email address in real-time |
| Verify up to 50 emails in one request |
| Check your credit balance |
| List verification history (paginated) |
| Aggregated statistics for 7d / 30d / 90d / 1y |
| Poll the status of an async file verification job |
| Get download URL for results with status filters |
| Subscribe to file completion events |
| List all configured webhooks |
| Remove a webhook |
| Check server health |
License
MIT
Available Tools
11 toolscreate_webhookBInspect
Create a webhook to receive file verification completion notifications
Inputs: url (required), events (required), api_key.
delete_webhookBInspect
Delete a webhook by ID
Inputs: webhook_id (required), api_key.
get_account_balanceAInspect
Get the current credit balance for your BillionVerify account
Inputs: api_key.
get_download_urlBInspect
Get the download URL for file verification results with optional status filters
Inputs: job_id (required), role, valid, api_key, +4 more.
get_task_statusAInspect
Get the status and progress of an async file verification job
Inputs: task_id (required), api_key.
get_verification_historyCInspect
List verification history for your BillionVerify account
Inputs: page, limit, api_key.
get_verification_statsCInspect
Get aggregated verification statistics for your BillionVerify account
Inputs: period, api_key.
health_checkAInspect
Check the BillionVerify MCP server health status
Inputs: no named parameters.
list_webhooksBInspect
List all webhooks for your BillionVerify account
Inputs: api_key.
verify_batch_emailsCInspect
Verify multiple email addresses (up to 50)
Inputs: emails (required), api_key, check_smtp.
verify_single_emailBInspect
Verify a single email address
Inputs: email (required), api_key, check_smtp, force_refresh.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool targets a distinct action and resource: health, webhook CRUD, single vs batch verification, history vs stats, task status vs download URL, and account balance. The only close pair is single vs batch, but the descriptions clearly differentiate by count.
All tool names follow a consistent verb_noun snake_case pattern (health_check, create_webhook, verify_single_email, get_task_status). The verbs are predictable and the nouns are clear, with no style mixing.
11 tools is well within the ideal 3-15 range for a focused email verification service. Each tool has a clear role and none feel redundant or excessive.
The tool surface covers the main workflows: single/batch verification, history/stats, account balance, and webhook management. However, the presence of get_task_status and get_download_url implies file-based verification, yet there is no tool to initiate such a job, leaving a minor gap.
Maintenance
Related MCP Connectors
Email verification and domain intelligence for AI agents, including single and bulk email checks.
Email verification for AI agents: verify addresses and lists, check credits, manage integrations.
Verify and find B2B emails, search leads and run bulk jobs from your AI assistant.
Validate emails (MX, disposable, role, typo) and phone numbers, singly or in batches, for AI agents.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables AI agents to send emails and manage sending domains, templates, analytics, and content checks through the SendByte platform using the Model Context Protocol.1113 npmMIT
Tratto MCP Serverofficial
AlicenseAqualityDmaintenanceLets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.2MIT- AlicenseAqualityCmaintenanceEnables AI assistants to verify email deliverability and find business emails via the Verifox API, supporting single and bulk operations.6MIT
- AlicenseAqualityDmaintenanceEnables AI agents to verify email addresses, clean lists, run bulk verification jobs, and manage a Verifly account through natural language, without writing HTTP calls.158 npmMIT