mxverdict
Registry code: 9c708949b672d6d2
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.
- endpoint
- https://mxverdict.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is mxverdict live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is mxverdict free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does mxverdict have?
- 7 tools: check_email_domain, check_blacklist, check_spf, dns_lookup, lookup_mx, check_dkim, check_dmarc.
- Is mxverdict safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.2%
last good check
of 7 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- communication email
- used for
- check a domain's spf dkim and dmarc
- check a domain against blocklists
- look up dns records
- check a domain's email setup
- takes → gives
- text → data
- tools
- 7 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_email_domain reads unknown never probed
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".
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 512, "description": "Domain name, for example example.com." } } }arguments 14 linescheck_blacklist reads unknown 6h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "target" ], "properties": { "target": { "type": "string", "maxLength": 512, "description": "One IPv4 or IPv6 address, or one domain name." } } }arguments 14 linescheck_spf reads unknown 10h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 512, "description": "Domain name, for example example.com." } } }arguments 14 linesdns_lookup reads unknown 10h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 512, "description": "Domain name or IP address, for example example.com or _dmarc.example.com." }, "type": { "enum": [ "ALL", "A", "AAAA", "CNAME", "MX", "NS", "PTR", "SOA", "TXT", "CAA", "SRV", "DS", "DNSKEY", "TLSA", "HTTPS", "SVCB" ], "type": "string", "description": "Record type; ALL when left out." } } }arguments 36 lineslookup_mx reads unknown 10h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 512, "description": "Domain name, for example example.com." } } }arguments 14 linescheck_dkim reads unknown 6h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 512, "description": "Domain name, for example example.com." }, "selector": { "type": "string", "maxLength": 253, "description": "DKIM selector, for example google or selector1. Leave out to probe common selectors." } } }arguments 19 linescheck_dmarc reads unknown 6h ago
Check a domain's DMARC record: whether it exists and is valid, its policy (none, quarantine or reject), alignment, and where reports are sent.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 512, "description": "Domain name, for example example.com." } } }arguments 14 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id9c708949b672d6d2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9c708949b672d6d2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9c708949b672d6d2?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.