billionverify-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BILLIONVERIFY_API_KEY | Yes | Your BillionVerify API key | |
| BILLIONVERIFY_API_URL | No | API base URL override | https://api.billionverify.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check the BillionVerify MCP server health status |
| verify_single_emailB | Verify a single email address |
| verify_batch_emailsC | Verify multiple email addresses (up to 50) |
| get_account_balanceA | Get the current credit balance for your BillionVerify account |
| get_verification_historyC | List verification history for your BillionVerify account |
| get_verification_statsC | Get aggregated verification statistics for your BillionVerify account |
| get_task_statusA | Get the status and progress of an async file verification job |
| get_download_urlB | Get the download URL for file verification results with optional status filters |
| create_webhookB | Create a webhook to receive file verification completion notifications |
| list_webhooksB | List all webhooks for your BillionVerify account |
| delete_webhookB | Delete a webhook by ID |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.