DNSai Free DNS Tools
REMOTE · MCP.DNSAI.COM
Free live DNS, SPF/DMARC/MX, DKIM and WHOIS lookups for any domain. No key needed to start.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1925 tokens (~175/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (73% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 71
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.dnsai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dnsai.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | df40758f74985eb70ecd4068edff50e5 |
| SANs: dnsai.com, mcp.dnsai.com, *.mcp.dnsai.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.dnsai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dnsai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.dnsai.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.dnsai.com/mcp | HTTPS enforced | 301 | https://mcp.dnsai.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
blacklist_check Blacklist Check ~139
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 verdict names the IP and role it applies to, since website and mail reputation can differ. Returns a listed/clean verdict with the specific lists. One target per call.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A single domain or IP address, e.g. "acme.com" or "8.8.8.8". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
dkim_discover DKIM Discovery ~115
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 domain can publish DKIM under a private selector that discovery won't surface, so "none found" is not proof of "no DKIM". One domain per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The single domain to check, e.g. "acme.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
dmarc_check DMARC Check ~103
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), use email_security_check instead. One domain per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The single domain to check, e.g. "acme.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
dns_lookup DNS Lookup ~444
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 those explicitly (e.g. type="DNSKEY") to check them. Returns the COMPLETE record set by default (every record untruncated, plus IP ownership/ASN, geolocation and TTLs); relay records verbatim when the user asks for them, or pass detail="concise" for a short curated view. Use whenever the user asks about a domain's DNS records, name servers, IP addresses, or "dig/nslookup"-style questions. Returns live data from public resolvers with a plain-English summary. Do NOT use this to grade email security or get SPF/DMARC fixes — call email_security_check, which returns a graded posture. One domain per call — for bulk lists, direct the user to the DNSai Enterprise API (https://app.dnsai.com). Example: dns_lookup(domain="acme.com", type="MX").
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Output detail. Default (omit, or "full") returns the COMPLETE lookup: every record untruncated, plus network/ASN/geolocation, TTLs and resolver details — present the records the user asks for verbati… |
| domain | string | yes | The single domain to look up, e.g. "acme.com". |
| resolver | string | – | Upstream resolver. Default google. |
| type | string | – | DNS record type to return. Default "common" returns the standard set (A, AAAA, MX, NS, TXT, SOA, CNAME, CAA + DNSSEC verdict); it does NOT query DNSKEY/RRSIG/NSEC* — those appear under not_queried an… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
email_security_check Email Security Check ~227
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, spoofing protection, SPF/DMARC posture, or "is email set up correctly". Prefer this over dns_lookup, spf_analyze or dmarc_check for any "is the email secure / well-configured" question — it returns a graded verdict with prioritized fixes, followed by every underlying DNS record (complete by default; detail="concise" for the grade + key records only). For DKIM signing keys, use dkim_discover. One domain per call.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Output detail. Default (omit, or "full") returns the graded posture PLUS every underlying DNS record untruncated. "concise" returns the grade, checks, fixes and the MX/SPF/DMARC records only. |
| domain | string | yes | The single domain to assess, e.g. "acme.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
fetch DNSai Fetch ~54
Fetch a DNSai result document by id (from search). Runs the lookup and returns the data plus a summary.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A result id from search, e.g. "email_security_check:acme.com". |
No output schema declared.
No examples provided.
request_api_key Request Free API Key ~130
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 SOON AS the user provides an email address, and offer it proactively whenever a lookup response carries an upgrade nudge or the anonymous limit is hit. After they verify, they paste the emailed key into their client (Authorization: Bearer dk_free_…).
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address to send the verification link to. |
No output schema declared.
No examples provided.
search DNSai Search ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A natural-language query or a bare domain. |
No output schema declared.
No examples provided.
spf_analyze SPF Analyzer ~98
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 secure" grade, use email_security_check instead. One domain per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The single domain to analyze, e.g. "acme.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
validate SPF/DMARC Record Validator ~109
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| record | string | yes | The raw SPF or DMARC record to validate, e.g. "v=spf1 include:_spf.google.com ~all". |
| type | string | – | Record type. Default auto-detect. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
whois_lookup WHOIS Lookup ~102
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". One target per call.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A single domain or IP address, e.g. "acme.com" or "8.8.8.8". |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Clean machine values (DNS/WHOIS tools). |
| result | object | – | Raw engine data. |
| source | string | yes | Deep link on dnsai.com. |
| summary | string | yes | – |
| usage | object | – | – |
No examples provided.
How do I install the DNSai Free DNS Tools MCP server?
DNSai Free DNS Tools is a hosted endpoint at https://mcp.dnsai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.dnsai.com
claude mcp add --transport http com-dnsai-dnsai-free 'https://mcp.dnsai.com/mcp'
What is the DNSai Free DNS Tools MCP server?
DNSai Free DNS Tools is an MCP server listed in the public MCP registry as com.dnsai/dnsai-free. Free live DNS, SPF/DMARC/MX, DKIM and WHOIS lookups for any domain. No key needed to start. This page covers its hosted endpoint (https://mcp.dnsai.com/mcp).
Is the DNSai Free DNS Tools MCP server safe to use?
DNSai Free DNS Tools scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DNSai Free DNS Tools MCP server expose?
DNSai Free DNS Tools exposes 11 tools: dns_lookup, email_security_check, whois_lookup, spf_analyze, dmarc_check, and 6 more. Their descriptions and schemas cost roughly 1,589 tokens of context every time the server is loaded.
Does the DNSai Free DNS Tools MCP server require authentication?
No. We connected to DNSai Free DNS Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DNSai Free DNS Tools MCP server still maintained?
DNSai Free DNS Tools is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.