# MailX Email Deliverability (remote · themailx.com)

Check SPF/DKIM/DMARC/BIMI, blacklists, SMTP/IMAP; DNS lookups; generate email DNS records.

- Trust score: 76/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `themailx.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-themailx-email-deliverability/themailx.md), [page](https://verifymcp.io/servers/com-themailx-email-deliverability/themailx)

## Channel facts

- Endpoint: `https://themailx.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 89/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1483 tokens (~82/item across 18 items; 16 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-themailx-email-deliverability https://themailx.com/mcp
```

### Codex

```toml
[mcp_servers.com-themailx-email-deliverability]
url = "https://themailx.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-themailx-email-deliverability": {
      "type": "remote",
      "url": "https://themailx.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-themailx-email-deliverability --url https://themailx.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-themailx-email-deliverability:
    url: "https://themailx.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-themailx-email-deliverability": {
      "type": "http",
      "url": "https://themailx.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 71, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 71)

First indexed and scored.

## MCP tools (16)

### `spf_check` (~62 tokens)

SPF Check

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.

Input parameters:

- `domain_name` (string, required): The domain to check SPF records for, e.g. example.com

### `dkim_check` (~97 tokens)

DKIM Check

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.

Input parameters:

- `dkim_selector` (string, required): The DKIM selector to look up, e.g. google, default, selector1
- `domain_name` (string, required): The domain to check DKIM records for, e.g. example.com

### `dmarc_check` (~73 tokens)

DMARC Check

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.

Input parameters:

- `domain_name` (string, required): The domain to check DMARC records for, e.g. example.com

### `bimi_check` (~67 tokens)

BIMI Check

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.

Input parameters:

- `domain_name` (string, required): The domain to check BIMI records for, e.g. example.com

### `dmarc_generate` (~115 tokens)

DMARC Generator

Generate a DMARC DNS record for a domain. Returns the record name, value, and type ready to be added to DNS.

Input parameters:

- `dmarc_policy` (string, required): The DMARC policy: none (monitor only), quarantine (mark as spam), or reject (block entirely)
- `domain_name` (string, required): The domain to generate a DMARC record for, e.g. example.com
- `email` (string, required): The email address to receive DMARC aggregate reports, e.g. dmarc@example.com

### `spf_generate` (~126 tokens)

SPF Generator

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.

Input parameters:

- `domain_name` (string, required): The domain to generate an SPF record for, e.g. example.com
- `hard_fail_boolean` (boolean, required): If true, uses strict -all policy (reject unauthorized senders). If false, uses soft ~all (mark but deliver).
- `provider` (string, required): The mail provider identifier, e.g. google, mailgun, sendgrid, postmark, amazon-ses

### `smtp_check` (~186 tokens)

SMTP Check

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.

Input parameters:

- `encryption` (string, required): The encryption protocol: ssl, tls, or none
- `from_email` (string): Optional sender email address for sending a test email
- `host` (string, required): The SMTP server hostname, e.g. smtp.gmail.com
- `password` (string, required): The SMTP password or app-specific password
- `port` (integer, required): The SMTP port number, e.g. 587 for TLS, 465 for SSL, 25 for unencrypted
- `to_email` (string): Optional recipient email address for sending a test email
- `username` (string, required): The SMTP username for authentication

### `imap_check` (~128 tokens)

IMAP Check

Test an IMAP server connection by attempting to connect and authenticate. Use this to verify email receiving configuration.

Input parameters:

- `imap_encryption` (string, required): The encryption protocol: ssl, tls, or none
- `imap_host` (string, required): The IMAP server hostname, e.g. imap.gmail.com
- `imap_port` (integer, required): The IMAP port number, e.g. 993 for SSL, 143 for unencrypted
- `password` (string, required): The IMAP password or app-specific password
- `username` (string, required): The IMAP username for authentication

### `smtp_finder` (~75 tokens)

SMTP Finder

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.

Input parameters:

- `provider_name` (string, required): The email provider name to look up, e.g. gmail, sendgrid, mailgun, outlook

### `imap_finder` (~75 tokens)

IMAP Finder

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.

Input parameters:

- `imap_provider_name` (string, required): The email provider name to look up, e.g. gmail, outlook, yahoo

### `blacklist_check` (~71 tokens)

Blacklist Check

Check if a domain or IP address is listed in popular email blacklists (DNSBLs). Being blacklisted can severely impact email deliverability.

Input parameters:

- `domain_name` (string, required): The domain name or IP address to check against blacklists, e.g. example.com or 1.2.3.4

### `mx_lookup` (~51 tokens)

MX Lookup

Look up MX (Mail Exchanger) records for a domain. Returns the mail servers and their priorities.

Input parameters:

- `domain_name` (string, required): The domain to look up MX records for, e.g. example.com

### `txt_lookup` (~57 tokens)

TXT Lookup

Look up all TXT records for a domain. TXT records contain SPF policies, domain verification tokens, DKIM keys, and other metadata.

Input parameters:

- `domain_name` (string, required): The domain to look up TXT records for, e.g. example.com

### `cname_lookup` (~52 tokens)

CNAME Lookup

Look up CNAME (Canonical Name) records for a domain. Shows where a hostname aliases to.

Input parameters:

- `domain_name` (string, required): The domain to look up CNAME records for, e.g. www.example.com

### `ptr_lookup` (~67 tokens)

PTR Lookup

Reverse DNS lookup. Find the hostname associated with an IP address. A valid PTR record is important for email sending reputation.

Input parameters:

- `ip_address` (string, required): The IP address to look up, e.g. 8.8.8.8 or 142.250.80.46

### `dns_lookup` (~63 tokens)

DNS Lookup

Look up all DNS records for a domain in one query. Returns A, AAAA, CNAME, MX, NS, TXT, and SOA records.

Input parameters:

- `domain_name` (string, required): The domain to look up all DNS records for, e.g. example.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-themailx-email-deliverability/themailx#diagnostics

## Score history

- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 73
- 2026-07-29: 73
- 2026-07-28: 72
- 2026-07-27: 71
- 2026-07-26: 71

## Links

- Remote endpoint: https://themailx.com/mcp
- Website: https://themailx.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-themailx-email-deliverability/themailx/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-themailx-email-deliverability/themailx/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-themailx-email-deliverability/themailx