IntoDNS.ai DNS & Email Security Scanner MCP Server

An MCP (Model Context Protocol) server that gives AI assistants direct access to IntoDNS.ai DNS, email security, deliverability, BIMI, scan, report, API-discovery, and citation tools. Its 40 documented tools cover check, report, email, scan.

People connecting email tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-21 · ★ 2 · #23 OF 75 MAINTAINED EMAIL · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install IntoDNS.ai DNS & Email Security Scanner

before you install - you'll need

Set INTODNS_SITE_URL, INTODNS_REQUEST_TIMEOUT_MS, INTODNS_HTTP_HOST, INTODNS_ALLOWED_HOSTS, INTODNS_ALLOWED_ORIGINS before connecting.

Claude Code

claude mcp add rosconl-intodns-mcp-server --transport http https://intodns.ai/api/mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "rosconl-intodns-mcp-server": {
      "url": "https://intodns.ai/api/mcp"
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://intodns.ai/api/mcp

transport: streamable-http

endpoint alive - responded to MCP initialize · probed 2026-08-25

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to intodns.ai

endpoint auth accepted our unauthenticated MCP initialize - no credentials needed to connect

license MIT - declared in the repository

npm package intodns-mcp - unscoped; check the name against the project README before installing

registry vendor namespace ai.intodns - domain-verified with the official MCP registry

03 · What IntoDNS.ai DNS & Email Security Scanner can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can read a previously created report snapshot by snapshot ID, fetch deep scan status/results, cancel a running deep scan, and parse a DMARC aggregate (RUA) XML report into structured sources, counts, and SPF/DKIM/DMARC results.

Capability map

Tools grouped from the project's README - what IntoDNS.ai DNS & Email Security Scanner lets an agent do.

Check

12 tools - e.g. DNS propagation across global, European, or American resolvers; TLSA/DANE check, defaulting to mail DANE on port 25; SPF parsing, recursive lookup graph, and flattening guidance

check_dns_propagation · check_tlsa_dane · check_spf · check_dmarc · check_bimi · check_mta_sts…

read & search

7 tools - e.g. A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV, PTR, DNSKEY, DS, RRSIG, NSEC, NSEC3 lookup; API, Redis/cache, and AI runtime health; Public scan/check counters

lookup_dns · get_health · get_stats · get_hall_of_fame · get_badge_link · read_llm_discovery…

Report

5 tools - e.g. Complete live DNS/email/security report as JSON or Markdown; Fixed Everything Report evidence snapshot with timestamp, content hash, and stable JSON/Markdown URLs; Read a previously created report…

get_everything_report · create_report_snapshot · get_report_snapshot · parse_dmarc_report · get_pdf_report_link

4 tools - e.g. Create an inbound test address for a deliverability test; Read email-test status/results; Poll and process a received email-test message

create_email_test · get_email_test · poll_email_test · analyze_raw_email

Deep

3 tools - e.g. Start Internet.nl deep scan (web, mail, or both); Fetch deep scan status/results; Cancel a running deep scan

start_deep_scan · get_deep_scan_status · cancel_deep_scan

Scan

1 tool - e.g. Fast IntoDNS.ai scan with grade, score, DNS/email/security results, issues, recommendations, and citation URLs

scan_domain

Nis2

1 tool - e.g. NIS2 Article 21.2 readiness score (0-100) mapped per measure, with evidence, critical gaps, and fix suggestions

nis2_quickscan

Validate

1 tool - e.g. DNSSEC chain, DS/DNSKEY and algorithm validation

validate_dnssec

Latest releases

v1.10.0 · 2026-08-21

Three tools that build DNS records, rather than only reading them. · generate_spf counts the ten-lookup limit while it builds. Exceeding it is a PermError, and receivers then treat the domain as having no SPF at all.…

v1.4.0 · 2026-05-27

Removed \run_public_scan\. It was functionally identical to \scan_domain\ (same backend, same output shape) and Glama's coherence rubric flagged the overlap. Tool surface drops from 37 to 36. · replace every…

v1.3.2 · 2026-05-27

Changes · Rewrote all 37 tool descriptions to fully cover Glama's TDQS rubric: behavior (side effects, auth, idempotency), parameter intent beyond schema, sibling differentiation, output shape, and explicit usage…

04 · Who maintains IntoDNS.ai DNS & Email Security Scanner

IntoDNS.ai DNS & Email Security Scanner is maintained by rosconl. It's the only MCP server we track from this author; the repo dates to Apr 2026.

05 · Facts

repository: github.com/rosconl/intodns-mcp-server
website: https://intodns.ai/mcp
category: email - ranked #23 of 75 actively-maintained email servers as of 2026-08-25.
release cadence: 4 releases in the last 90 days (latest 2026-08-21)
registry: ai.intodns/scanner (active, first published 2026-08-21)
packages: npm:intodns-mcp

06 · IntoDNS.ai DNS & Email Security Scanner FAQ

Is IntoDNS.ai DNS & Email Security Scanner still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-21 and it shipped 4 releases in the last 90 days. We re-verify nightly.

What can IntoDNS.ai DNS & Email Security Scanner do?

How do I install IntoDNS.ai DNS & Email Security Scanner?

Run `npx -y intodns-mcp`. The README documents 5 environment variables (INTODNS_SITE_URL, INTODNS_REQUEST_TIMEOUT_MS, INTODNS_HTTP_HOST…) to set first. Set INTODNS_SITE_URL, INTODNS_REQUEST_TIMEOUT_MS, INTODNS_HTTP_HOST, INTODNS_ALLOWED_HOSTS, INTODNS_ALLOWED_ORIGINS before connecting. You can also paste the ready-made client config above.

Does IntoDNS.ai DNS & Email Security Scanner require authentication?

No - the endpoint accepted our unauthenticated MCP initialize when probed on 2026-08-25; you can connect without credentials.

07 · Alternatives to IntoDNS.ai DNS & Email Security Scanner

Alternatives to IntoDNS.ai DNS & Email Security Scanner

Maintained email servers if IntoDNS.ai DNS & Email Security Scanner isn't the fit.

More email MCP servers · Forge MCP · Email Inbox API + Sending by Sendmux · AI · Sequenzy MCP · Abnormal Security MCP

More TypeScript MCP servers · Jira Alerts (JSM Operations) · Janee · Rootstock (RSK) MCP Server · Guardian · Runapi MCP · see all