DomainDNA MCP server
dev.workers.cybermax-tools.cybermax/domaindna-apicybermax.cybermax-tools.workers.devstreamable-httpv1.1.2Scanned
Tech stack, email security (SPF, DMARC, MX provider) and domain age API + MCP. 25 free domains/day.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DomainDNA MCP server can do
The DomainDNA MCP server is published by cybermax.cybermax-tools.workers.dev, a domain the MCP Registry verified. It has 4 tools. It can create or change data (4 tools: domain_report, email_security, tech_stack and domain_registration), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (domain_report, email_security, tech_stack and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.1.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 4Claude Code: ask
domain_registrationDomain registration only, for 1-10 domains, from the official RDAP registries.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Domain registration only, for 1-10 domains, from the official RDAP registries. Use this when you need to spot newly registered (possibly risky) domains, check who a domain is registered with, or find upcoming expiries. The fastest and cheapest tool here; no DNS, email or website checks (use domain_report for everything). Input: domains (1-10 domains, URLs or email addresses). Returns results[] with, per domain: registration (registrar, created, updated and expiry dates, age in days, status codes), errors, analyzedAt and cached. Limits: each domain counts as one lookup; answers cached for 1 hour per domain; 25 free domains a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored, no email is sent.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
- destructiveHint: false
- title: Domain age and registrar
domain_reportEverything about ONE domain in a single call.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Everything about ONE domain in a single call. Use this when you need to profile one company or website end to end (sales research, vendor or security review, due diligence). For several domains or only one aspect, use email_security, tech_stack or domain_registration instead (cheaper and faster). Input: domain (a domain, URL or email address). Returns check and results[0] with reachable, finalUrl, statusCode, title, description and language of the homepage; technologies[] (CMS, e-commerce, frameworks, analytics, CDN…, each with the evidence it was detected from); email (MX provider, SPF and DMARC policy); dns records and verification tokens; securityHeaders; registration (RDAP registrar, created and expiry dates, age); files (robots.txt, sitemap, llms.txt, security.txt); a one-line summary, analyzedAt and cached. exists tells whether the domain resolves; a site that blocks bots is flagged blocked=true. Limits: each domain counts as one lookup; answers cached for 1 hour per domain; 25 free domains a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored, no email is sent.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
- destructiveHint: false
- title: Full domain report
email_securityEmail and DNS setup only, for 1-5 domains.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Email and DNS setup only, for 1-5 domains. Use this when you need to check email deliverability or spoofing protection, or to see which email provider (Google Workspace, Microsoft 365…) a company uses. Does not fetch the website (use tech_stack) or registration data (use domain_registration). Input: domains (1-5 domains, URLs or email addresses). Returns results[] with, per domain: exists; email (MX hosts and provider, SPF record and its all qualifier, DMARC policy, pct and rua); dns (A/AAAA/NS records); verifications (services proven by TXT site-verification tokens, e.g. google, apple, atlassian); errors, analyzedAt and cached. Limits: each domain counts as one lookup; answers cached for 1 hour per domain; 25 free domains a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored, no email is sent.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
- destructiveHint: false
- title: Email provider, SPF and DMARC
tech_stackWebsite technologies only, for 1-3 sites.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Website technologies only, for 1-3 sites. Use this when you need to know what a website is built with, for lead qualification by technology or competitor research. Fetches each homepage once; no DNS, email or registration data (use email_security or domain_registration). Input: domains (1-3 domains or URLs). Returns results[] with, per site: reachable, blocked, finalUrl, statusCode, title, description, language; technologies[] (CMS, e-commerce platform, frameworks, analytics, tag managers, CDN, chat and more, each with category and the evidence it was detected from); securityHeaders the homepage sends; errors, analyzedAt and cached. Sites that block bots return blocked=true. Limits: each domain counts as one lookup; answers cached for 1 hour per domain; 25 free domains a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored, no email is sent.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
- idempotentHint: true
- destructiveHint: false
- title: Website tech stack
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 private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- 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, 19:26 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry: tools/list returned 4 tools to an anonymous client, including domain_report (write), email_security (write), tech_stack (write), domain_registration (write)
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http domaindna-api https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registryclaude mcp add --transport http domaindna-api https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registryRun 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": [],
"ask": [
"mcp__domaindna-api__domain_report",
"mcp__domaindna-api__email_security",
"mcp__domaindna-api__tech_stack",
"mcp__domaindna-api__domain_registration"
],
"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 domaindna-api. Review it before you use it.
Capability tags behind 4 rules
- mcp__domaindna-api__domain_report untrusted-input
- mcp__domaindna-api__email_security untrusted-input
- mcp__domaindna-api__tech_stack untrusted-input
- mcp__domaindna-api__domain_registration 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.cybermax-tools.cybermax/domaindna-api/verify?hash=1d509ef4636024569b04a3b4f621e3f7ffb98bc3c5d42886883f082b18ba9d90" | jq -e '.changed == false'Pinned hash 1d509ef46360, from Nov 17, 2026, 10:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.cybermax-tools.cybermax/domaindna-api/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.cybermax-tools.cybermax/domaindna-api)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
DomainDNA MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DomainDNA MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 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 DomainDNA MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the DomainDNA 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 DomainDNA MCP server have?
- 4 tools: 4 write. domain_report, email_security, tech_stack and domain_registration.
Does the DomainDNA MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the DomainDNA MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DomainDNA MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.