dev.emailiq/email-intelligence is an MCP server published by dev.emailiq, hosted at emailiq.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including analyze_email, analyze_email_batch.
Email intelligence MCP: MX/SPF/DKIM/DMARC, score, enrichment. x402 on emailiq.dev/mcp.
2 connections through 5 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Analyze one email: returns recommend first, then reasons, score, bounce_risk, syntax/MX/SPF/DKIM/DMARC, disposable, role, provider, enrichment. WHEN TO CALL: signup guard, disposable check, DMARC-before-outreach. WHEN NOT TO CALL: bulk lists >1 address (use analyze_email_batch); re-check of an address you already paid for (same payer cache is free). Price: /email/intelligence via x402 PAYMENT-SIGNATURE (canonical single price).
| Parameter | Type | Description |
|---|---|---|
| email * | string |
{
"name": "analyze_email",
"description": "Analyze one email: returns recommend first, then reasons, score, bounce_risk, syntax/MX/SPF/DKIM/DMARC, disposable, role, provider, enrichment. WHEN TO CALL: signup guard, disposable check, DMARC-before-outreach. WHEN NOT TO CALL: bulk lists >1 address (use analyze_email_batch); re-check of an address you already paid for (same payer cache is free). Price: /email/intelligence via x402 PAYMENT-SIGNATURE (canonical single price).",
"inputSchema": {
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}
}Analyze 2–25 emails in one call (same per-item schema as analyze_email; DNS/enrich cached within the batch; duplicates computed once). WHEN TO CALL: small multi-address checks from few domains. WHEN NOT TO CALL: single address (use analyze_email); lists >25 (split). Price: flat via x402 on /email/intelligence/batch. No free demo for batch.
| Parameter | Type | Description |
|---|---|---|
| emails * | array |
{
"name": "analyze_email_batch",
"description": "Analyze 2–25 emails in one call (same per-item schema as analyze_email; DNS/enrich cached within the batch; duplicates computed once). WHEN TO CALL: small multi-address checks from few domains. WHEN NOT TO CALL: single address (use analyze_email); lists >25 (split). Price: flat via x402 on /email/intelligence/batch. No free demo for batch.",
"inputSchema": {
"type": "object",
"required": [
"emails"
],
"properties": {
"emails": {
"type": "array",
"items": {
"type": "string"
}
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true
}
}Email intelligence for AI agents on https://emailiq.dev. Paid tools use x402 on Base: send PAYMENT-SIGNATURE on tools/call (analyze_email → /email/intelligence; analyze_email_batch → /email/intelligence/batch). Or prepaid X-EmailIQ-Credit-Key / marketplace X-EmailIQ-Gateway-Secret. Human demo remains at POST /demo/email — not via MCP. Same payer + same email within TTL skips settlement (X-EmailIQ-Cache).
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.