DNSai MCP server

Which MCP servers are DNSai's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-02

← Back to DNSai

Whose server it is

Registry namecom.dnsai/dnsai-freeverified in the MCP registry

The registry name sits under dnsai.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-02

Stateanswerschecked 2026-11-02
Tools11
Server calls itselfDNSai
Server version1.1.0
Protocol version2025-06-18

On 2026-11-02 the server answered initialize and tools/list without a sign-in. First answer in 213 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-11-02

INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
Answeredmeasuring1 of the 7 daily checks it takes to print a share
Median first answer154 ms
Space in an agent's context≈ 1,989 tokensthe definitions of all its tools (11), which an agent carries on every turn
Tool definitionsA · 100 of 100
Typed results8 of 11 toolsdeclared outputSchema: results come typed, read once

Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers11 tools · read 2026-11-02

dns_lookup
Look up live DNS records for ONE domain. The default "common" view queries the standard set (A, AAAA, MX, NS, TXT, SOA, CNAME, CAA and more) plus a DNSSEC signed/unsigned verdict; types it did not query are listed in not_queried — request…
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. The differentiator vs a plain DNS resolver. Use when the user asks about email deliverability…
whois_lookup
WHOIS / RDAP registration data for ONE domain or IP — registrar, status, creation/expiry, name servers. Returns publicly published WHOIS/RDAP data as-is. Use for "who owns", "when does it expire", "registrar", "when was it registered"…
spf_analyze
Analyze a domain's SPF record for ONE domain — the include tree and the RFC 10-DNS-lookup-limit verdict. Use only when the question is specifically about SPF (include tree, lookup count, the `all` qualifier). For an overall "is email…
dmarc_check
Fetch and parse the DMARC policy for ONE domain — presence, p= policy, and the raw record. Use for DMARC-only questions ("does this domain have DMARC", "is it p=reject/quarantine/none"). For full email posture (SPF + DMARC + MX, graded)…
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. Use when the user pastes an SPF/DMARC record and asks "is this correct?".
dkim_discover
Discover the DKIM signing keys published for ONE domain. Returns the signing keys found, the mail providers they map to, and their selectors. Use when the user asks about DKIM, signing keys, or "does this domain sign its mail?". Note: a…
blacklist_check
Check whether ONE domain or IP is listed on major email blacklists / RBLs (Spamhaus, Barracuda, SpamCop, SORBS, UCEPROTECT and more). For a domain, checks the domain itself, its website (A-record) IP AND its mail-server (MX) IPs — each…
search
Search DNSai for a domain. Returns result items (id, title, url) covering that domain's DNS records, email-security posture, DMARC policy and WHOIS — pass a result id to fetch for the full data.
fetch
Fetch a DNSai result document by id (from search). Runs the lookup and returns the data plus a summary.
request_api_key
Get a FREE DNSai API key that raises the daily limit from the small shared anonymous allowance to 100 lookups/day. Pass the user's email; they receive a verification link and, once clicked, the key — no password, no signup. Call this AS…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "dnsai-free": {
      "type": "http",
      "url": "https://mcp.dnsai.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http dnsai https://mcp.dnsai.com/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.dnsai.com/mcp as a custom connector in the settings.

Other servers listed as DNSai's

com.dnsai/dnsaianswers, requires sign-inverified in the MCP registry

OpenAPI spec

10 paths, read 2026-11-02. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.