{"data":{"name":"ai.intodns/scanner","title":"IntoDNS.ai DNS & Email Security Scanner","description":"DNS and email security: check SPF, DKIM, DMARC, DNSSEC, DANE and build the records. 45 tools.","version":"1.11.3","websiteUrl":"https://intodns.ai/mcp","repositoryUrl":"https://github.com/RoscoNL/intodns-mcp-server","remotes":[{"type":"streamable-http","url":"https://intodns.ai/api/mcp"}],"packages":[{"registryType":"npm","identifier":"intodns-mcp","version":"1.11.3","runtimeHint":"stdio","runtimeArguments":null,"environmentVariables":null}],"status":"active","isLatest":true,"publishedAt":"2026-10-27T20:21:23.990Z","updatedAt":"2026-10-27T20:21:23.990Z","source":"official-registry","verification":"official","confidence":100,"stars":null,"sources":[{"source":"official-registry","sourceId":"ai.intodns/scanner","verification":"official","confidence":100,"stars":null,"updatedAt":"2026-10-27T20:21:23.990Z","title":"IntoDNS.ai DNS & Email Security Scanner","description":"DNS and email security: check SPF, DKIM, DMARC, DNSSEC, DANE and build the records. 45 tools.","websiteUrl":"https://intodns.ai/mcp","repositoryUrl":"https://github.com/RoscoNL/intodns-mcp-server"}],"toolIndex":{"tools":[{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"analyze_raw_email","title":"Analyze raw email","description":"Read-only analysis of a pasted raw RFC-5322 MIME email source. Parses Authentication-Results, Received chain, SPF/DKIM/DMARC/ARC verdicts, sender IP reputation/blacklist status, content-side spam triggers (suspicious URLs, misleading From, content/HTML imbalance), and produces a 0-100 spam score plus AI-assisted fix suggestions. `rawEmail` is full headers+body, max 500KB. Use to debug a specific failing email when the user can paste the raw source from their MUA; use create_email_test instead when the user can resend it. POST body is processed in-memory and not stored. No auth.","inputSchema":{"type":"object","properties":{"rawEmail":{"type":"string","maxLength":500000,"description":"Raw email source including headers and body, max 500,000 characters"}},"required":["rawEmail"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"7f94a8e194491c69874ab86ac6f14ed4e65dac3055c212b9689fae769b19924c","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"analyze_security_headers","title":"Analyze security headers","description":"Scan a live website and report which HTTP security headers it currently sends. These headers tell the browser how to behave more safely — the main ones are HSTS (force HTTPS), Content-Security-Policy / CSP (block injected scripts and XSS), X-Frame-Options (stop clickjacking), X-Content-Type-Options (stop MIME sniffing), Referrer-Policy (limit what the URL leaks to other sites), and Permissions-Policy (turn off camera/mic/geolocation by default). Read-only — fetches the page once over HTTPS, nothing is changed. Returns: whether HTTPS works, each expected header with present/missing and its current value, a list of the ones that are missing, a recommended best-practice config, and ready-to-paste server snippets (nginx/Apache/Caddy/Cloudflare/_headers) so a beginner can just copy the fix in. Use this to audit a real site's header posture; use generate_security_headers when you just want a fresh best-practice config to apply without scanning anything first.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"9131860699850c392dab2c986dd8799aadd918bac685407d79c96f354f0443a6","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"cancel_deep_scan","title":"Cancel deep scan","description":"Cancel an in-progress Internet.nl deep scan. Marks the scan cancelled; the polling loop then withdraws the upstream Internet.nl batch, usually within ten seconds. Requires `scanId` returned by start_deep_scan. Nothing is deleted: a scan that already finished keeps its results and is left alone, so calling this twice is safe. An unknown or expired scanId returns 404. Use when the user changes their mind mid-scan or when polling get_deep_scan_status would otherwise time out. No auth.","inputSchema":{"type":"object","properties":{"scanId":{"type":"string","description":"Deep scan ID returned by start_deep_scan"}},"required":["scanId"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"22e4fcc522cedaab6fc972fd60fdc7835a540eb1802c6ab1d98027890c94ae23","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_bimi","title":"Check BIMI readiness","description":"Read-only BIMI readiness check. Parses the `default._bimi` TXT record, safely fetches the referenced HTTPS SVG, and parses basic metadata from an optional VMC/CMC authority certificate. Returns record syntax, URL reachability/content type, certificate subject/issuer/validity dates, and explicit issues. It does not certify SVG Tiny PS profile compliance, validate the full mark-certificate trust chain, verify trademark ownership, or guarantee logo display by any mailbox provider. Use for a technical preflight before a formal BIMI/VMC review. No auth or destructive actions.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"278967406c163fb3a1b8fe921d9cc3b65f7771a144a3896ea7ad60ebd06d2fc1","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_blacklist","title":"Check DNS blacklists","description":"Read-only query against the configured public DNSBL/RBL providers; the response lists which ones answered, which could not be measured and which are disabled. Provide either `domain` to resolve and inspect its MX IPv4 addresses or an IPv4 `ip` for a direct check; at least one is required. Returns each provider's listed/clean result, severity, removal metadata, plus unavailable and disabled provider evidence. A provider error code (e.g. Spamhaus 127.255.255.x when the query is refused), a timeout, or a list that does not answer its RFC 5782 test entry is listed under unavailableProviders: that provider's status is unknown, not clean. Domain-only lists (Spamhaus DBL, NordSpam DBL) and Validity's reputation-score zone (score.senderscore.com, a score rather than a listing) are excluded from IP checks. Use for mail-server reputation triage; it is not a delisting service. No auth or destructive actions.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"},"ip":{"description":"IPv4 address to check directly","type":"string","format":"ipv4","pattern":"^(?:(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])$"}},"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"db729e19ee47aca9d9eb729ce8db55ea3907d7d1a0424ef407f5ad562a6ff3f9","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_dmarc","title":"Check DMARC record","description":"Read-only fetch and parse of the _dmarc TXT record. Returns parsed tag map (p, sp, rua, ruf, adkim, aspf, pct, fo), policy strength assessment, alignment mode, and warnings (missing rua, p=none, weak alignment, multiple records). Use for DMARC policy review; use check_sender_requirements for combined Google/Yahoo SPF+DKIM+DMARC pass/fail verdict. Single GET, no auth, no side effects.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"4e382b7e7bb9c60be04cca6f935f8b384411caa8bb4fb2637df029043d05f944","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_dns_propagation","title":"Check DNS propagation","description":"Compare DNS responses across the nine currently configured public and authoritative resolvers to detect propagation lag, missing answers, or differing record sets. Each resolver's answer is compared as a whole RRset (order, case of names and trailing dots ignored; TXT case kept; TTLs ignored, as caches count them down). Defaults to record type A and region 'all'. Returns every resolver response, how many resolvers were queried, answered and failed, and `percentage` = share of the answering resolvers that agree on the most common answer; that is agreement, not coverage, and a failed resolver was not measured. Use when records were just changed and you suspect staleness; for a single DNS-over-HTTPS lookup use lookup_dns instead. Read-only HTTP, no auth, and no destructive actions.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"DNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)"},"type":{"default":"A","description":"DNS record type to check","type":"string","enum":["A","AAAA","CNAME","MX","NS","TXT","SOA","CAA","SRV","PTR"]},"region":{"default":"all","description":"Resolver region","type":"string","enum":["all","global","europe","americas"]}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"30c919dd32ff96fa52aff93779b9de3389726bdc24767ce2aee7de2e3b9f3411","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_email_security","title":"Full email security check","description":"Read-only combined email-security check covering SPF parse, DKIM selector discovery, DMARC policy validation, MX IP blacklist status across major feeds, and an aggregated 0-100 email-security score with prioritised issue list. Single call replaces sequential check_spf + discover_dkim + check_dmarc + check_blacklist for the typical case. Use for one-shot email security overview; use check_sender_requirements specifically for Google/Yahoo bulk-sender compliance, or the individual check_* tools when you need only one signal. No auth, ~3-8s.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"726ac9af81802491c1c44bddcf0cb4a8ee125f0eaedb45c8fd145560d8d314ff","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_fcrdns","title":"Check forward-confirmed reverse DNS","description":"Read-only FCrDNS (Forward-Confirmed Reverse DNS) audit for every IP that backs the domain's MX records. For each IP: looks up PTR record, then resolves that PTR's hostname back to A/AAAA records to confirm the round-trip. Returns per-IP PTR value, forward-resolution result, match verdict, and warnings (missing PTR, mismatched forward, generic ISP reverse). Use for mail deliverability audits, SpamExperts-style cluster checks, and any 'why is our mail being rejected' debugging; pair with check_blacklist for reputation signals. No auth.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"a53aa9d8d13ce6c86c184be1039054248e2fdb5c6c56c17a4e7209fd31d0dc7b","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_http3","title":"Check HTTP/3 support","description":"Read-only HTTP/3 + QUIC support check for a domain. Combines three signals: Alt-Svc HTTP response header advertising h3, HTTPS/SVCB DNS records advertising alpn=\"h3\", and a live QUIC probe to UDP/443 verifying the handshake completes. Returns per-signal verdict plus an aggregate 'http3_ready' boolean. Use when validating CDN/Cloudflare HTTP/3 rollouts or auditing modern transport posture; not relevant for mail-only domains. No auth, ~2-5s due to UDP handshake timeout.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"d15d5019b9f3d53dcf3b215edf7eaacdbe2858e6884bdb03ca8606c52c8dafcb","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_mta_sts","title":"Check MTA-STS","description":"Read-only check of MTA-STS: TXT record at _mta-sts.<domain> plus the HTTPS policy file at mta-sts.<domain>/.well-known/mta-sts.txt. Returns parsed policy (mode: enforce/testing/none, mx allowlist, max_age), TLS certificate validity for the policy host, and consistency warnings between DNS and HTTPS. Use to verify enforced TLS for inbound mail; pair with check_smtp_tls for live STARTTLS validation. No auth, DNS + HTTPS GET only.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"ff126e7fc3c22c8d0b91cebcec82c2ee31aa014944a5bd7f64edbe07af28879a","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_sender_requirements","title":"Check Google/Yahoo sender requirements","description":"Read-only domain-side preflight against Google/Yahoo bulk-sender requirements. Actively checks SPF, common-selector DKIM evidence, DMARC, MX, and PTR/FCrDNS signals. TLS use, one-click unsubscribe, complaint rate, and From-header behavior require a real sent message/provider telemetry and are returned as informational follow-up items, not false passes. Returns per-requirement pass/fail/warning/info plus an explicitly limited readiness summary. Use before a campaign; use analyze_raw_email or create_email_test to verify message-level requirements. Single GET, no auth.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"34b3e61614cda6ad4fc581475bff4a2b1e32f416be8e6f0c9dcf6d3bfd7c18d2","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_smtp_tls","title":"Check mail server STARTTLS","description":"Live check of the first 4 MX hosts in priority order (hosts beyond 4 are not tested): opens TCP 25, runs EHLO + STARTTLS, validates TLS certificate trust chain, hostname match, expiry window, advertised EHLO capabilities, plus PTR and forward-confirmed reverse DNS. Read-only — connects and quits without sending mail. Returns per-MX TLS protocol version, certificate subject/issuer/SANs/validity/SHA-256 fingerprint, expiry days, and FCrDNS details. Use to verify inbound mail TLS posture; pair with check_mta_sts for the policy layer. May be slower (10-30s) due to live SMTP handshakes. Measured from the IntoDNS.ai server: a host that does not answer there has startTlsSupported null (not measured), not false; do not report that as missing STARTTLS. No auth.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"9b5b256f803c7cf0d87f90125b03f2ddc00d5c7e4dbe6942c9143d6192c7c46b","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_spf","title":"Check SPF record","description":"Read-only SPF parse and validation for a domain. Recursively walks include/redirect mechanisms to build the full lookup graph, counts DNS lookups against the RFC-7208 10-lookup limit, and returns flattening guidance when the count is close to or over the limit. Returns parsed mechanisms, lookup graph, total count, qualifier (~all / -all / +all), and warnings. Use for SPF auditing or before adding new include: senders; use check_email_security for the broader SPF+DKIM+DMARC overview. No auth, no side effects.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"DNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"e949db4e1834925022f97a986c0d72390da9912e4f9d54617c20eace312e4a80","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"check_tlsa_dane","title":"Check TLSA/DANE records","description":"Read-only TLSA/DANE DNS record check. With no port, resolves MX hosts and validates their `_25._tcp` TLSA tuple syntax; with an explicit port, queries `_<port>._<protocol>.<domain>`. Returns parsed usage, selector, matching type, certificate data, syntax errors, and best-practice advisories. It does not fetch or cryptographically match the live service certificate, so pair it with check_smtp_tls for SMTP certificate evidence. Use before publishing DANE records or troubleshooting DANE handover. No auth or destructive actions.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"},"port":{"description":"Port to check, defaults to 25","type":"integer","minimum":1,"maximum":65535},"protocol":{"default":"tcp","description":"Transport protocol","type":"string","enum":["tcp","udp"]}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"d54e01bea4edc1a8a1864e67075636b904e648016bf45a324e9132e86a3d41cc","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"create_email_test","title":"Create email test","description":"Create a new IntoDNS.ai inbound email-test session. Returns a unique single-use test email address (valid 60 minutes) and a `testId` used by get_email_test or poll_email_test. This is an additive, non-idempotent POST: every call creates a fresh session but never modifies prior sessions. `language` controls result text (en/nl/de/fr, default en). Use to debug an outbound message's SPF/DKIM/DMARC, headers, and spam triggers; after sending, call poll_email_test. No auth.","inputSchema":{"type":"object","properties":{"language":{"default":"en","description":"Result language","type":"string","enum":["en","nl","de","fr"]}},"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"e39e44e2a030d1d650db49330f6fa688dfde0eeb8b66510051728523453544ad","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"create_report_snapshot","title":"Create report snapshot","description":"Create 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.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"},"format":{"default":"json","description":"Return the created snapshot as JSON or Markdown","type":"string","enum":["json","markdown"]}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true},"definitionHash":"6bc288d5e36812d896e8f41e3c41fabcb085e1d8215b1d37fd35ce6fa27409ff","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"discover_dkim","title":"Discover DKIM selectors","description":"Read-only DKIM check for a domain. Without `selector`, heuristically queries 50 common selectors and explicitly reports that a miss is inconclusive because DKIM has no enumeration protocol. With `selector`, performs one authoritative exact lookup for a selector obtained from a DKIM-Signature header or mail provider. Returns discovery method, coverage note, parsed key tags, public-key strength, and warnings. Use exact mode whenever the selector is known; use check_email_security for the broader SPF/DKIM/DMARC overview. No auth or destructive actions.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"},"selector":{"type":"string","maxLength":253,"description":"Optional exact DKIM selector, e.g. selector1 or google"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"7f8ef3242f24fa239bc0e57ecd409f89d957c8460478060b84c287696f276fd4","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"explain_issue","title":"Explain issue","description":"Ask the IntoDNS.ai AI service for a plain-language explanation of one specific issue (e.g. `spf_missing`, `no_dnssec`). Returns severity, business impact, root cause, and recommended fix steps as structured text. Read-only POST to /ai/explain — never mutates DNS or domain state. Provide `domain` and `issue` (enum); pass `context` from prior scan output (e.g. scan_domain result) for higher-quality answers. Use after scan_domain when an agent needs to walk a user through *why* a finding matters; use generate_dns_fix for the actual DNS record snippet that resolves it.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"},"issue":{"type":"string","enum":["no_a_record","no_mx_record","mx_ptr_missing","mx_fcrdns_missing","single_ns","dnssec_invalid","nsec3_not_compliant","rrsig_expiring","ds_digest_weak","dnskey_algo_weak","rrsig_ttl_unsafe","chain_incomplete","no_ipv6","no_ipv6_mail","no_dnssec","no_spf","no_dmarc","weak_dmarc","no_dkim","excessive_verification_records","no_http3","spf_missing","spf_too_many_lookups","spf_softfail","dkim_missing","dmarc_missing","dmarc_none","dmarc_quarantine","no_caa","dane_missing"],"description":"Issue identifier, e.g. spf_missing or no_dnssec"},"context":{"description":"Optional issue context from scan output","type":"object","propertyNames":{"type":"string"},"additionalProperties":{}}},"required":["domain","issue"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"970223cb784ecf293644165aaebbfb2632047ed6698c474f3c23b8fd1ceb602f","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"flatten_spf","title":"Flatten SPF record","description":"Read-only SPF flattening for a domain. Resolves the full include/a/mx/redirect graph to literal ip4/ip6 addresses and returns a single flattened SPF record that fits under the RFC-7208 10-lookup limit, plus lookup counts before/after, IP count, record length, whether it must be split across multiple records, and a maintenance warning. Use when a domain hits 'too many DNS lookups' (PermError) and removing unused includes is not enough; run check_spf first to see the lookup graph and whether flattening is actually needed. Flattened records are high-maintenance — they break when a provider rotates IPs — so treat the output as a last resort to re-verify periodically. No auth, no side effects.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"DNS name, e.g. example.com, _spf.google.com or _dmarc.example.com (no URL, path, or port)"}},"required":["domain"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"6c2192b9ba6fca9de5ecd808151db2bf66d1a7c47394529a1d8d01eb475763c8","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"generate_dmarc","title":"Generate DMARC record","description":"Build a DMARC record — the `_dmarc` TXT record that tells receivers what to do when a message fails SPF and DKIM alignment, and where to send reports about it. The risk here is not syntax but policy. `p=none` monitors without affecting delivery and is where every deployment starts; `p=quarantine` sends failures to spam; `p=reject` refuses them outright, which silently destroys legitimate mail from any sender that was missed and gives that sender no explanation. Always publish a `rua` address: without aggregate reports there is no way to see which senders fail before enforcing against them. Use `percentage` to apply an enforcing policy to only part of the mail while rolling out. Returns the record, the host to publish it on (`_dmarc`), and warnings covering the mistakes that actually break mail — enforcing without reporting, reject at full coverage, pct at p=none, and strict alignment breaking subdomain senders and ESPs. Nothing is looked up or stored. A rua/ruf entry that is not a mailbox (name@example.com, optionally mailto: and a !size) or a pct outside 1-100 is refused with an error instead of a record.","inputSchema":{"type":"object","properties":{"policy":{"description":"p= — start at 'none' and only enforce once reports show all legitimate senders aligning. Defaults to none.","type":"string","enum":["none","quarantine","reject"]},"subdomainPolicy":{"description":"sp= — a different policy for subdomains. Omitted when it matches the main policy.","type":"string","enum":["none","quarantine","reject"]},"rua":{"description":"Aggregate report address(es). mailto: is added automatically.","anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}]},"ruf":{"description":"Forensic report address(es). Contains message content and is honoured by very few receivers.","anyOf":[{"type":"string"},{"type":"array","items":{"type":"string"}}]},"percentage":{"description":"pct= — share of mail the policy applies to, for a gradual rollout. Has no effect at p=none. Also accepted as `pct`.","type":"integer","minimum":1,"maximum":100},"pct":{"description":"Alias for `percentage`, matching the DNS tag name.","type":"integer","minimum":1,"maximum":100},"spfAlignment":{"description":"aspf= — strict requires an exact domain match and breaks subdomain senders.","type":"string","enum":["relaxed","strict"]},"dkimAlignment":{"description":"adkim= — strict requires an exact domain match and breaks many ESPs.","type":"string","enum":["relaxed","strict"]},"reportInterval":{"description":"ri= — seconds between aggregate reports. Defaults to 86400 (daily).","type":"integer","minimum":60,"maximum":604800}},"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"f3cc1e48760986b435abf9f9e7e04d7cbb8a79aa891715aedbae064315120b34","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"generate_dns_fix","title":"Generate DNS fix","description":"Generate copy-pasteable DNS record snippets that fix one specific issue (e.g. `spf_missing` → suggested SPF record). Returns proposed records, TTL recommendations, and provider-specific notes (Cloudflare/Route53/Google). Read-only POST to /ai/fix — the API only suggests; it never modifies the user's zone. Provide `domain` and `issue` (enum); pass `context` from prior scan output for tailored output. Use after explain_issue or scan_domain identifies a problem; use lookup_dns afterwards to verify the user has applied the suggested record.","inputSchema":{"type":"object","properties":{"domain":{"type":"string","maxLength":253,"description":"Domain name only, e.g. example.com (no URL, path, or port)"},"issue":{"type":"string","enum":["no_a_record","no_mx_record","mx_ptr_missing","mx_fcrdns_missing","single_ns","dnssec_invalid","nsec3_not_compliant","rrsig_expiring","ds_digest_weak","dnskey_algo_weak","rrsig_ttl_unsafe","chain_incomplete","no_ipv6","no_ipv6_mail","no_dnssec","no_spf","no_dmarc","weak_dmarc","no_dkim","excessive_verification_records","no_http3","spf_missing","spf_too_many_lookups","spf_softfail","dkim_missing","dmarc_missing","dmarc_none","dmarc_quarantine","no_caa","dane_missing"],"description":"Issue identifier, e.g. spf_missing or no_dnssec"},"context":{"description":"Optional issue context from scan output","type":"object","propertyNames":{"type":"string"},"additionalProperties":{}}},"required":["domain","issue"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"ef5de10c8e8dfa0c2060238727a2c246090519680f79955f8207bda69188f756","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"generate_security_headers","title":"Generate security headers","description":"Generate a complete, best-practice set of HTTP security headers (including a sensible Content-Security-Policy) as copy-paste configuration — no scan needed, nothing about your live site is read. Pick a `preset`: 'recommended' is a safe baseline that works for most sites, 'strict' is hardened with a nonce-based CSP for higher security, and 'report-only' puts the CSP in report-only mode so you can roll it out and watch for breakage before enforcing it. Advanced users can instead pass a full `config` object to fine-tune every header; if you pass neither, it defaults to 'recommended'. Returns the resulting headers as name/value pairs, plus ready-to-paste output for nginx, Apache, Caddy, Cloudflare, a Netlify/Cloudflare-Pages `_headers` file, and raw headers, along with any warnings. Use this to set up headers on a new or unscanned site; use analyze_security_headers first when you want to see what an existing site is already missing.","inputSchema":{"type":"object","properties":{"preset":{"description":"Built-in baseline: 'recommended' (safe default), 'strict' (hardened, nonce-based CSP), or 'report-only' (CSP in report-only mode for safe rollout)","type":"string","enum":["recommended","strict","report-only"]},"config":{"description":"Advanced: a full SecurityHeadersConfig object to fine-tune every header. Overrides preset when provided.","type":"object","propertyNames":{"type":"string"},"additionalProperties":{}}},"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"29fa7baf98458fa066cd566853e7ee9b2f181fce78f196847c7513162e476402","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"generate_spf","title":"Generate SPF record","description":"Build an SPF (Sender Policy Framework) record — the DNS TXT record that lists which servers may send mail for a domain. Pass the senders as `mechanisms`: `include` for a provider's own SPF (Google Workspace is `_spf.google.com`, Microsoft 365 is `spf.protection.outlook.com`, SendGrid is `sendgrid.net`), `ip4`/`ip6` for your own servers, plus `useMx`/`useA` to authorise the domain's own MX or A records. The `policy` decides what receivers do with mail from anywhere else: 'fail' (-all, the production choice), 'softfail' (~all, for testing), 'neutral', or 'pass' (+all, which authorises the entire internet and should never be published). SPF is limited to ten DNS-triggering terms during recursive evaluation. This pure builder counts direct mechanisms; include and redirect targets can add nested lookups, so validate the published record with check_spf before treating the count as final. Returns the record, direct lookup count, whether that direct count or the 255-character limit is exceeded, plain-language warnings, and the DNS entry to publish. Use check_spf to resolve and validate a live record, and flatten_spf only when an existing record is over the limit. Invalid input (an address that is not IPv4/IPv6 for ip4/ip6, a value that is not a domain name, or a second redirect=) is refused with an error instead of a record. Nothing is looked up or stored — this is computation only.","inputSchema":{"type":"object","properties":{"mechanisms":{"description":"Senders to authorise, in the order they should appear in the record","type":"array","items":{"type":"object","properties":{"type":{"type":"string","enum":["ip4","ip6","include","a","mx","exists","redirect"]},"value":{"type":"string","description":"The value after the colon, e.g. '_spf.google.com' for an include or '203.0.113.5' for ip4"}},"required":["type","value"]}},"useA":{"description":"Authorise the domain's own A/AAAA records. Costs one DNS lookup.","type":"boolean"},"useMx":{"description":"Authorise the domain's MX hosts. Costs one DNS lookup.","type":"boolean"},"policy":{"description":"What receivers do with everything else: fail (-all) for production, softfail (~all) while testing. Defaults to fail.","type":"string","enum":["fail","softfail","neutral","pass"]}},"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"b52de7d8be23e7a3994e37c1f88c2bd2bf81bff03fae14255e1906211f8328f6","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"},{"serverName":"ai.intodns/scanner","endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","name":"generate_tlsa","title":"Generate TLSA record","description":"Build a DANE TLSA record from a certificate or public key — the DNS record that pins which certificate a mail server may present, so an attacker cannot strip STARTTLS or substitute another CA-issued certificate. Paste the PEM (a CERTIFICATE or PUBLIC KEY block) as `pem`; the hash is computed here because a language model cannot hash. Never send a private key: none is needed and the request is refused if one is present. The three numbers: `usage` 3 (DANE-EE) pins the end-entity key and needs no CA, `selector` 1 hashes the SubjectPublicKeyInfo, `matching` 1 is SHA-256 — the 3 1 1 profile recommended for SMTP, because it survives certificate renewal as long as the key is reused. `host` must be the mail server hostname from the MX record, not the domain. Two things break DANE and both are reported: a TLSA record in a zone without DNSSEC proves nothing and is ignored, and DANE fails closed, so installing a new certificate before the matching record has propagated stops mail from every sender that validates. Returns the record, the hash, what each number means, and the DNS entry.","inputSchema":{"type":"object","properties":{"pem":{"type":"string","description":"PEM block: -----BEGIN CERTIFICATE----- or -----BEGIN PUBLIC KEY-----. Never a private key."},"usage":{"description":"0 PKIX-TA, 1 PKIX-EE, 2 DANE-TA, 3 DANE-EE. Use 3 for SMTP. Defaults to 3.","anyOf":[{"type":"number","const":0},{"type":"number","const":1},{"type":"number","const":2},{"type":"number","const":3}]},"selector":{"description":"0 full certificate, 1 SubjectPublicKeyInfo. Use 1. Defaults to 1.","anyOf":[{"type":"number","const":0},{"type":"number","const":1}]},"matching":{"description":"0 exact, 1 SHA-256, 2 SHA-512. Use 1. Defaults to 1.","anyOf":[{"type":"number","const":0},{"type":"number","const":1},{"type":"number","const":2}]},"host":{"description":"Mail server hostname from the MX record, e.g. mail.example.com — not the domain itself.","type":"string"},"port":{"description":"Port the record covers. Defaults to 25 for SMTP.","type":"integer","minimum":1,"maximum":65535}},"required":["pem"],"$schema":"http://json-schema.org/draft-07/schema#"},"annotations":{"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true},"definitionHash":"f8a7f5327dff5c3c33c62eaed8b2b98ffd0efb0244a229903513c9274d7796b3","schemaStatus":"valid","origin":"official-registry","observedAt":"2026-11-13T20:46:00.381Z","metadataTrust":"untrusted"}],"endpoints":[{"endpointFingerprint":"7b5c0e8da75714db91791b3be7713465100f56d7c380a2cba7bdb67b16fc236b","protocol":"streamable-http","status":"indexed","toolCount":45,"observedAt":"2026-11-13T20:46:00.381Z"}],"authentication":"unknown"},"connectionConfigurations":{"status":"ready","authentication":"not embedded","clients":{"Claude Desktop":{"mcpServers":{"ai.intodns/scanner":{"url":"https://intodns.ai/api/mcp"}}},"Cursor":{"mcpServers":{"ai.intodns/scanner":{"url":"https://intodns.ai/api/mcp"}}},"VS Code":{"servers":{"ai.intodns/scanner":{"type":"http","url":"https://intodns.ai/api/mcp"}}}}},"resourceType":"mcp-server","callable":true,"runtime":{"callable":true,"protocols":["mcp"]},"interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://intodns.ai/api/mcp"},{"protocol":"mcp","package":"intodns-mcp","registryType":"npm","version":"1.11.3"}],"profile":{"apiVersion":"1","schemaVersion":"1","id":"mcp-server:ai.intodns%2Fscanner","resourceType":"mcp-server","canonicalUrl":"https://www.agentsjunction.com/api/v1/servers/ai.intodns%2Fscanner","name":"ai.intodns/scanner","description":"DNS and email security: check SPF, DKIM, DMARC, DNSSEC, DANE and build the records. 45 tools.","interfaces":[{"protocol":"mcp","transport":"streamable-http","url":"https://intodns.ai/api/mcp"},{"protocol":"mcp","package":"intodns-mcp","registryType":"npm","version":"1.11.3"}],"capabilities":[],"identity":{"source":"official-registry","websiteUrl":"https://intodns.ai/mcp","repositoryUrl":"https://github.com/RoscoNL/intodns-mcp-server","version":"1.11.3"},"verification":{"state":"official","confidence":100},"operations":{"resourceType":"mcp-server","name":"ai.intodns/scanner","status":"online","lastCheckedAt":"2026-11-20T05:16:41.517Z","lastSuccessfulCheck":"2026-11-20T05:16:41.517Z","latencyMs":379,"consecutiveFailures":0,"isStale":false,"checks":{"endpointReachable":true,"protocolValid":true,"agentCardValid":null,"mcpHandshakeValid":true},"lastSeen":null,"lastSuccessfulInteraction":null,"lastHealthCheck":"2026-11-20T05:16:41.517Z","source":{"type":"health-check","url":null},"observedAt":"2026-11-20T05:16:41.517Z"},"security":null,"timestamps":{"createdAt":"2026-10-27T20:21:23.990Z","updatedAt":"2026-10-27T20:21:23.990Z","observedAt":"2026-11-20T05:16:41.517Z"},"compatibility":{"serverVersion":"1.11.3","protocolVersions":[{"protocol":"mcp","version":null}]}}}}