Skip to content

MX Verdict MCP server

com.mxverdict/mxverdictmxverdict.comstreamable-httpv1.0.0Scanned

Free, read-only email and DNS checks: SPF, DKIM, DMARC, MX, DNS records, blocklists, domain health.

7 tools: 5 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 5 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the MX Verdict MCP server can do

The MX Verdict MCP server is published by mxverdict.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (5 tools: check_email_domain, check_spf, check_dkim, check_dmarc and 1 more), but cannot delete data. 2 tools only read.

1 tool reads private data (lookup_mx); 7 tools bring in text other people can write (check_email_domain, check_spf, check_dkim and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 5Claude Code: ask
  • check_blacklistCheck whether an IP address or a domain is listed on public DNS blocklists (DNSBLs).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check whether an IP address or a domain is listed on public DNS blocklists (DNSBLs). A domain is checked on domain blocklists only; to check a mail server, give its IP address.

    Annotations the server declares

    • title: Blacklist check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_dkimCheck a domain's DKIM public keys in DNS.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check a domain's DKIM public keys in DNS. With a selector (the s= tag of a DKIM-Signature header), checks that selector's key; without one, probes common selector names. Finding no key on common names does not prove DKIM is missing: selectors cannot be listed from DNS.

    Annotations the server declares

    • title: DKIM check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_dmarcCheck a domain's DMARC record: whether it exists and is valid, its policy (none, quarantine or reject), alignment, and where reports are sent.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check a domain's DMARC record: whether it exists and is valid, its policy (none, quarantine or reject), alignment, and where reports are sent.

    Annotations the server declares

    • title: DMARC check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_email_domainCheck 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Use it for a general question such as "is email set up correctly for example.com".

    Annotations the server declares

    • title: Email domain health check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • check_spfCheck 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: SPF check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • dns_lookupLook up DNS records of a name.Reads text others writeNo findings

    Why it is in this group

    • The name "dns_lookup" says "lookup": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Look up DNS records of a name. Type ALL (the default) queries A, AAAA, CNAME, MX, NS, TXT, SOA and CAA; any single type can be asked for. An IP address gives its reverse DNS (PTR) lookup.

    Annotations the server declares

    • title: DNS lookup
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • lookup_mxLook up a domain's MX records (its incoming mail servers), their IP addresses and reverse DNS.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "lookup_mx" says "lookup": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "mail": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "mail": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Look up a domain's MX records (its incoming mail servers), their IP addresses and reverse DNS. DNS only: it does not connect to the mail servers.

    Annotations the server declares

    • title: MX lookup
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mxverdict.com/mcp: tools/list returned 7 tools to an anonymous client, including check_email_domain (write), check_spf (write), check_dkim (write), check_dmarc (write), check_blacklist (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mxverdict https://mxverdict.com/mcp
claude mcp add --transport http mxverdict https://mxverdict.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mxverdict__lookup_mx",
      "mcp__mxverdict__dns_lookup"
    ],
    "ask": [
      "mcp__mxverdict__check_email_domain",
      "mcp__mxverdict__check_spf",
      "mcp__mxverdict__check_dkim",
      "mcp__mxverdict__check_dmarc",
      "mcp__mxverdict__check_blacklist"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mxverdict. Review it before you use it.

Capability tags behind 7 rules
  • mcp__mxverdict__check_email_domain untrusted-input
  • mcp__mxverdict__check_spf untrusted-input
  • mcp__mxverdict__check_dkim untrusted-input
  • mcp__mxverdict__check_dmarc untrusted-input
  • mcp__mxverdict__lookup_mx private-data, untrusted-input
  • mcp__mxverdict__dns_lookup untrusted-input
  • mcp__mxverdict__check_blacklist untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.mxverdict/mxverdict/verify?hash=e4c3b39a4f5474b3eca2af6db9f2d67ec518c1c77f2875bc9ac6138a6f235345" | jq -e '.changed == false'

Pinned hash e4c3b39a4f54, from Nov 13, 2026, 20:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.mxverdict/mxverdict/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.mxverdict/mxverdict
[![Anlyon Radar](https://radar.anlyon.com/badge/com.mxverdict/mxverdict.svg)](https://radar.anlyon.com/servers/com.mxverdict/mxverdict)

Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.

MX Verdict MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MX Verdict MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the MX Verdict MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MX Verdict MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MX Verdict MCP server have?

7 tools: 5 write, 2 read. check_email_domain, check_spf, check_dkim, check_dmarc, check_blacklist, lookup_mx and dns_lookup.

Does the MX Verdict MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MX Verdict MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MX Verdict MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.