Skip to content

email-intelligence MCP server

dev.emailiq/email-intelligenceemailiq.devstreamable-httpv0.2.1Scanned

Email intelligence MCP: MX/SPF/DKIM/DMARC, score, enrichment. x402 on emailiq.dev/mcp.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the email-intelligence MCP server can do

The email-intelligence MCP server is published by emailiq.dev, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools read private data (analyze_email and analyze_email_batch); 2 tools bring in text other people can write (analyze_email and analyze_email_batch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.2.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • analyze_emailAnalyze one email: returns recommend first, then reasons, score, bounce_risk, syntax/MX/SPF/DKIM/DMARC, disposable, role, provider, enrichment.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "analyze_email" says "analyze": a word for reading.

    What it can reach

    • private-dataThe name "analyze_email" says "analyze" and "email": it reads mail.
    • private-dataThe description's first sentence says "analyze" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "analyze_email" says "analyze" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "analyze" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote 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).

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • analyze_email_batchAnalyze 2–25 emails in one call (same per-item schema as analyze_email; DNS/enrich cached within the batch; duplicates computed once).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "analyze_email_batch" says "analyze": a word for reading.

    What it can reach

    • private-dataThe name "analyze_email_batch" says "analyze" and "email": it reads mail.
    • private-dataThe description's first sentence says "analyze" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "analyze_email_batch" says "analyze" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "analyze" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:52 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.2.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http email-intelligence https://emailiq.dev/mcp/
claude mcp add --transport http email-intelligence https://emailiq.dev/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__email-intelligence__analyze_email",
      "mcp__email-intelligence__analyze_email_batch"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as email-intelligence. Review it before you use it.

Capability tags behind 2 rules
  • mcp__email-intelligence__analyze_email private-data, untrusted-input
  • mcp__email-intelligence__analyze_email_batch private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.emailiq/email-intelligence/verify?hash=74b98cf365eb006aff79e7b221d17a79a3bbc503da972f51ff320d480322feb5" | jq -e '.changed == false'

Pinned hash 74b98cf365eb, from Nov 8, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.emailiq/email-intelligence/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.emailiq/email-intelligence
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.emailiq/email-intelligence.svg)](https://radar.anlyon.com/servers/dev.emailiq/email-intelligence)

Source: MCP Registry · repository. Synced Oct 22, 2026, 11:17 UTC.

email-intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the email-intelligence MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the email-intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the email-intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the email-intelligence MCP server have?

2 tools: 2 read. analyze_email and analyze_email_batch.

Does the email-intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the email-intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the email-intelligence MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.