email-deliverability-mc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DNS_SERVERS | No | Comma-separated resolver IPs for all other DNS lookups. | the system resolver |
| BLOCKLIST_DNS | No | Comma-separated IPs of a recursive resolver you run, used for blocklist lookups. | the system resolver |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_domainA | Check a domain's SPF (including the 10-DNS-lookup limit), DMARC policy and reporting, DKIM keys on common selectors, and MX records. Returns problems ranked by severity with the fix for each, plus the email services the domain uses. |
| check_sending_ipA | Check a mail server's IP: reverse DNS (PTR) and whether it resolves back to the IP, and listings on Spamhaus ZEN, Barracuda, SpamCop, PSBL, Mailspike and UCEPROTECT level 1. A refused Spamhaus query is reported as unknown, never as a listing. |
| check_email_headersA | Check a received email's headers against Gmail's and Yahoo's bulk sender requirements: SPF, DKIM and DMARC results, From domain alignment, one-click unsubscribe (and whether DKIM covers it), TLS, reverse DNS and Message-ID. Use the full headers as the recipient got them (Gmail: Show original). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.