x402 Domain Lookup & DNS Email Auth MCP server
dev.workers.microtools-x402.x402-dns-auth-checker/dns-auth-checkerx402-dns-auth-checker.microtools-x402.workers.devstreamable-httpv0.3.2Scanned
DNS+RDAP lookup and SPF/DKIM/DMARC audit via x402. Free sample: /v1/sample
4 tools: 2 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the x402 Domain Lookup & DNS Email Auth MCP server can do
The x402 Domain Lookup & DNS Email Auth MCP server is published by x402-dns-auth-checker.microtools-x402.workers.dev, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: domain_auth_check and health), but cannot delete data. 2 tools only read.
1 tool reads private data (domain_lookup); 1 tool brings in text other people can write (domain_lookup).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 3, 2026, version 0.3.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 2Claude Code: ask
domain_auth_checkAudit a domain's email authentication DNS: SPF (record count, all qualifier, includes, ~DNS lookups vs 10 limit), DMARC (p, sp, pct, rua/ruf, adkim/aspf), DKIM (common or given sel…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Audit a domain's email authentication DNS: SPF (record count, all qualifier, includes, ~DNS lookups vs 10 limit), DMARC (p, sp, pct, rua/ruf, adkim/aspf), DKIM (common or given selectors, key type and length), MX, plus BIMI / MTA-STS / TLS-RPT presence. Returns per-check status, issues, recommendations, score 0-100 and grade A-F. Costs $0.003 USDC per call via x402.
healthFree health check.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Free health check. Returns service status, price and network.
Only reads 2Show 2 read-only tools
domain_lookupDomain lookup: DNS records (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA via Cloudflare DNS-over-HTTPS, DNSSEC AD flag) plus registration data from the registry's RDAP server (IANA bootst…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "domain_lookup" says "lookup": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Domain lookup: DNS records (A, AAAA, MX, NS, TXT, CNAME, SOA, CAA via Cloudflare DNS-over-HTTPS, DNSSEC AD flag) plus registration data from the registry's RDAP server (IANA bootstrap): registrar + IANA id, created / updated / expiry dates, age in days, days to expiry, EPP status, nameservers, DNSSEC delegation, registrar abuse contact. No registrant personal data. Charged only when DNS answered (NOERROR) or the registry RDAP returned the registration. TLDs without RDAP (e.g. .de, .io) still succeed with DNS records and rdap_available:false. NXDOMAIN with no registration (404 DOMAIN_NOT_FOUND), upstream failure (502) and bad input (400) are not charged. Costs $0.003 USDC per call via x402.
domain_lookup_bulkBulk domain lookup: the same DNS + RDAP registration report as domain_lookup for up to 10 domains in one call (deduplicated).No findings
Why it is in this group
- The name "domain_lookup_bulk" says "lookup": a word for reading.
Description, as the server wrote it Bulk domain lookup: the same DNS + RDAP registration report as domain_lookup for up to 10 domains in one call (deduplicated). Per-domain errors are returned inline. Charged once ($0.01 USDC via x402) only if at least one domain succeeded; otherwise not charged.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 500
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 500.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 500
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 500; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 500
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
Tools2 added.+2 addedView diff
- Added:domain_lookupOnly reads
- Added:domain_lookup_bulkOnly reads
Install
Pinned to version 0.3.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http dns-auth-checker https://x402-dns-auth-checker.microtools-x402.workers.dev/mcpclaude mcp add --transport http dns-auth-checker https://x402-dns-auth-checker.microtools-x402.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dns-auth-checker__domain_lookup",
"mcp__dns-auth-checker__domain_lookup_bulk"
],
"ask": [
"mcp__dns-auth-checker__domain_auth_check",
"mcp__dns-auth-checker__health"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dns-auth-checker. Review it before you use it.
Capability tags behind 1 rule
- mcp__dns-auth-checker__domain_lookup private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.microtools-x402.x402-dns-auth-checker/dns-auth-checker/verify?hash=e8c091961b81253a9985cbd88b3cfe0b2e971484aef3c2c6c72071305f4bbd3e" | jq -e '.changed == false'Pinned hash e8c091961b81, from Nov 3, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.microtools-x402.x402-dns-auth-checker/dns-auth-checker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.microtools-x402.x402-dns-auth-checker/dns-auth-checker)Source: MCP Registry. Synced Nov 18, 2026, 12:17 UTC.
x402 Domain Lookup & DNS Email Auth MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the x402 Domain Lookup & DNS Email Auth MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the x402 Domain Lookup & DNS Email Auth MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the x402 Domain Lookup & DNS Email Auth MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the x402 Domain Lookup & DNS Email Auth MCP server have?
- 4 tools: 2 write, 2 read. domain_auth_check, health, domain_lookup and domain_lookup_bulk.
Does the x402 Domain Lookup & DNS Email Auth MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the x402 Domain Lookup & DNS Email Auth MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the x402 Domain Lookup & DNS Email Auth MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.