MailX Email Deliverability
Server Details
Check SPF/DKIM/DMARC/BIMI, blacklists, SMTP/IMAP; DNS lookups; generate email DNS records.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 16 of 16 tools scored.
Each tool targets a distinct aspect of email deliverability, such as specific DNS records (BIMI, DKIM, DMARC, SPF, etc.), server connectivity (IMAP, SMTP), or record generation. Overlap is minimal and clarified by descriptions, e.g., dns_lookup covers all records but each specialized check is more focused.
All tools follow a consistent pattern: `<record/protocol>_<operation>` (e.g., bimi_check, dmarc_generate, imap_finder, mx_lookup). Operations are verbs like check, lookup, generate, finder, making names predictable and easy to understand.
16 tools is appropriate for the domain of email deliverability, covering DNS checks, record generation, and server configuration testing. The count feels well-scoped without being overwhelming or sparse.
The tool set covers core deliverability checks (DNS records, blacklists, server connectivity) and provides generation for SPF and DMARC. Minor gaps exist, such as no tool for DKIM key generation or spam content analysis, but these are not essential for the primary use case.
Available Tools
16 toolsbimi_checkBIMI CheckRead-onlyIdempotentInspect
Check if a domain has a valid BIMI (Brand Indicators for Message Identification) DNS record. BIMI allows brands to display their logo next to authenticated emails in supporting email clients.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to check BIMI records for, e.g. example.com |
blacklist_checkBlacklist CheckRead-onlyIdempotentInspect
Check if a domain or IP address is listed in popular email blacklists (DNSBLs). Being blacklisted can severely impact email deliverability.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain name or IP address to check against blacklists, e.g. example.com or 1.2.3.4 |
cname_lookupCNAME LookupRead-onlyIdempotentInspect
Look up CNAME (Canonical Name) records for a domain. Shows where a hostname aliases to.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to look up CNAME records for, e.g. www.example.com |
dkim_checkDKIM CheckRead-onlyIdempotentInspect
Check if a domain has a valid DKIM (DomainKeys Identified Mail) DNS record for a given selector. DKIM allows the receiver to verify that an email was sent by the domain owner.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to check DKIM records for, e.g. example.com | |
| dkim_selector | Yes | The DKIM selector to look up, e.g. google, default, selector1 |
dmarc_checkDMARC CheckRead-onlyIdempotentInspect
Check if a domain has a valid DMARC (Domain-based Message Authentication, Reporting & Conformance) DNS record. DMARC tells receiving servers what to do with emails that fail SPF or DKIM checks.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to check DMARC records for, e.g. example.com |
dmarc_generateDMARC GeneratorIdempotentInspect
Generate a DMARC DNS record for a domain. Returns the record name, value, and type ready to be added to DNS.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | The email address to receive DMARC aggregate reports, e.g. dmarc@example.com | ||
| domain_name | Yes | The domain to generate a DMARC record for, e.g. example.com | |
| dmarc_policy | Yes | The DMARC policy: none (monitor only), quarantine (mark as spam), or reject (block entirely) |
dns_lookupDNS LookupRead-onlyIdempotentInspect
Look up all DNS records for a domain in one query. Returns A, AAAA, CNAME, MX, NS, TXT, and SOA records.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to look up all DNS records for, e.g. example.com |
imap_checkIMAP CheckIdempotentInspect
Test an IMAP server connection by attempting to connect and authenticate. Use this to verify email receiving configuration.
| Name | Required | Description | Default |
|---|---|---|---|
| password | Yes | The IMAP password or app-specific password | |
| username | Yes | The IMAP username for authentication | |
| imap_host | Yes | The IMAP server hostname, e.g. imap.gmail.com | |
| imap_port | Yes | The IMAP port number, e.g. 993 for SSL, 143 for unencrypted | |
| imap_encryption | Yes | The encryption protocol: ssl, tls, or none |
imap_finderIMAP FinderRead-onlyIdempotentInspect
Look up IMAP server settings (host, port, encryption) for a given email provider. Use this to find the correct IMAP configuration for services like Gmail, Outlook, Yahoo, etc.
| Name | Required | Description | Default |
|---|---|---|---|
| imap_provider_name | Yes | The email provider name to look up, e.g. gmail, outlook, yahoo |
mx_lookupMX LookupRead-onlyIdempotentInspect
Look up MX (Mail Exchanger) records for a domain. Returns the mail servers and their priorities.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to look up MX records for, e.g. example.com |
ptr_lookupPTR LookupRead-onlyIdempotentInspect
Reverse DNS lookup. Find the hostname associated with an IP address. A valid PTR record is important for email sending reputation.
| Name | Required | Description | Default |
|---|---|---|---|
| ip_address | Yes | The IP address to look up, e.g. 8.8.8.8 or 142.250.80.46 |
smtp_checkSMTP CheckIdempotentInspect
Test an SMTP server connection by attempting to connect and authenticate. If from_email and to_email are provided, the tool may attempt to send a test email. Only provide these fields if you are authorized to send from the account and intentionally want to test full sending capability.
| Name | Required | Description | Default |
|---|---|---|---|
| host | Yes | The SMTP server hostname, e.g. smtp.gmail.com | |
| port | Yes | The SMTP port number, e.g. 587 for TLS, 465 for SSL, 25 for unencrypted | |
| password | Yes | The SMTP password or app-specific password | |
| to_email | No | Optional recipient email address for sending a test email | |
| username | Yes | The SMTP username for authentication | |
| encryption | Yes | The encryption protocol: ssl, tls, or none | |
| from_email | No | Optional sender email address for sending a test email |
smtp_finderSMTP FinderRead-onlyIdempotentInspect
Look up SMTP server settings (host, port, encryption) for a given email provider. Use this to find the correct SMTP configuration for services like Gmail, Outlook, SendGrid, etc.
| Name | Required | Description | Default |
|---|---|---|---|
| provider_name | Yes | The email provider name to look up, e.g. gmail, sendgrid, mailgun, outlook |
spf_checkSPF CheckRead-onlyIdempotentInspect
Check if a domain has a valid SPF (Sender Policy Framework) DNS record. SPF specifies which mail servers are authorized to send email on behalf of a domain.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to check SPF records for, e.g. example.com |
spf_generateSPF GeneratorIdempotentInspect
Generate an SPF DNS record for a domain based on the email provider being used. Returns the record name, value, and type ready to be added to DNS.
| Name | Required | Description | Default |
|---|---|---|---|
| provider | Yes | The mail provider identifier, e.g. google, mailgun, sendgrid, postmark, amazon-ses | |
| domain_name | Yes | The domain to generate an SPF record for, e.g. example.com | |
| hard_fail_boolean | Yes | If true, uses strict -all policy (reject unauthorized senders). If false, uses soft ~all (mark but deliver). |
txt_lookupTXT LookupRead-onlyIdempotentInspect
Look up all TXT records for a domain. TXT records contain SPF policies, domain verification tokens, DKIM keys, and other metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| domain_name | Yes | The domain to look up TXT records for, e.g. example.com |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!