Security & Testing
intodns.ai
Provides DNS and email security scanning, NIS2 compliance readiness assessment, and evidence snapshots for domains.
ENDPOINT 1
https://intodns.ai/api/mcp
MCP server metadata
- Name
- intodns
- Version
- 1.9.0
Known tools 45
create_report_snapshotCreate an immutable evidence snapshot of the current Everything Report for a domain.
Potential side effectscheck_dns_propagationCompare DNS responses across the nine currently configured public and authoritative resolvers to detect propagation lag, missing answers, or inconsistent TTL/data values.
Inferred read-onlycheck_smtp_tlsLive check of every MX host: 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.
Inferred read-onlycheck_fcrdnsRead-only FCrDNS (Forward-Confirmed Reverse DNS) audit for every IP that backs the domain's MX records.
Inferred read-onlycheck_blacklistRead-only query against the currently configured public DNSBL/RBL providers (roughly 60, with noisy providers explicitly disabled).
Inferred read-onlycheck_sender_requirementsRead-only domain-side preflight against Google/Yahoo bulk-sender requirements.
Inferred read-onlycheck_email_securityRead-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.
Potential side effectsanalyze_raw_emailRead-only analysis of a pasted raw RFC-5322 MIME email source.
Potential side effectsparse_dmarc_reportRead-only parser for a DMARC aggregate (RUA) XML report (RFC 7489).
Inferred read-onlygenerate_dns_fixGenerate copy-pasteable DNS record snippets that fix one specific issue (e.
Inferred read-onlyanalyze_security_headersScan a live website and report which HTTP security headers it currently sends.
Inferred read-onlygenerate_security_headersGenerate 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.
Inferred read-onlygenerate_spfBuild an SPF (Sender Policy Framework) record — the DNS TXT record that lists which servers may send mail for a domain.
Potential side effectsgenerate_dmarcBuild 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.
Potential side effectsgenerate_tlsaBuild 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.
Inferred read-onlyscan_cspCrawl a live website (up to 20 same-origin pages) and build a Content-Security-Policy for it.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.intodns]
url = "https://intodns.ai/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"intodns": {
"type": "http",
"url": "https://intodns.ai/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: intodns
Remote MCP URL: https://intodns.ai/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"intodns": {
"url": "https://intodns.ai/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"intodns": {
"type": "http",
"url": "https://intodns.ai/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "intodns",
"transport": "streamable-http",
"url": "https://intodns.ai/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for intodns.ai was fetched 2026-08-21T13:40:10.779Z.
intodns.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.