MailVeri MCP (stdio)
Use MailVeri MCP over local stdio to verify email addresses, check account credits and inspect batch results. It requires a MailVeri API key and verification credits; email data goes to MailVeri.
Start with the current requirements ↓What it helps you do
Choose this when an agent needs to check a permitted email list and retrieve structured verification results. Tools cover single-address verification, balance lookup, batch submission, batch status, result download links and batch deletion. The batch tool documents a minimum of two addresses.
This listing covers stdio only. We do not provide or recommend a remote-server setup. The repository's other transport and some client configuration examples have known issues; this listing does not claim those issues are fixed.
Costs and access requirements
Verification uses account credits. Check mailveri_get_balance before starting and consult MailVeri pricing for current packs and terms. This listing does not promise a free allowance or a fixed rate per result. The README documents one single-email verification request per second. Queued batches remain subject to credits and service limits; queuing is not free unlimited verification.
Documented setup
Install uv using its official documentation, then obtain a MailVeri API key from the dashboard. Configure a client that launches local MCP processes:
Transport: stdio
Command: uvx
Arguments: --from git+https://github.com/mailveri/mailveri-mcp mailveri-mcp
Environment: MAILVERI_API_KEY=YOUR_MAILVERI_API_KEY
Put the key in the client's environment/secret settings. The executable uses stdio by default; your client starts it as a subprocess. We checked that source path but did not run it. Follow your client's current local-process configuration format rather than assuming every client accepts the same JSON file.
Check your first result
First confirm that the client can discover the tools and retrieve your balance. Only then, if you approve spending credits, verify an address you control or are authorized to process. Inspect the returned status; a validity classification is not a guarantee of future email delivery. For batches, keep the batch ID, check status and use its result link rather than resubmitting after an uncertain response.
If credits are exhausted, the documented response says “Not enough credits to verify email”. Check balance and service terms before topping up. Local stdio is only the client connection: the server still sends submitted email addresses to the MailVeri API. Batch deletion changes stored batch state. Project documentation.
What this listing covers
This is a free editorial listing based on public documentation and source inspection, not a security certification or a hands-on product review. Your AI client can have separate subscription or model usage charges. Check the linked product terms before connecting an account or running billable work.
Primary sources
Source-checked 2026-10-22. Published documentation, account availability and hands-on behavior are separate evidence. Examples and checklists here are editorial material.