
MX Verdict MCP server
Which MCP servers are MX Verdict's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-21
- Registry namecom.mxverdict/mxverdictverified in the MCP registry
The registry name sits under mxverdict.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-21
- Tools7
- Server calls itselfmxverdict
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 173 ms.
- Whether its tools do the product's job has not been judged yet.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
- Answered100% of days7 of 7 daily checks
- Median first answer552 ms
- Space in an agent's context≈ 880 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Check SPF, DKIM and DMARC on a test email
- not sure · Find blocklist listings for a sending server
- not sure · Estimate the spam score of a message before sending
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
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. Use it for a general question such as "is email set up correctly for example.com".
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.
check_dkimCheck 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…
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.
lookup_mxLook 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.
dns_lookupLook 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.
check_blacklistCheck 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.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"mxverdict": {
"type": "http",
"url": "https://mxverdict.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http mxverdict https://mxverdict.com/mcpclaude.ai, ChatGPT and other clients: add https://mxverdict.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.