Security & Testing

mxverdict.com

Checks a domain's email security and authentication setup, including SPF, DKIM, DMARC, MX, blocklists, MTA-STS, TLS-RPT, and BIMI records.

1 endpoint7 known toolsFirst detected September 28, 2026Last detected September 28, 2026

ENDPOINT 1

https://mxverdict.com/mcp

No auth detected

MCP server metadata

Name: mxverdict
Version: 1.0.0

Capabilities

tools

Server instructions

MX Verdict (mxverdict.com) runs free, read-only email and DNS checks: SPF, DKIM, DMARC, MX, DNS records, blocklists, and a whole-domain email health check. The tools only read public DNS and public blocklists; they never send email. Every result ends with a link to the full report on mxverdict.com; give it to the user. Identical checks within 60 seconds return the same result. Checks are rate limited per client IP address, the same limits as the website; a rate-limited tool result says how long to wait.

Known tools 7

check_email_domain

Check everything about a domain's email setup in one call: SPF, DMARC, MX, DKIM on common selectors, domain blocklists, MTA-STS, TLS-RPT and BIMI.

Potential side effects

check_spf

Check a domain's SPF record: whether it exists and is valid, how many of the 10 allowed DNS lookups it uses, and how its all mechanism treats mail from servers that are not listed.

Inferred read-only

check_dkim

Check a domain's DKIM public keys in DNS.

Inferred read-only

check_dmarc

Check a domain's DMARC record: whether it exists and is valid, its policy (none, quarantine or reject), alignment, and where reports are sent.

Inferred read-only

lookup_mx

Look up a domain's MX records (its incoming mail servers), their IP addresses and reverse DNS.

Inferred read-only

dns_lookup

Look up DNS records of a name.

Inferred read-only

check_blacklist

Check whether an IP address or a domain is listed on public DNS blocklists (DNSBLs).

Inferred read-only

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.mxverdict]
url = "https://mxverdict.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mxverdict": {
      "type": "http",
      "url": "https://mxverdict.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mxverdict
Remote MCP URL: https://mxverdict.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": {
    "mxverdict": {
      "url": "https://mxverdict.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mxverdict": {
      "type": "http",
      "url": "https://mxverdict.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mxverdict",
  "transport": "streamable-http",
  "url": "https://mxverdict.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.