DomainCanary

Name: DomainCanary
Author: com.domaincanary

MCP serverMCP

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

by com.domaincanaryhomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"domaincanary","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability25/25 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	105 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
8 h ago	mcp initialize	ok	200	140 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
14 h ago	mcp initialize	ok	200	111 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
20 h ago	mcp initialize	ok	200	107 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
27 h ago	mcp initialize	ok	200	129 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
33 h ago	mcp initialize	ok	200	121 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	111 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	144 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	99 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools
2 d ago	mcp initialize	ok	200	119 ms	server domaincanary 1.0.0 · protocol 2025-06-18 · 4 tools

Tools observed via MCP handshake

check_domain — 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
build_spf — 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.
explain_bounce — 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. Re
analyze_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 receive

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

productivity.emailEmail95%analytics.reportingReporting & Dashboards89%security.identityIdentity & Access58%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.domaincanary/mcp

first seen 7 d ago · fetched 20 h agoopen ↗

Field history (6 recent events)

7 d ago · declared · summary → "Check a domain's DMARC, SPF and DKIM, build SPF records, explain bounces, read DMARC reports."
7 d ago · declared · description → "Check a domain's DMARC, SPF and DKIM, build SPF records, explain bounces, read DMARC reports."
7 d ago · declared · publisherName → "com.domaincanary"
7 d ago · declared · homepageUrl → "https://domaincanary.com/guides/check-your-domain-from-chatgpt-or-claude"
7 d ago · declared · version → "1.0.0"
7 d ago · declared · protocols → ["mcp"]