# Domain Health (remote · mcp.modernmustardseed.com)

Domain checks: SPF, DKIM, DMARC, BIMI, MTA-STS, SSL/TLS and HTTP security headers.

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

## Components

- remote · `mcp.modernmustardseed.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-modernmustardseed-domain-health/domain-health.md), [page](https://verifymcp.io/servers/com-modernmustardseed-domain-health/domain-health)

## Channel facts

- Endpoint: `https://mcp.modernmustardseed.com/domain-health`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 80/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1116 tokens (~223/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Domain Health MCP server?

Domain Health is a hosted endpoint at https://mcp.modernmustardseed.com/domain-health, 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 com-modernmustardseed-domain-health 'https://mcp.modernmustardseed.com/domain-health'
```

### Cursor

```json
{
  "mcpServers": {
    "com-modernmustardseed-domain-health": {
      "url": "https://mcp.modernmustardseed.com/domain-health"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-modernmustardseed-domain-health": {
      "type": "http",
      "url": "https://mcp.modernmustardseed.com/domain-health"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-modernmustardseed-domain-health]
url = "https://mcp.modernmustardseed.com/domain-health"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-modernmustardseed-domain-health": {
      "type": "remote",
      "url": "https://mcp.modernmustardseed.com/domain-health",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-modernmustardseed-domain-health --url 'https://mcp.modernmustardseed.com/domain-health' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-modernmustardseed-domain-health:
    url: "https://mcp.modernmustardseed.com/domain-health"
```

### Netclaw

```json
{
  "McpServers": {
    "com-modernmustardseed-domain-health": {
      "Transport": "http",
      "Url": "https://mcp.modernmustardseed.com/domain-health"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-modernmustardseed-domain-health -t streamable-http -u 'https://mcp.modernmustardseed.com/domain-health'
```

### Other

```json
{
  "mcpServers": {
    "com-modernmustardseed-domain-health": {
      "type": "http",
      "url": "https://mcp.modernmustardseed.com/domain-health"
    }
  }
}
```

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 77, +1)

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

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

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

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

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

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

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

### 2026-10-14 (score 73, +1)

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

### 2026-10-13 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (5)

### `check_email_auth` (~251 tokens)

Check email authentication

Explain in plain words whether email from a domain will reach the inbox and whether others can forge it. Checks MX, SPF with every include expanded and counted against the 10-lookup limit, DMARC policy, alignment and report permissions, DKIM keys at about 40 common selectors plus any you name (with key size), BIMI, MTA-STS and TLS-RPT, and the DNS rules Google, Yahoo and Microsoft set for bulk senders. Every finding has a severity, a one-sentence fix and the RFC or provider document behind it. Reads public DNS only.

Input parameters:

- `detail` (string): "summary" (default) lists only findings that need action; "full" also lists every passing check.
- `dkim_selectors` (array): Extra DKIM selectors to check, such as the s= value from a DKIM-Signature header (for example "s1" or "selector1"). About 40 common selectors are always checked.
- `domain` (string, required): The domain to check, such as example.com. A website address (https://www.example.com/page) or an email address (jo@example.com) also works; the domain is taken from it.

### `check_ssl` (~202 tokens)

Check SSL certificate

Check the HTTPS certificate and TLS setup of a domain on port 443: issuer, expiry date and days left, whether the chain is complete and trusted, whether the certificate matches the name, key type and size, which TLS versions (1.0 to 1.3) the server accepts, and the CAA record that limits who may issue certificates. Checks www as well when given a bare domain. Every finding has a severity, a fix and a citation.

Input parameters:

- `detail` (string): "summary" (default) lists only findings that need action; "full" also lists every passing check.
- `domain` (string, required): The domain to check, such as example.com. A website address (https://www.example.com/page) or an email address (jo@example.com) also works; the domain is taken from it.
- `include_www` (boolean): Also check www.<domain> when a bare domain is given and www exists. Default true.

### `check_security_headers` (~180 tokens)

Check security headers

Read the HTTP security headers a domain's homepage sends, as a browser receives them, and grade each: Strict-Transport-Security, Content-Security-Policy, clickjacking protection (X-Frame-Options or CSP frame-ancestors), X-Content-Type-Options, Referrer-Policy and Permissions-Policy, plus whether http:// redirects to https://, cookie flags, and software version disclosure. Only public web servers on ports 80 and 443 are contacted.

Input parameters:

- `detail` (string): "summary" (default) lists only findings that need action; "full" also lists every passing check.
- `domain` (string, required): The domain to check, such as example.com. A website address (https://www.example.com/page) or an email address (jo@example.com) also works; the domain is taken from it.

### `check_domain_registration` (~175 tokens)

Check domain registration

Read a domain's public registration record from its registry over RDAP (no WHOIS scraping): registrar, creation, expiry and last-change dates, status locks such as clientTransferProhibited, danger states such as redemption period or hold, and nameservers. Also compares the registry's nameservers with the live zone and checks DNSSEC. Subdomains are checked as their registered domain. Some country-code registries do not publish RDAP; the tool says so.

Input parameters:

- `detail` (string): "summary" (default) lists only findings that need action; "full" also lists every passing check.
- `domain` (string, required): The domain to check, such as example.com. A website address (https://www.example.com/page) or an email address (jo@example.com) also works; the domain is taken from it.

### `full_domain_report` (~219 tokens)

Full domain report

Run every Domain Health check on one domain at once (email authentication, SSL and TLS, security headers, registration and DNSSEC) and answer three questions in plain words: will its email land, is its website safe, and is the domain owned well. Returns a score and grade per area, the top fixes across all areas, and every finding with its severity, fix and citation. Takes 5 to 20 seconds.

Input parameters:

- `detail` (string): "summary" (default) lists only findings that need action; "full" also lists every passing check.
- `dkim_selectors` (array): Extra DKIM selectors to check, such as the s= value from a DKIM-Signature header (for example "s1" or "selector1"). About 40 common selectors are always checked.
- `domain` (string, required): The domain to check, such as example.com. A website address (https://www.example.com/page) or an email address (jo@example.com) also works; the domain is taken from it.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-modernmustardseed-domain-health/domain-health#diagnostics

## Score history

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

## Common questions

### What is the Domain Health MCP server?

Domain Health is an MCP server listed in the public MCP registry as com.modernmustardseed/domain-health. Domain checks: SPF, DKIM, DMARC, BIMI, MTA-STS, SSL/TLS and HTTP security headers. This page covers its hosted endpoint (https://mcp.modernmustardseed.com/domain-health).

### Is the Domain Health MCP server safe to use?

Domain Health scores 77 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 Domain Health MCP server expose?

Domain Health exposes 5 tools: check_email_auth, check_ssl, check_security_headers, check_domain_registration, full_domain_report. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.

### Does the Domain Health MCP server require authentication?

No. We connected to Domain Health without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Domain Health MCP server still maintained?

Domain Health 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://mcp.modernmustardseed.com/domain-health
- Website: https://mcp.modernmustardseed.com/docs/domain-health
- Changelog RSS feed: https://verifymcp.io/servers/com-modernmustardseed-domain-health/domain-health.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-modernmustardseed-domain-health/domain-health.json
- HTML version of this page: https://verifymcp.io/servers/com-modernmustardseed-domain-health/domain-health