# DomainCanary (remote · domaincanary.com)

Check a domain's DMARC, SPF and DKIM, build SPF records, explain bounces, read DMARC reports.

- Trust score: 86/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://domaincanary.com/mcp`
- 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-11-05.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 910 tokens (~227/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**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 current MCP spec version (2026-07-28).

## Install

### How do I install the DomainCanary MCP server?

DomainCanary is a hosted endpoint at https://domaincanary.com/mcp, 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-domaincanary-mcp 'https://domaincanary.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-domaincanary-mcp": {
      "url": "https://domaincanary.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-domaincanary-mcp]
url = "https://domaincanary.com/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-domaincanary-mcp:
    url: "https://domaincanary.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

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

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-11-02 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 86, +1)

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

### 2026-10-29 (score 85, +1)

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

### 2026-10-27 (score 84, +1)

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

### 2026-10-25 (score 83, +1)

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

### 2026-10-23 (score 82, +1)

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

### 2026-10-21 (score 81, +1)

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

### 2026-10-19 (score 80, +1)

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

## MCP tools (4)

### `check_domain` (~166 tokens)

Check a domain's email authentication

Use this when someone asks whether a domain's email authentication is set up correctly, why mail from a domain fails DMARC, SPF or DKIM, or which DNS records to publish for it. Reads the domain's live DMARC, SPF and DKIM records and returns what is wrong with each, plus the records to add or change. Pass a DKIM selector when you know it. Without one, common selectors are tried. Takes a domain name only, not a mailbox address or an IP address.

Input parameters:

- `domain` (string, required): The domain to check, such as example.com. A URL is cut down to its host.
- `selector` (string): The DKIM selector, the s= value in a DKIM-Signature header. Leave it out to try common ones.

Output parameters:

- `dkim` (object)
- `dmarc` (object)
- `domain` (string)
- `external_data` (object)
- `records_to_publish` (array)
- `spf` (object)
- `url` (string)
- `verdict` (string)

### `build_spf` (~305 tokens)

Build an SPF record

Use this when someone lists the services that send their email and wants the SPF record to publish, or wants a sender added to the SPF record they already have. Takes provider names such as Google Workspace or Mailchimp, include terms such as include:spf.example.com, or IP addresses, and returns one merged record with its count of DNS lookups against the limit of ten. Pass the domain when you know it, so the result includes the senders already in its published record.

Input parameters:

- `all` (string): How the record ends. A new record ends in ~all unless you pass -all. A record the domain already publishes keeps its own ending unless you pass one.
- `domain` (string): The domain the record is for. When given, the SPF record it publishes today is read and the senders are added to it, so nothing already in it is lost.
- `ip4` (array): IPv4 addresses or ranges that send this domain's mail directly, such as 192.0.2.10 or 192.0.2.0/24.
- `ip6` (array): IPv6 addresses or ranges that send this domain's mail directly, such as 2001:db8::1 or 2001:db8::/32.
- `senders` (array, required): The platforms that send this domain's mail: provider names such as Google Workspace or Mailchimp, or include terms such as include:spf.example.com.

Output parameters:

- `added` (array)
- `after` (string|null)
- `domain` (string|null)
- `external_data` (object)
- `findings` (array)
- `findings_omitted` (integer)
- `lookups` (integer)
- `no_include` (array)
- `outcome` (string)
- `over_limit` (boolean)
- `published` (boolean)
- `skipped` (array)
- `unrecognised` (integer)
- `url` (string)

### `explain_bounce` (~129 tokens)

Explain a bounce or SMTP error

Use this when someone pastes a bounce message, an SMTP reply such as 550 5.7.26, or an Authentication-Results header and asks what it means or how to fix it. Returns what the receiving server refused, what to change, when it clears, and the page that explains it. Works from the pasted text alone and reads no DNS records.

Input parameters:

- `text` (string, required): The bounce message, the SMTP reply or the Authentication-Results line, as pasted. When the bounce runs past 4,000 characters, pass the lines with the error code and the reason.

Output parameters:

- `change` (string|null)
- `clears` (string|null)
- `code` (string|null)
- `faq` (array)
- `matched` (boolean)
- `meaning` (string)
- `page` (object)
- `related` (array)

### `analyze_report` (~201 tokens)

Read a DMARC aggregate report

Use this when someone has a DMARC aggregate report and wants to know which senders passed and which failed. The report is the XML, .gz or .zip file that receivers such as Google and Yahoo email to the address in a domain's rua tag. In ChatGPT, pass the uploaded file. Elsewhere, pass the report XML as text. Returns totals per report and each sending IP address with its SPF, DKIM and DMARC results. The result gives a next step for the report's domain and a link to a live check of that domain's DNS records. Nothing from the report is stored.

Input parameters:

- `file` (object): The report file the user uploaded in ChatGPT: the .xml, .xml.gz or .zip a mailbox provider emailed them.
- `report_xml` (string): The report XML as text, from <feedback> to </feedback>. Use this when there is no uploaded file, or when the user pasted the XML.

Output parameters:

- `analyzer_url` (string|null)
- `external_data` (object)
- `next_steps` (array)
- `record_limit_reached` (boolean)
- `reports` (array)
- `reports_omitted` (number)
- `skipped_payloads` (number)

## Diagnostics

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

## Score history

- 2026-11-05: 86
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 86
- 2026-10-31: 85
- 2026-10-30: 85
- 2026-10-29: 85
- 2026-10-28: 84
- 2026-10-27: 84
- 2026-10-26: 83
- 2026-10-25: 83
- 2026-10-24: 82
- 2026-10-23: 82
- 2026-10-22: 81
- 2026-10-21: 81
- 2026-10-20: 80
- 2026-10-19: 80
- 2026-10-18: 79
- 2026-10-17: 79
- 2026-10-16: 78
- 2026-10-15: 78
- 2026-10-14: 78
- 2026-10-13: 77
- 2026-10-12: 77
- 2026-10-11: 76
- 2026-10-10: 76
- 2026-10-07: 74
- 2026-10-06: 74
- 2026-10-04: 73

## Common questions

### What is the DomainCanary MCP server?

DomainCanary is an MCP server listed in the public MCP registry as com.domaincanary/mcp. Check a domain's DMARC, SPF and DKIM, build SPF records, explain bounces, read DMARC reports. This page covers its hosted endpoint (https://domaincanary.com/mcp).

### Is the DomainCanary MCP server safe to use?

DomainCanary scores 86 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 DomainCanary MCP server expose?

DomainCanary exposes 4 tools: check_domain, build_spf, explain_bounce, analyze_report. Their descriptions and schemas cost roughly 801 tokens of context every time the server is loaded.

### Does the DomainCanary MCP server require authentication?

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

### Is the DomainCanary MCP server still maintained?

DomainCanary is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DomainCanary MCP server?

VerifyMCP ran 13 checks on DomainCanary, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://domaincanary.com/mcp
- Website: https://domaincanary.com/guides/check-your-domain-from-chatgpt-or-claude
- Changelog RSS feed: https://verifymcp.io/servers/com-domaincanary-mcp/domaincanary.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-domaincanary-mcp/domaincanary/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-domaincanary-mcp/domaincanary.json
- HTML version of this page: https://verifymcp.io/servers/com-domaincanary-mcp/domaincanary