DomainCanary
REMOTE · DOMAINCANARY.COM
Check a domain's DMARC, SPF and DKIM, build SPF records, explain bounces, read DMARC reports.
Available components
Last scanned (12 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 current MCP spec version (2026-07-28).Pass
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
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 5 Nov 2026 · Probed https://domaincanary.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=domaincanary.com | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d262edb0163a18d50e64dd19e482d3eb |
| SANs: domaincanary.com, *.domaincanary.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 domaincanary.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| domaincanary.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://domaincanary.com/mcp | Verified | 200 | |
| http (plaintext) | http://domaincanary.com/mcp | HTTPS enforced | 308 | https://domaincanary.com/mcp |
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 →
analyze_report Read a DMARC aggregate report ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| analyzer_url | string|null | yes | – |
| external_data | object | yes | – |
| next_steps | array | yes | – |
| record_limit_reached | boolean | yes | – |
| reports | array | yes | – |
| reports_omitted | number | yes | – |
| skipped_payloads | number | yes | – |
No examples provided.
build_spf Build an SPF record ~305
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| added | array | yes | – |
| after | string|null | yes | – |
| domain | string|null | yes | – |
| external_data | object | yes | – |
| findings | array | yes | – |
| findings_omitted | integer | yes | – |
| lookups | integer | yes | – |
| no_include | array | yes | – |
| outcome | string | yes | – |
| over_limit | boolean | yes | – |
| published | boolean | yes | – |
| skipped | array | yes | – |
| unrecognised | integer | yes | – |
| url | string | yes | – |
No examples provided.
check_domain Check a domain's email authentication ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| dkim | object | yes | – |
| dmarc | object | yes | – |
| domain | string | yes | – |
| external_data | object | yes | – |
| records_to_publish | array | yes | – |
| spf | object | yes | – |
| url | string | yes | – |
| verdict | string | yes | – |
No examples provided.
explain_bounce Explain a bounce or SMTP error ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| change | string|null | yes | – |
| clears | string|null | yes | – |
| code | string|null | yes | – |
| faq | array | yes | – |
| matched | boolean | yes | – |
| meaning | string | yes | – |
| page | object | yes | – |
| related | array | yes | – |
No examples provided.
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.
remote · domaincanary.com
claude mcp add --transport http com-domaincanary-mcp 'https://domaincanary.com/mcp'
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.