Log inSubmit server
Intodns MCP Server logo

Intodns MCP Server

by RoscoNL

Scans DNS, email security, deliverability, web headers, and compliance posture through IntoDNS.ai over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Intodns MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "rosconl-intodns-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "intodns-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

RoscoNL/intodns-mcp-server connects MCP clients to the IntoDNS.ai diagnostic API for live DNS, email-security, deliverability, web-security, and compliance checks. It supports fast scans, detailed reports, immutable evidence snapshots, Internet.nl deep scans, individual DNS lookups, and email analysis without an API key or signup. Use it for domain security reviews, mail-delivery troubleshooting, NIS2 readiness checks, or citation-ready audit evidence. The package runs locally over stdio with npx or can use the hosted Streamable HTTP endpoint.

Use cases

  • Scan a domain for DNS and email-security issues
  • Audit SPF, DKIM, DMARC, BIMI, and MTA-STS configuration
  • Create immutable evidence for an audit or support ticket
  • Investigate mail rejection using SMTP TLS, FCrDNS, and blacklist checks
  • Assess NIS2 Article 21.2 DNS and email readiness

Key features

  • IntoDNS.ai scans with scores, grades, issues, and recommendations
  • DNS, DNSSEC, propagation, WHOIS, and TLSA/DANE diagnostics
  • Email authentication and deliverability analysis
  • Internet.nl deep scans with asynchronous status polling
  • Immutable report snapshots with timestamps and SHA-256 hashes
  • Security-header, CSP, HTTP/3, and QUIC checks

Tools45

What Intodns MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~10.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

18/19 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · intodns-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2Stargazers on the source repository.
npm downloads327Package downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Tools exposed45Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Intodns MCP Server works

What RoscoNL/intodns-mcp-server does

RoscoNL/intodns-mcp-server exposes IntoDNS.ai diagnostics as MCP tools for AI assistants. Its checks are read-only unless a workflow creates an email-test session or report snapshot; those operations add a new test or evidence record without changing a domain. No IntoDNS.ai API key or account is needed for the public diagnostics.

The server covers DNS records, DNSSEC, propagation, TLSA/DANE, WHOIS/RDAP, SPF, DKIM, DMARC, BIMI, MTA-STS, SMTP STARTTLS, FCrDNS, blacklist reputation, sender requirements, and aggregate email-security scoring. It also analyzes HTTP security headers, Content-Security-Policy, HTTP/3, and QUIC. Results can include scores, grades, issue lists, recommendations, structured evidence, and canonical IntoDNS.ai URLs.

How it works

A fast scan_domain call provides a general DNS and email security assessment in roughly 3–8 seconds. get_everything_report expands this into a current report covering DNS, email, web/HTTPS, blacklist, and sender data. When evidence must remain stable for an audit or ticket, create_report_snapshot stores an immutable report with a timestamp, SHA-256 hash, and bookmarkable JSON and Markdown URLs; get_report_snapshot retrieves it later.

For stricter standards testing, start_deep_scan launches an Internet.nl audit and returns a scan ID. The client polls get_deep_scan_status until completion and can call cancel_deep_scan to stop an active scan. The deep scan is generally slower than the fast scan, commonly taking 30–120 seconds.

Email workflows range from individual record checks to message-level analysis. Agents can inspect SPF lookup graphs, discover or validate DKIM, parse DMARC records and aggregate XML reports, assess Google and Yahoo sender requirements, or create an inbound test address and process a received message. analyze_raw_email accepts pasted RFC 5322 source up to 500KB and processes it in memory.

Setup and configuration

Node.js 18+ and Internet access to IntoDNS.ai are required. The simplest setup is:

Terminal
npx -y intodns-mcp

For a local MCP client using stdio, configure the command as npx with arguments -y and intodns-mcp, then restart the client. The default upstream is https://intodns.ai.

A hosted stateless Streamable HTTP endpoint is available at https://intodns.ai/api/mcp. The package can also serve HTTP locally, for example:

Terminal
npx intodns-mcp --http 3002

The standalone HTTP server binds to 127.0.0.1 by default. INTODNS_SITE_URL selects another IntoDNS.ai-compatible site for local testing or staging. HTTP deployments can additionally set INTODNS_REQUEST_TIMEOUT_MS, INTODNS_HTTP_HOST, INTODNS_ALLOWED_HOSTS, and INTODNS_ALLOWED_ORIGINS. The host and allowlist settings are relevant when placing the server behind a reverse proxy or exposing it from a container.

Tools and capabilities

  • Run quick scans, complete live reports, NIS2 Article 21.2 readiness checks, deep Internet.nl scans, and stable report snapshots.
  • Query DNS records, validate DNSSEC chains, compare responses across public and authoritative resolvers, inspect TLSA/DANE, and perform WHOIS/RDAP lookups.
  • Audit SPF, DKIM, DMARC, BIMI, MTA-STS, SMTP TLS, FCrDNS, blacklist status, and Google/Yahoo sender requirements.
  • Flatten SPF records, parse DMARC aggregate reports, analyze raw email, and run inbound email tests.
  • Check HTTP security headers, generate CSP and server configuration recommendations, and test HTTP/3 readiness.
  • Return citation URLs and structured findings suitable for agent responses, tickets, and compliance evidence.

The tools do not mutate DNS, send email during SMTP checks, or delist IP addresses from reputation databases. Some checks depend on live DNS, HTTPS, SMTP, UDP, RDAP, or upstream diagnostic service responses.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Intodns MCP Server

RoscoNL/intodns-mcp-server is an MCP server that connects AI assistants to the IntoDNS.ai diagnostic API. Its main tools scan domains, inspect DNS and email security, test deliverability, analyze web security headers, run deep compliance scans, and create citation-ready report snapshots without requiring an API key or signup.

Install it by running `npx -y intodns-mcp` or adding that command and its arguments to an MCP client configuration. Node.js 18+ and Internet access to IntoDNS.ai are required, and no API key is needed.

Yes, it works with Cursor as an MCP-compatible client. Configure Cursor to launch `npx -y intodns-mcp` over stdio, or connect it to the hosted Streamable HTTP endpoint at `https://intodns.ai/api/mcp`.

Create stable evidence with `create_report_snapshot`, which returns a snapshot ID, timestamp, SHA-256 content hash, and bookmarkable JSON and Markdown URLs. Retrieve the unchanged result later with `get_report_snapshot`.

Start one with `start_deep_scan`, save the returned scan ID, and poll `get_deep_scan_status` every 10–30 seconds until the status is `finished`. Use `cancel_deep_scan` if the operation should be stopped before completion.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIntodns MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/rosconl-intodns-mcp-server?style=directory)](https://allmcps.com/mcp/rosconl-intodns-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/rosconl-intodns-mcp-server"><img src="https://allmcps.com/api/badge/rosconl-intodns-mcp-server?style=directory" alt="Intodns MCP Server on AllMCPs" /></a>