DomainDNA
REMOTE · DOMAINDNA-API.CYBERMAXTOOLS.COM · SCANNED OCT 14
Tech stack, email security (SPF, DMARC, MX provider) and domain age API + MCP. 25 free domains/day.
Available components
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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1032 tokens (~258/item across 4 items; 4 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 Management17
- Stability observed for 5 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the DomainDNA MCP server?
DomainDNA is a hosted endpoint at https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry, 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 · domaindna-api.cybermaxtools.com
claude mcp add --transport http dev-workers-cybermax-tools-cybermax-domaindna-ap 'https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry'
{
"mcpServers": {
"dev-workers-cybermax-tools-cybermax-domaindna-ap": {
"url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
}
}
} {
"servers": {
"dev-workers-cybermax-tools-cybermax-domaindna-ap": {
"type": "http",
"url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
}
}
} [mcp_servers.dev-workers-cybermax-tools-cybermax-domaindna-ap] url = "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-workers-cybermax-tools-cybermax-domaindna-ap": {
"type": "remote",
"url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry",
"enabled": true
}
}
} openclaw mcp add dev-workers-cybermax-tools-cybermax-domaindna-ap --url 'https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry' --transport streamable-http
mcp_servers:
dev-workers-cybermax-tools-cybermax-domaindna-ap:
url: "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry" {
"McpServers": {
"dev-workers-cybermax-tools-cybermax-domaindna-ap": {
"Transport": "http",
"Url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
}
}
} assistant mcp add dev-workers-cybermax-tools-cybermax-domaindna-ap -t streamable-http -u 'https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry'
{
"mcpServers": {
"dev-workers-cybermax-tools-cybermax-domaindna-ap": {
"type": "http",
"url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −1
- Tool “domain_registration” rewrote its description, which is the text the model reads security
- Tool “domain_report” rewrote its description, which is the text the model reads security
- Tool “email_security” rewrote its description, which is the text the model reads security
- Tool “tech_stack” rewrote its description, which is the text the model reads security
- Schema quality: 136 → 258 ▼ functional
- “tech_stack” reworded the description of “domains” cosmetic
- “domain_registration” reworded the description of “domains” cosmetic
- “email_security” reworded the description of “domains” cosmetic
- 10 Oct 26 72
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 14 Oct 2026 · Probed https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cybermaxtools.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb3f3e5f76ac8b42134f783215d505ce |
| SANs: cybermaxtools.com, domaindna-api.cybermaxtools.com, *.domaindna-api.cybermaxtools.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 domaindna-api.cybermaxtools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cybermaxtools.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://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry | Verified | 200 | |
| http (plaintext) | http://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry | HTTPS enforced | 301 | https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry |
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 →
domain_registration Domain age and registrar ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | 1-10 domains, website URLs or email addresses (the domain part is used) |
No output schema declared.
No examples provided.
domain_report Full domain report ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | One domain, URL or email address, e.g. stripe.com, https://stripe.com/pricing or ops@stripe.com (the domain part is used) |
No output schema declared.
No examples provided.
email_security Email provider, SPF and DMARC ~235
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | 1-5 domains, website URLs or email addresses (the domain part is used) |
No output schema declared.
No examples provided.
tech_stack Website tech stack ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | 1-3 domains, website URLs or email addresses (the domain part is used) |
No output schema declared.
No examples provided.
What is the DomainDNA MCP server?
DomainDNA is an MCP server listed in the public MCP registry as dev.workers.cybermax-tools.cybermax/domaindna-api. Tech stack, email security (SPF, DMARC, MX provider) and domain age API + MCP. 25 free domains/day. This page covers its hosted endpoint (https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry).
Is the DomainDNA MCP server safe to use?
DomainDNA 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 DomainDNA MCP server expose?
DomainDNA exposes 4 tools: domain_report, email_security, tech_stack, domain_registration. Their descriptions and schemas cost roughly 961 tokens of context every time the server is loaded.
Does the DomainDNA MCP server require authentication?
No. We connected to DomainDNA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DomainDNA MCP server still maintained?
DomainDNA is still listed as active in the MCP registry. We last reached this channel on 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.