scan.mx
Registry code: 9ea499471c72c8c4
Check email deliverability for a domain: MX, SPF, DKIM, DMARC, blacklists. Graded, no key.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.scan.mx/mcp
- protocol
- http-sse ·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 scan.mx live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
- Is scan.mx free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does scan.mx have?
- 6 tools: check_blacklist, check_dkim, check_domain, check_dmarc, check_mx, check_spf.
- Is scan.mx 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.4%· all time 99.4%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- communication email
- used for
- check email deliverability for a domain
- check spf, dkim and dmarc records
- check if a domain is blacklisted
- check mx records
- takes → gives
- text → data
- tools
- 6 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_blacklist reads unknown 13h ago
Check whether the domain and its mail server IPs are listed on the Spamhaus (ZEN, DBL, ZRD, AuthBL), SpamCop, GBUdb and PSBL blocklists.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "The domain to check, e.g. example.com. No scheme or path." } } }arguments 15 linescheck_dkim reads unknown 13h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "The domain to check, e.g. example.com. No scheme or path." }, "selector": { "type": "string", "pattern": "^[a-z0-9_.-]+$", "maxLength": 63, "description": "An explicit DKIM selector to look up (e.g. \"google\", \"s1\")." } } }arguments 21 linescheck_domain reads unknown 4h ago
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 individual check with its RFC reference. Set include_smtp to also run a live SMTP probe of the mail servers: the probe is non-blocking, so when smtp_status is "pending" or "running" call this tool again (poll_after_seconds hints how long to wait) until smtp_status is "complete" and the SMTP checks appear in checks.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "The domain to check, e.g. example.com. No scheme or path." }, "include_smtp": { "type": "boolean", "default": false, "description": "Also run a live SMTP connectivity probe of the MX hosts. Non-blocking: poll by re-calling until smtp_status is complete." } } }arguments 20 linescheck_dmarc reads unknown 13h ago
Check the domain DMARC policy at _dmarc: presence, policy strength (none/quarantine/reject), and reporting.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "The domain to check, e.g. example.com. No scheme or path." } } }arguments 15 linescheck_mx reads unknown 4h ago
Check the MX records of a domain: presence, hostnames, resolution, null-MX, and common misconfigurations.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "The domain to check, e.g. example.com. No scheme or path." } } }arguments 15 linescheck_spf reads unknown 4h ago
Check the domain SPF policy: presence, syntax, the all qualifier, and the 10-lookup limit.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "The domain to check, e.g. example.com. No scheme or path." } } }arguments 15 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 id9ea499471c72c8c4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9ea499471c72c8c4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9ea499471c72c8c4?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
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 1,034ms
- 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
- —
1 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.