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_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 9 tools
Each tool has a clearly distinct purpose: email verification (single/batch), webhook management (create, delete, list), account balance, result download, task status, and health check. The only potential overlap is between verify_single_email and verify_batch_emails, but they are differentiated by the number of emails, making them unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_webhook, get_account_balance). There are no deviations or mixed conventions, ensuring predictability.
With 9 tools, the server is well-scoped for its purpose: email verification plus supporting account and webhook management. The count is neither too few nor excessive, covering essential operations without redundancy.
The tool set covers core CRUD for webhooks, single and batch verification, result retrieval (via download URL and status), and account balance. Minor gaps include the absence of a webhook update tool and a way to cancel a verification job, but these are not critical for typical workflows.