# DomainDNA (remote · domaindna-api.cybermaxtools.com)

Tech stack, email security (SPF, DMARC, MX provider) and domain age API + MCP. 25 free domains/day.

- Trust score: 76/100 (medium)
- Change this week: +14
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `domaindna-api.cybermaxtools.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-domaindna-api/domaindna-api-2.md), [page](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-domaindna-api/domaindna-api-2)

## Channel facts

- Endpoint: `https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-workers-cybermax-tools-cybermax-domaindna-ap 'https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-domaindna-ap": {
      "url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-cybermax-tools-cybermax-domaindna-ap": {
      "type": "http",
      "url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-cybermax-tools-cybermax-domaindna-ap]
url = "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add dev-workers-cybermax-tools-cybermax-domaindna-ap --url 'https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-cybermax-tools-cybermax-domaindna-ap:
    url: "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-cybermax-tools-cybermax-domaindna-ap": {
      "Transport": "http",
      "Url": "https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-cybermax-tools-cybermax-domaindna-ap -t streamable-http -u 'https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 73, +11)

- [security improvement] Transport: fail → pass

### 2026-10-15 (score 62, −10)

- [security regression] Transport: pass → fail

### 2026-10-14 (score 72, +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.

### 2026-10-12 (score 71, −1)

- [security] Tool “tech_stack” rewrote its description, which is the text the model reads
- [security] 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
- [functional regression] Schema quality: 136 → 258
- [cosmetic] “email_security” reworded the description of “domains”
- [cosmetic] “tech_stack” reworded the description of “domains”
- [cosmetic] “domain_registration” reworded the description of “domains”

### 2026-10-10 (score 72)

First indexed and scored.

## MCP tools (4)

### `domain_report` (~293 tokens)

Full domain report

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.

Input parameters:

- `domain` (string, required): One domain, URL or email address, e.g. stripe.com, https://stripe.com/pricing or ops@stripe.com (the domain part is used)

### `email_security` (~235 tokens)

Email provider, SPF and DMARC

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.

Input parameters:

- `domains` (array, required): 1-5 domains, website URLs or email addresses (the domain part is used)

### `tech_stack` (~230 tokens)

Website tech stack

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.

Input parameters:

- `domains` (array, required): 1-3 domains, website URLs or email addresses (the domain part is used)

### `domain_registration` (~203 tokens)

Domain age and registrar

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.

Input parameters:

- `domains` (array, required): 1-10 domains, website URLs or email addresses (the domain part is used)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-domaindna-api/domaindna-api-2#diagnostics

## Score history

- 2026-10-22: 76
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 62
- 2026-10-14: 72
- 2026-10-13: 71
- 2026-10-12: 71
- 2026-10-10: 72

## Common questions

### 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 76 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 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://domaindna-api.cybermaxtools.com/mcp?via=mcp-registry
- Repository: https://gitlab.com/CyberMax.tools/agent-tools
- Website: https://cybermaxtools.com/store/domaindna-api/?s=mcp-registry-domaindna-api
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-domaindna-api/domaindna-api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-domaindna-api/domaindna-api-2.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-domaindna-api/domaindna-api-2