Email Address Validator (Syntax, MX, Disposable & Role Checks)
omnial/email-validate
Checks one or more email addresses (comma-separated, up to 25 per call) for RFC syntax validity, a live MX record lookup, disposable/throwaway domain membership, and role-account or free-provider status, returning a per-address verdict with the reasons behind it.
Price
$0.0451 per call
You pay the price shown. If a call turns out to cost more than its quote, you pay the actual price, capped at twice the quote. No monthly minimum. Top-ups start at $0.50.
Data source
Data from public DNS records.
Use it
Five steps: search, inspect, learn, run, settle. No per-tool setup; your agent reaches this tool through the meta-tools it already has.
Connect once and your AI can find and run this tool, and any other it needs.
// 1. search: find the tool
omnial_search({ query: "what you need" })
// 2. inspect: price and input schema
omnial_inspect({ tool: "omnial/email-validate" })
// 3. learn: read the usage guide at runtime
omnial_learn({ tool: "omnial/email-validate" })
// 4. run: price the exact call first, then run it
omnial_execute({ tool: "omnial/email-validate", input: { /* see input_schema */ }, dry_run: true })
omnial_execute({ tool: "omnial/email-validate", input: { /* ... */ } })
// 5. settle: the call is charged when it finishes, nothing to doNot connected yet? Point your MCP client at https://mcp.eden-engine.com/mcp, then copy a config for your client.
Pricing
Every charge this tool can incur.
| Charge | Price |
|---|---|
Per call | $0.0451 |
- Updated
- Oct 25, 2026
Input and output schemas
Input schema
{
"type": "object",
"required": [
"emails"
],
"properties": {
"emails": {
"type": "string",
"description": "comma-separated email addresses, up to 25 per call (a single address works too)"
}
},
"additionalProperties": false
}Output schema
{
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "Number of addresses validated in this call."
},
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"type": {
"type": "string",
"description": "Typically the literal string 'email_validation'."
},
"email": {
"type": "string",
"description": "The address as submitted, echoed back exactly as given in the input."
},
"domain": {
"type": "string",
"description": "The portion of the address after the '@'."
},
"mxFound": {
"type": "boolean",
"description": "True when the domain has at least one resolvable MX record."
},
"reasons": {
"type": "array",
"items": {
"type": "string"
},
"description": "Human-readable reason strings behind the verdict."
},
"verdict": {
"type": "string",
"description": "Confirmed as 'risky' in testing (a role account and a disposable domain). The endpoint's own documentation also describes 'ok' and 'invalid' verdicts, but neither has been seen in a real call -- treat those two as documented-but-unconfirmed rather than guaranteed values."
},
"localPart": {
"type": "string",
"description": "The portion of the address before the '@'."
},
"mxRecords": {
"type": "array",
"items": {
"type": "object",
"properties": {
"host": {
"type": "string"
},
"priority": {
"type": "number"
}
},
"additionalProperties": true
},
"description": "The domain's mail-exchange hosts. Empty when mxFound is false."
},
"normalized": {
"type": "string",
"description": "The address after normalization -- typically identical to `email` (no case-folding or alias-stripping difference has been seen)."
},
"roleAccount": {
"type": "boolean",
"description": "True for a generic mailbox local part (e.g. 'support', 'sales', 'info') rather than an individual's own address."
},
"syntaxValid": {
"type": "boolean"
},
"freeProvider": {
"type": "boolean",
"description": "True when the domain is a known free consumer email provider."
},
"disposableDomain": {
"type": "boolean",
"description": "True when the domain matches a known throwaway/disposable list."
}
},
"additionalProperties": true
}
}
},
"description": "The validation batch.",
"additionalProperties": true
}