email-deliverability-mc
Related Servers
Alternatives to email-deliverability-mc
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables auditing any domain's email deliverability and DNS health, including SPF, DKIM, DMARC, MX, mail provider, DNS blacklist status, catch-all, domain age, and a deliverability score.1126 npm1MIT
- AlicenseAqualityBmaintenanceProvides comprehensive email deliverability and domain registration analysis, evaluating SPF, DKIM, DMARC, DNS records, and expiry to identify issues and suggest fixes.51MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to audit a domain's email-authentication DNS configuration—covering SPF, DKIM, DMARC, MX, BIMI, MTA-STS, and TLS-RPT—and receive issues, recommendations, a 0–100 score, and A–F grade.MIT
- AlicenseNot gradedqualityCmaintenanceAudits email deliverability configuration for a domain, checking SPF, DKIM, DMARC, and MX records, returning a score and recommendations.MIT
- AlicenseAqualityDmaintenanceMCP server for email deliverability: validate SPF/DKIM/DMARC/BIMI, check blacklists, test SMTP/IMAP, look up DNS, and generate ready-to-deploy records for any major email provider. Ships with two one-click prompts (audit-deliverability, setup-dns). Public, no auth.17MIT
- AlicenseNot gradedqualityCmaintenanceEnables checking email deliverability for domains or IPs, tracking IP reputation over time, and analyzing bounce patterns and issues.MIT
TDQS
Scored across 3 tools
Each tool takes a fundamentally different input type: a domain, a sending IP, or an email's raw headers. There is no plausible way to confuse check_domain with check_sending_ip or check_email_headers, and the descriptions reinforce the boundary by listing what each inspects.
All three tools use the identical check_<noun> pattern with nouns that accurately describe the target (domain, sending_ip, email_headers). The convention is predictable and would extend cleanly if more checks were added.
Three tools is lean but each maps to a distinct diagnostic axis (domain auth, IP reputation, message-level compliance), so none is filler. It is on the sparse side of the 3-15 range for the breadth of email deliverability, but not thin enough to be a real mismatch.
The surface covers the three core pillars: domain authentication records, IP reputation/blocklists, and header-level bulk-sender compliance, all with actionable severity-ranked fixes. Minor gaps remain, such as BIMI/MTA-STS/TLS-RPT checks, DMARC aggregate report analysis, and batch checking of multiple domains or IP ranges, but agents can work around these.