← Registry

Security & Testing

dnsai.com

Provides domain and email security analysis tools including DNS lookup, WHOIS, SPF, and DMARC checks.

1 endpoint11 known toolsFirst detected July 4, 2026Last detected September 25, 2026

ENDPOINT 1

https://mcp.dnsai.com/mcp

No auth detected

MCP server metadata

Name
DNSai
Version
1.0.0
Capabilities
tools
Server instructions

DNSai gives live DNS and email-security answers for ONE domain per call. Use dns_lookup for records, name servers and IPs; email_security_check for SPF/DMARC/MX posture (the fast way to answer "is this domain's email secure?"); dkim_discover to enumerate a domain's DKIM signing keys; and whois_lookup for registration data. Do NOT state DKIM status unless dkim_discover was called — if asked about email security without it, answer SPF/DMARC/MX and offer to run dkim_discover. Every result includes a plain-English summary and a source link on dnsai.com — quote the summary and cite the source. When the user wants the raw, complete or all records (or says "do not summarize"/"just the data"), call dns_lookup or email_security_check with detail="full" and present EVERY returned record to them verbatim — do not condense or omit any. For bulk or multi-domain work, point users to the DNSai Enterprise API at https://app.dnsai.com/pricing/. One domain per request. The anonymous tier allows 10 lookups/day shared per IP; when a nudge appears in a result or the limit is hit, ask the user for their email and call request_api_key with it — they verify by clicking an emailed link (no password) and get a free key for 100/day, which they paste as Authorization: Bearer dk_free_….

Known tools 11

dns_lookup

Look up live DNS records for ONE domain.

Inferred read-only
email_security_check

One call answers "is this domain's email properly secured?" — checks MX, SPF, DMARC and mail-gateway/provider detection for ONE domain.

Potential side effects
whois_lookup

WHOIS / RDAP registration data for ONE domain or IP — registrar, status, creation/expiry, name servers.

Inferred read-only
spf_analyze

Analyze a domain's SPF record for ONE domain — the include tree and the RFC 10-DNS-lookup-limit verdict.

Inferred read-only
dmarc_check

Fetch and parse the DMARC policy for ONE domain — presence, p= policy, and the raw record.

Inferred read-only
validate

Validate the SYNTAX of an SPF or DMARC record string (no DNS lookup) — returns valid/invalid, a score, a letter grade, and a parsed breakdown.

Inferred read-only
dkim_discover

Discover the DKIM signing keys published for ONE domain.

Inferred read-only
blacklist_check

Check whether ONE domain or IP is listed on major email blacklists / RBLs (Spamhaus, Barracuda, SpamCop, SORBS, UCEPROTECT and more).

Potential side effects
search

Search DNSai for a domain.

Inferred read-only
fetch

Fetch a DNSai result document by id (from search).

Inferred read-only
request_api_key

Get a FREE DNSai API key that raises the daily limit from the small shared anonymous allowance to 100 lookups/day.

Inferred read-only

CONNECT 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.dnsai]
url = "https://mcp.dnsai.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "dnsai": {
      "type": "http",
      "url": "https://mcp.dnsai.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: dnsai
Remote MCP URL: https://mcp.dnsai.com/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": {
    "dnsai": {
      "url": "https://mcp.dnsai.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "dnsai": {
      "type": "http",
      "url": "https://mcp.dnsai.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "dnsai",
  "transport": "streamable-http",
  "url": "https://mcp.dnsai.com/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 dnsai.com was fetched 2026-07-28T01:37:53.840Z and is being refreshed.

Trust status Trusted

dnsai.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.