INDIVIDUAL MCP TOOL
check_mta_sts
Check MTA-STS (RFC 8461) for a domain: the _mta-sts TXT record (strict §3.1 selection — case-sensitive leading v=STSv1, exactly one record, required 1-32 alphanumeric id), the policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt fetched WITHOUT following redirects (§3.3), strict §3.2 policy validation (version/mode/max_age required, mx required unless mode none, max_age ≤ 31557600, duplicate keys first-wins), the policy-host X.509 certificate (§3.3 — an invalid cert means compliant senders fetch no policy), and live MX coverage against the mx: patterns (§4.1 — wildcards match exactly one leftmost label; coverage is all/partial/none, partial meaning strict senders skip the uncovered hosts per §5.1).
Input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests retrieving external content.
Parent endpoint
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tamingdns-com]
url = "https://tamingdns.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tamingdns-com": {
"type": "http",
"url": "https://tamingdns.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tamingdns-com
Remote MCP URL: https://tamingdns.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tamingdns-com": {
"url": "https://tamingdns.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tamingdns-com": {
"type": "http",
"url": "https://tamingdns.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tamingdns-com",
"transport": "streamable-http",
"url": "https://tamingdns.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
check_spf— Check the SPF record for a domain.check_dkim— Look up a DKIM public key at <selector>._domainkey.<domain> and validate it.check_dmarc— Check the _dmarc record for a domain with DUAL discovery: the RFC 7489 §6.6.3 organisational-domain ladder (what major receivers enforce today — grade/verdict anchor to it) AND the RFC 9989 §4.10 DNS Tree Walk (8-query cap, psd=n/y stop rules, fewest-labels org selection) into analysis.discovery {legacy, tree_walk, diverges}.check_tls_rpt— Check the TLS-RPT (SMTP TLS Reporting, RFC 8460) record at _smtp._tls.<domain>.check_bimi— Check default._bimi.<domain>: parses the BIMI record, validates the SVG Tiny-PS logo, inspects the VMC chain (expiry, EKU, SCT, issuer-accepted, SAN match, logotype hash), and verifies the DMARC prerequisite (p=quarantine/reject at pct=100 — the RFC 7489 reading Gmail and Apple Mail evaluate today).check_dane— Check SMTP DANE / TLSA records for a domain (RFC 7672).check_dnssec— Validate a domain's DNSSEC chain of trust.check_mx— Inspect a domain's MX / mail-routing posture.