# MX Verdict

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

- name: com.mxverdict/mxverdict
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.mxverdict%2Fmxverdict
- tools: https://api.protogrid.dev/v1/servers/com.mxverdict%2Fmxverdict/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 99
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-97% +updated-22d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 7 of 7 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 996 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 996 tokens to load them all
- tool set hash: 274ca32e20cef6a533eae4875f24a770
- badge: [![protogrid quality](https://protogrid.dev/badge/com.mxverdict/mxverdict.svg)](https://protogrid.dev/servers/com.mxverdict/mxverdict)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mxverdict.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.96511626)

## Packages

_none_

## Tools (7)

- `check_blacklist`: 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.
- `check_dkim`: 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.
- `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.
- `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. Use it for a general question such as "is email set up correctly for example.com".
- `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.
- `dns_lookup`: 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.
- `lookup_mx`: 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.