EmailIQ — Email Intelligence (MCP)

Instant email + domain intelligence for AI agents: syntax, MX, SPF, DKIM, DMARC, disposable detection, role accounts, provider, and a 0–100 score — one MCP tool call.

View on Apify Store | MCP endpoint

This Actor runs EmailIntelligence.analyze() in-process. It does not call https://emailiq.dev, and it has no x402 / wallet code. Billing is Apify pay-per-event only.

---

When to call

Persona	Scenario
Outbound / SDR agent	Before cold email, check that the address is syntactically valid, the domain accepts mail (MX), isn’t disposable, and the domain publishes SPF/DKIM/DMARC — then use the score as a gate.
Growth / list hygiene	Clean signup or CRM lists: drop role accounts (info@, support@), temp mailboxes, and low-score domains before a campaign.
Security / trust agent	Decide whether a contact or signup domain looks legitimate (auth records + provider) without running a full mailbox SMTP probe.

---

Example AI prompts

Copy-paste into Claude, Cursor, or any MCP client connected to this Actor:

1. Qualify before outreach
   Analyze the email jane.doe@acme.com with EmailIQ. Tell me if I should send a cold email: syntax, MX, SPF/DKIM/DMARC, disposable/role flags, provider, and score.

2. Filter a batch
   Run analyze_email on these addresses and return only those with score ≥ 80 and is_disposable=false: a@gmail.com, b@mailinator.com, support@stripe.com

3. Domain trust check
   Check founder@startup.io — does the domain have SPF, DKIM, and DMARC? What’s the mail provider and delivery score?

---

MCP tool: analyze_email

Input	Type	Required	Price
email	string	yes	$0.01 per successful call (email-analyzed)

Output fields:

Field	Type
email	string
valid_syntax	boolean
domain_exists	boolean | null
mx_records	string[] | null
spf_enabled	boolean | null
dkim_enabled	boolean | null
dmarc_enabled	boolean | null
is_disposable	boolean | null
is_role_account	boolean | null
mail_provider	string | null
score	integer (0–100)
processing_time_ms	number

Example output

{
  "email": "someone@microsoft.com",
  "valid_syntax": true,
  "domain_exists": true,
  "mx_records": ["microsoft-com.mail.protection.outlook.com"],
  "spf_enabled": true,
  "dkim_enabled": true,
  "dmarc_enabled": true,
  "is_disposable": false,
  "is_role_account": false,
  "mail_provider": "microsoft",
  "score": 100,
  "processing_time_ms": 65.825
}

dkim_enabled is a presence check on common selectors (default, google, selector1, selector2, k1) at {selector}._domainkey.<domain> — not cryptographic signature validation (same spirit as spf_enabled / dmarc_enabled). Note: some providers (e.g. consumer Gmail) only publish date-rotated selectors outside this common set, so dkim_enabled may be false even when the domain signs mail.

---

How EmailIQ compares

Capability	Pure email validators	Pure domain / DNS checkers	EmailIQ
Syntax + disposable + role	Yes	Rarely	Yes
MX / domain exists	Sometimes	Yes	Yes
SPF + DKIM + DMARC	Rarely	Often SPF/DMARC only	Yes (all three)
Per-address delivery score (0–100)	Sometimes	No	Yes
MCP / AI-agent native	Rare	Rare	Yes
Pay per call (no SaaS seat)	Varies	Varies	$0.01 / call

EmailIQ combines mailbox-oriented signals (syntax, disposable, role, score) with domain auth intelligence (MX + SPF/DKIM/DMARC + provider) in one tool — so agents don’t stitch a validator and a DNS checker together.

---

Pricing

Event	When	Price
email-analyzed	Once per successful analyze_email call	$0.01 USD

Configured in .actor/pay_per_event.json. Charged with Actor.charge(event_name="email-analyzed").

---

Connect (Standby MCP)

{
  "mcpServers": {
    "emailiq": {
      "url": "https://marcelocarlos--emailiq-mcp.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_API_TOKEN>"
      }
    }
  }
}

Transport: Streamable HTTP (webServerMcpPath: /mcp).

---

Local development

cd apify-actor
python3 -m venv .venv && .venv/bin/pip install -r requirements.txt

# Smoke-test intelligence only (no MCP server):
ACTOR_TEST_PAY_PER_EVENT=true .venv/bin/python scripts/local_analyze.py user@gmail.com

# Run MCP Actor locally (Standby-style HTTP on port 3000):
ACTOR_TEST_PAY_PER_EVENT=true APIFY_CONTAINER_PORT=3000 .venv/bin/python -m my_actor

---

Architecture notes

• Standby: one long-lived process serves many MCP requests until idle timeout; in-memory TTLCache (300s) is intentional and effective within that lifetime.
• aiodns: resolver is created lazily on the running asyncio loop; startup runs an early MX smoke test against gmail.com.
• Isolation: packaged under apify-actor/ so production EmailIQ (FastAPI + x402) is untouched.
• Score: syntax 25 + domain 15 + MX 20 + SPF/DKIM/DMARC 10 each + not-disposable 5 + not-role 5 (capped at 100).

---

Status

Status: Live on Apify Store. Published, pay-per-event billing active ($0.01 USD per successful analyze_email call).

---

SEO Keywords

email validation API, email intelligence MCP, SPF DMARC DKIM checker, disposable email detector, role account email detection, MX lookup API, email deliverability score, AI agent email validation, MCP email server, email reputation API, domain email authentication check, Apify email intelligence, pay per event email API, cold email list cleaning, B2B email quality score