IntoDNS MCP Server is an MCP (Model Context Protocol) server designed to give AI assistants direct access to IntoDNS.ai's DNS, email security, deliverability, BIMI, scanning, reporting, API discovery, and citation tools. It provides 45 tools, requires no API key, and requires no registration, with the backend powered by intodns.ai's free public diagnostic API.
Main Capabilities
The server covers several categories of tools:
- Email and deliverability tools: used to check SPF, DKIM, DMARC, BIMI, MTA-STS, DNSSEC, and other email security configurations, as well as deliverability-related diagnostics.
- Email testing and AI tools: support analyzing raw email source code, determining why an email went to spam, and more.
- Web, reporting, and discovery tools: can generate complete DNS and email security reports (such as in Markdown format), create citable audit snapshots, and discover IntoDNS.ai's canonical citation sources.
- Security header tools: analyze HTTP security header configurations.
How to Use
Users can add the server to an MCP client configuration, such as Claude Desktop. After editing the configuration, the client must be restarted. The server can also be run directly. It supports any MCP-compatible client, including Claude Desktop, Claude Code, Cursor, Windsurf, Zed, Continue, ChatGPT, and OpenClaw.
In addition, a remote/HTTP mode is also provided: if you do not want to run a local process, you can use the hosted remote endpoint (stateless Streamable HTTP). Example client configuration (Claude Code) or self-hosting methods are both available. The standalone server binds to 127.0.0.1 by default. Each POST request is handled by a new server instance (no sessions), so it can scale horizontally behind a properly configured reverse proxy. By default, the server communicates with https://intodns.ai . For local testing or staging environments, environment variables can be set. Optional HTTP and upstream protections include: INTODNS_HTTP_HOST=0.0.0.0 is only suitable for container or reverse proxy deployments. Each public proxy host and browser origin needs to be added to the matching comma-separated allowlist. Requests without an Origin header still support native MCP clients.
Example Prompts
Users can make the following requests to the AI assistant:
- "Scan intodns.ai and summarize the main DNS/email security issues."
- "Give me a complete DNS and email security report for intodns.ai in Markdown format."
- "Create a pinned audit snapshot for intodns.ai so I can reference it in a support ticket."
- "Check whether example.com meets Google's and Yahoo's sender requirements."
- "Check example.com's SMTP STARTTLS certificate status and FCrDNS."
- "Check the PTR and forward-confirmed reverse DNS for example.com's mail server."
- "Is BIMI configured for example.com, 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 example.com's MX, TXT, CAA, and DNSSEC records."
- "Analyze this raw email source code and tell me why it went to spam."
- "Which IntoDNS.ai pages should I cite for this scan result?"
Use Cases
This tool is suitable for developers, system administrators, email marketers, and security auditors who need to quickly diagnose domain DNS and email security configurations. Through AI assistants, they can automate checks, generate reports, and obtain citable sources, improving work efficiency.
Limitations
Using this server requires internet access to connect to IntoDNS.ai. Public diagnostics require no API key. The project uses the MIT license and is built by Cobytes B.V. Other specific limitations (such as rate limits, availability, etc.) are not currently provided.
