Audits DNS, email authentication, deliverability, TLS, and web security through IntoDNS.ai without an API key.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent ā or use 1-click editor setup below.
š” Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Intodns MCP Server.
scan_domainRun the fast IntoDNS.ai DNS and email security scan (~3-8s). Returns a letter grade A+ to F, numeric score 0-100, structured issue list, prioritised recommendations, full DNS/email/web/security result sections, and canonical citation URLs. Read-only ā no domain mutation, no destructive side effects. The default tool for agent-visible scan evidence; use get_everything_report for a deeper single-shot report including web/blacklist/sender data, or start_deep_scan for slower Internet.nl-grade analysis. After running, use explain_issue or generate_dns_fix on any returned issue. No auth.
nis2_quickscanCompute a NIS2 Article 21.2 readiness score for a domain by mapping the IntoDNS quickscan onto the ten NIS2 measures. Returns a 0-100 weighted total, per-measure status (Article 21.2 a-j), evidence rows, critical gaps, and concrete fix suggestions. The score reflects only the DNS and email layer of NIS2 ā full NIS2 compliance also requires audit of web applications, supply chain, organisational processes, and training. Use when the user asks about NIS2 compliance, NIS2 readiness, NIS2 Article 21.2, cyber-hygiene compliance, or related EU-NIS regulation checks for a domain.
get_everything_reportGenerate the complete live IntoDNS.ai report covering DNS, email authentication, web/HTTPS, blacklist reputation, sender requirements, and canonical citation URLs in a single call. Read-only, no domain mutation. ~5-15s latency depending on backend cache state. Use when the user asks for everything, the full picture, or a deep current-state summary; use scan_domain for a faster default scan, or create_report_snapshot when the result must remain immutable for audit/ticket use. No auth, no side effects.
create_report_snapshotCreate an immutable evidence snapshot of the current Everything Report for a domain. Returns a snapshot ID, ISO timestamp, SHA-256 content hash, and stable bookmarkable URLs for both JSON and Markdown renderings of the report. Snapshots are write-once and resolve to the same evidence months/years later ā useful for tickets, audit trails, NIS2/ISO compliance evidence, and LLM citations that should not drift. A canonical POST creates one snapshot per call (additive and not idempotent); use get_report_snapshot to read it back. Use this instead of get_everything_report when the result must remain stable.
get_report_snapshotRead a previously created IntoDNS.ai Everything Report evidence snapshot by snapshot ID. Read-only GET ā returns the immutable JSON report exactly as it was at snapshot creation, with the original SHA-256 content hash and timestamp. Requires `snapshotId` from create_report_snapshot. Use to verify or re-read an audit-trail evidence record without re-running a live scan; use get_everything_report for current live data instead. No auth, fully idempotent.
start_deep_scanStart a long-running Internet.nl deep scan (typically 30-120s). Returns a `scanId` immediately; poll get_deep_scan_status until status='finished'. Read-only ā no domain mutation. Internet.nl runs an exhaustive standards-compliance audit (IPv6, DNSSEC, modern TLS, RPKI, mail authentication) used by EU governments. Use when scan_domain output is not strict enough for compliance reporting, or when the user asks for an Internet.nl-grade audit. For sub-10s answers, use scan_domain. To abort an in-progress scan, call cancel_deep_scan. No auth.
RoscoNL/intodns-mcp-server MCP server exposes IntoDNS.ai diagnostics as MCP tools for AI clients. Its checks cover DNS records, DNSSEC, propagation, SPF, DKIM, DMARC, BIMI, MTA-STS, SMTP STARTTLS, FCrDNS, TLSA/DANE, mail-server blacklists, sender requirements, and HTTP/3. It also provides WHOIS/RDAP lookups, security-header and CSP analysis, raw email analysis, DMARC report parsing, and inbound email testing.
The main entry point is scan_domain, which returns a grade, numeric score, detected issues, recommendations, detailed result sections, and citation URLs. Use get_everything_report for a broader live report or start_deep_scan for an Internet.nl-style audit that runs asynchronously. All of these diagnostics are read-only except for additive operations such as creating an email-test session or report snapshot; they do not change DNS or mail configuration.
The server sends requests to the public IntoDNS.ai API and returns structured results through MCP. Most tools require only a domain, while specialized operations accept inputs such as a DNS record type, DKIM selector, IP address, scan ID, snapshot ID, raw email, or DMARC XML. No authentication or API key is required for the public diagnostic functions.
Long-running scans use a start-and-poll pattern: call start_deep_scan, then check get_deep_scan_status until completion. Report snapshots create write-once evidence with a timestamp, SHA-256 hash, snapshot ID, and stable JSON and Markdown URLs. Email tests create a temporary address valid for 60 minutes; after sending a message, retrieve or process the result with get_email_test or poll_email_test.
RoscoNL/intodns-mcp-server MCP server requires Node.js 18+ and internet access to reach IntoDNS.ai. The local stdio configuration runs the package with npx -y intodns-mcp. It can also be used through the hosted Streamable HTTP endpoint at https://intodns.ai/api/mcp, or started locally in HTTP mode with npx intodns-mcp --http 3002.
The default upstream is https://intodns.ai. INTODNS_SITE_URL can point to a local or staging instance. Optional controls include INTODNS_REQUEST_TIMEOUT_MS, INTODNS_HTTP_HOST, INTODNS_ALLOWED_HOSTS, and INTODNS_ALLOWED_ORIGINS. The standalone HTTP server binds to 127.0.0.1 by default. When placed behind a proxy, configure the host and origin allowlists for the public endpoint; native MCP requests without an Origin header remain supported.
Useful tool groups include:
scan_domain, nis2_quickscan, get_everything_report, report snapshots, and Internet.nl deep scans.RoscoNL/intodns-mcp-server MCP server reports current observations rather than guaranteeing full compliance. The NIS2 score covers only DNS and email controls, not applications, supply chain, organisational processes, or training. DKIM discovery without a known selector is heuristic and a miss is inconclusive. BIMI checks do not certify SVG profile compliance, certificate trust, trademark ownership, or mailbox-provider logo display.
TLSA/DANE checks inspect DNS records but do not cryptographically compare them with a live certificate. Sender-requirement checks cannot verify message behavior such as complaint rate or one-click unsubscribe without provider telemetry. Blacklist checks are reputation signals, not delisting services. Flattened SPF records require maintenance when providers change their IP ranges. SMTP and deep scans can take substantially longer than the fast scan.
Factual signals from GitHub, npm, and our automated checks ā not a rating.
No reviews yet ā be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/rosconl-intodns-mcp-server)<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>