Agents & MCP
Give your agents 40 tools and a credit budget
We ship a Model Context Protocol server, so Claude Desktop or any MCP client can verify, find, audit, and monitor email natively. Issue each agent its own credit wallet with a hard cap, and keep every spend confirm-first.
{
"mcpServers": {
"emaillistvalidation": {
"command": "npx",
"args": ["-y", "@emaillistvalidation/mcp"],
"env": {
"ELV_API_KEY": "your_api_key_here"
}
}
}
}Why MCP
Native tooling for autonomous workflows
Not a webhook bolt-on — a proper tool surface your agents can reason about, with the spend controls that make autonomy safe.
Connect any MCP client
We ship a Model Context Protocol server, so Claude Desktop, your IDE, or any MCP-compatible agent can drive Email List Validation natively. One config block and your assistant can verify, find, audit, and monitor.
40 tools, one registry
Every platform capability is exposed as a typed MCP tool — verification, the Finder, deliverability audits, domain and blacklist monitoring, DMARC analytics, and account operations — all from a single, versioned registry.
Agent credit wallets
Give an autonomous agent its own wallet with a hard spending limit. It can work independently up to that cap and no further — so automation never runs away with your credit balance.
Confirm-first on spend
Credit-consuming tool calls are gated behind explicit confirmation by default. Agents propose the spend; a human (or a pre-authorized wallet rule) approves it. Safe automation, not blind automation.
Quick start
Connect Claude Desktop in one config block
Add the server to your MCP client config, set your API key, and restart. The full tool registry shows up automatically — your assistant can now drive Email List Validation.
The MCP server authenticates with the same key as the REST API and draws from the same credit pool — no separate billing, no extra setup.
{
"mcpServers": {
"emaillistvalidation": {
"command": "npx",
"args": ["-y", "@emaillistvalidation/mcp"],
"env": {
"ELV_API_KEY": "your_api_key_here"
}
}
}
}The registry
40 tools, one versioned surface
Every platform capability is a typed MCP tool. A selection of what your agents can call:
Verification
- › verify_email()
- › verify_bulk()
- › get_job_status()
- › download_results()
Finder
- › find_email()
- › find_bulk()
Deliverability
- › audit_authentication()
- › test_inbox_placement()
- › score_spam()
- › check_reputation()
Monitoring
- › watch_domain()
- › check_blacklists()
- › list_alerts()
DMARC
- › ingest_dmarc()
- › summarize_dmarc()
- › list_sources()
Account
- › get_credit_balance()
- › list_credit_usage()
- › create_wallet()
Spend control
Autonomy with a hard ceiling
An agent with its own wallet can work unattended right up to its cap — and not a credit further. Combine wallet limits with confirm-first spend and you get automation you can actually leave running.
Prefer a guided, plain-English experience over wiring up a client? The in-app AI assistant runs on the same tool registry. Building a server-side integration instead? Start with the REST API.
Agents FAQ
Common questions
The Model Context Protocol is an open standard for connecting AI assistants to tools and data. Any MCP-compatible client works — including Claude Desktop — by adding our server to its configuration. Once connected, the assistant can call all 40 Email List Validation tools natively.
Each agent can be issued its own credit wallet with a hard cap. The agent draws only from that wallet and stops when it's exhausted, so an autonomous workflow can never spend beyond the limit you set. Credit-consuming actions are also confirm-first by default.
The MCP server authenticates with the same API key as the REST API, drawing from the same credit pool. Set ELV_API_KEY in your client's MCP server config and you're connected.
Wire email verification into your agents
Connect an MCP client, set a wallet limit, and let your agents verify, find, and monitor — safely. 100 free credits to start.
80,000+ users · 4.8/5 from 400+ reviews