Email verification for AI agents: verify single or bulk emails, check credits and history.
Connect any AI assistant to BillionVerify email verification via the Model Context Protocol. Built with the official MCP TypeScript SDK.
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 | https://mcp.billionverify.com/mcp |
| 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.
BillionVerify, MCP server URL https://mcp.billionverify.com/mcp, authentication OAuth → create.BillionVerify, URL https://mcp.billionverify.com/mcp → Add (leave Advanced settings empty).Team / Enterprise: an Owner adds the connector under Organization settings → Connectors, then each member clicks Connect.
claude mcp add --transport http billionverify https://mcp.billionverify.com/mcp
Then run /mcp inside Claude Code, select billionverify and finish the sign-in in your browser.
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"
}
}
}
Run your own MCP server using this TypeScript implementation.
BILLIONVERIFY_API_KEY=your_api_key npx billionverify-mcp
{
"mcpServers": {
"billionverify": {
"command": "npx",
"args": ["-y", "billionverify-mcp"],
"env": {
"BILLIONVERIFY_API_KEY": "your_api_key_here"
}
}
}
}
npm install -g billionverify-mcp
billionverify-mcp
git clone https://github.com/BillionVerify/billionverify-mcp.git
cd billionverify-mcp
npm install
npm run build
npm start
| Variable | Description | Default |
|---|---|---|
BILLIONVERIFY_API_KEY | Your BillionVerify API key | — |
BILLIONVERIFY_API_URL | API base URL override | https://api.billionverify.com |
| Tool | Description |
|---|---|
verify_single_email | Verify a single email address in real-time |
verify_batch_emails | Verify up to 50 emails in one request |
get_account_balance | Check your credit balance |
get_verification_history | List verification history (paginated) |
get_verification_stats | Aggregated statistics for 7d / 30d / 90d / 1y |
get_task_status | Poll the status of an async file verification job |
get_download_url | Get download URL for results with status filters |
create_webhook | Subscribe to file completion events |
list_webhooks | List all configured webhooks |
delete_webhook | Remove a webhook |
health_check | Check server health |
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y billionverify-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-billionverify-billionverify-mcp": {
"command": "npx",
"args": [
"-y",
"billionverify-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencebillionverify-mcpnpmBillionVerify works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.