MailProbe
Verify email addresses in real time: deliverability, disposable and role addresses, typo fixes.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"mailprobe": {
"url": "https://mailprobe.dev/mcp"
}
}
}Remote endpoints
https://mailprobe.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢verify_emails(emails)
Checks whether email addresses exist and can receive mail, in real time and without sending anything. Returns one result per address, in input order. Act on `status`: `valid` is safe to send, `invalid` must not be used, `risky` is accepted but uncertain (catch-all domain, role or disposable address, provider that blocks probing) and `unknown` could not be determined. `score` is a 0-100 confidence value, `reason` explains a verdict that is not plainly deliverable and `did_you_mean` suggests a fix for a likely typo. One credit per address actually probed: duplicates and malformed addresses are free. At most 20 addresses per call: split a longer list into several calls.
Input Schema
{
"type": "object",
"properties": {
"emails": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 1,
"maxItems": 20,
"description": "Email addresses to verify, 1 to 20."
}
},
"required": [
"emails"
],
"additionalProperties": false
}🟢get_credits
Returns the number of verification credits left on the MailProbe account that owns the API key. Reading the balance uses no credit.
Input Schema
{
"type": "object",
"additionalProperties": false
}Community
Evidence