Scan.mx MCP server

• Registry namemx.scan/diagnosticsverified in the MCP registry

The registry name sits under scan.mx. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools9
• Server calls itselfscan.mx
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 146 ms.

• Its tools do every use case we checked: Check SPF, DKIM and DMARC records for a domain; Find blacklist listings for a domain's mail servers.
• Checked on 1 of the 7 days it takes to judge reliability.

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 scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it2 of 2 use cases
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer322 ms
• Space in an agent's context≈ 1,128 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results9 of 9 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

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_domain

  Run the full email and DNS deliverability check for a domain: MX, SPF, DKIM, DMARC, DNS health, provider detection, and blacklists. Returns a letter grade (A+ to F, where specific weaknesses cap the grade), a 0 to 100 score, and every…

• check_mx

  Check the MX records of a domain: presence, hostnames, resolution, null-MX, and common misconfigurations.

• check_spf

  Check the domain SPF policy: presence, syntax, the all qualifier, and the 10-lookup limit.

• check_dmarc

  Check the domain DMARC policy at _dmarc: presence, policy strength (none/quarantine/reject), and reporting.

• check_blacklist

  Check whether the domain and its mail server IPs are listed on the Spamhaus (ZEN, DBL, ZRD, AuthBL), SpamCop, GBUdb and PSBL blocklists.

• check_mta_sts

  Check the domain MTA-STS policy (_mta-sts TXT and the HTTPS policy file, mode and MX coverage) and its TLS-RPT reporting record.

• check_dnssec

  Check DNSSEC validation and DNS health: delegation, nameserver count, SOA, and reverse DNS of the mail servers.

• check_bimi

  Check the domain BIMI record at default._bimi: the SVG logo URL, the VMC/CMC certificate, and the DMARC enforcement BIMI needs.

• check_dkim

  Check DKIM signing keys for a domain. Without a selector, common provider selectors are probed. Pass an explicit selector to look up that exact key at selector._domainkey.