Real-time web search, reasoning, and research through Perplexity's API
Nothing to run from here
DNSai Free DNS Tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
Free live DNS, SPF/DMARC/MX, DKIM and WHOIS lookups for any domain. No key needed to start.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http dnsai-free-dns-tools-mcp https://mcp.dnsai.com/mcp
# 2 — ask your agent for something these tools do
# dns_lookup, email_security_check, whois_lookup and 8 more
DNSai Free DNS Tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DNAll 2 servers
dnsai2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http dnsai-free-dns-tools-mcp https://mcp.dnsai.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take Authorization header (Optional: 'Bearer dk_free_...' free key for 100 lookups/day (the server's request_api_key tool emails one)) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The single domain to look up, e.g. "acme.com". |
| type | string | no | 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 and |
| resolver | string | no | Upstream resolver. Default google. |
| detail | string | no | 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 verbatim |
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-confi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The single domain to assess, e.g. "acme.com". |
| detail | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A single domain or IP address, e.g. "acme.com" or "8.8.8.8". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The single domain to analyze, e.g. "acme.com". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The single domain to check, e.g. "acme.com". |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| record | string | yes | The raw SPF or DMARC record to validate, e.g. "v=spf1 include:_spf.google.com ~all". |
| type | string | no | Record type. Default auto-detect. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | The single domain to check, e.g. "acme.com". |
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 ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A single domain or IP address, e.g. "acme.com" or "8.8.8.8". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | A natural-language query or a bare domain. |
Fetch a DNSai result document by id (from search). Runs the lookup and returns the data plus a summary.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A result id from search, e.g. "email_security_check:acme.com". |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The user's email address to send the verification link to. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install DNSai Free DNS Tools or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.1.0 · scanned 2 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest68a39f41272ce3f6486572d10df83565d01d31f5b96aaec7fe93c2d15e2b63e2
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| dns_lookup | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| email_security_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| whois_lookup | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| spf_analyze | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| dmarc_check | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| validate | no tags | |
| dkim_discover | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| blacklist_check | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| search | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| fetch | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| request_api_key | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest68a39f41272ce3f6
Scanned2026-11-02
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish DNSai Free DNS Tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.