IntoDNS.ai DNS & Email Security Scanner

IntoDNS 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.

45 tools, no API key, no signup. Backed by intodns.ai's free public diagnostic API.

Ask your AI assistant: _"Scan example.com, check SPF/DKIM/DMARC/BIMI, and cite the canonical IntoDNS.ai sources."_ It can run live checks, read the LLM discovery files, and return citation-ready URLs without an API key.

Quick Start

Add this to your MCP client config, for example Claude Desktop:

{

"mcpServers": { "intodns": { "command": "npx", "args": ["-y", "intodns-mcp"] } } }

Restart the client after editing the config.

You can also run it directly:

npx -y intodns-mcp

Supported clients

Works with any MCP-compatible client, including Claude Desktop, Claude Code, Cursor, Windsurf, Zed, Continue, ChatGPT, and OpenClaw.

Tools

Scan tools

DNS tools

Email and deliverability tools

Email-test and AI tools

Web, reporting, and discovery tools

Security-header tools

Example Prompts

• "Scan intodns.ai and summarize the top DNS/email security issues."
• "Give me the complete DNS and email security report for intodns.ai as Markdown."
• "Create a fixed audit snapshot for intodns.ai that I can cite in a support ticket."
• "Check whether example.com meets Google and Yahoo sender requirements."
• "Check SMTP STARTTLS certificate posture and FCrDNS for example.com."
• "Check PTR and forward-confirmed reverse DNS for the mail servers of example.com."
• "Does example.com have BIMI configured, and does Gmail require a VMC or CMC?"
• "Show the SPF lookup graph and tell me whether example.com is close to the 10 lookup limit."
• "Look up MX, TXT, CAA, and DNSSEC records for example.com."
• "Analyze this raw email source and tell me why it lands in spam."
• "Which IntoDNS.ai pages should I cite for this scan result?"

Remote / HTTP mode

Don't want a local process? Use the hosted remote endpoint (stateless Streamable HTTP):

https://intodns.ai/api/mcp

Example client config (Claude Code):

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

Or self-host the same thing:

npx intodns-mcp --http 3002   # POST /mcp, GET /health

The standalone server binds to 127.0.0.1 by default. Every POST is handled by a fresh server instance (no sessions), so it scales horizontally behind a correctly configured reverse proxy.

Configuration

By default the server talks to https://intodns.ai.

For local testing or staging, set:

INTODNS_SITE_URL=http://localhost:3000 npx -y intodns-mcp

Optional HTTP and upstream safeguards:

INTODNS_REQUEST_TIMEOUT_MS=60000

INTODNS_HTTP_HOST=127.0.0.1 INTODNS_ALLOWED_HOSTS=mcp.example.com INTODNS_ALLOWED_ORIGINS=https://mcp.example.com

INTODNS_HTTP_HOST=0.0.0.0 is intended only for containers or reverse-proxy deployments. Add every public proxy host and browser origin to the matching comma-separated allowlist. Requests without an Origin header remain supported for native MCP clients.

Requirements

• Node.js 18+
• Internet access to reach IntoDNS.ai
• No API key required for public diagnostics

License

MIT - built by Cobytes B.V.