_ registry / mcp streamable-http · checked 3h ago

mailx-deliverability

https://themailx.com

Registry code: 14975546abb282f1

api record

mailX runs live email deliverability checks on public DNS. Use it when the user asks why emails go to spam, wants to check SPF, DKIM, DMARC or BIMI, look up MX, TXT, CNAME, PTR or full DNS records, check a domain against blacklists, generate SPF or DMARC records, or find SMTP/IMAP settings for a provider. Ask for the domain if it is missing. For a full audit or when emails go to spam, call audit_domain: it runs SPF, DKIM, DMARC, blacklist and MX checks in one call. mailX never changes DNS: generated records must be published by the user at their DNS provider. smtp_check and imap_check test a…

endpoint
https://themailx.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 it live, free and safe measured by this hub
Is mailx-deliverability live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is mailx-deliverability free to use?
Yes — the hub reached it with no key and no payment.
What tools does mailx-deliverability have?
17 tools: dmarc_check, spf_check, smtp_check, imap_check, audit_domain, mx_lookup, ptr_lookup, smtp_finder, ….
Is mailx-deliverability 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.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
1,192ms

last good check

priced tools
0

of 17 tools

_ answered our checks, 90 days 369 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
communication email
used for
  • check spf, dkim and dmarc records
  • check a domain against blacklists
  • test smtp or imap connection
  • generate spf or dmarc records
  • look up dns records
takes → gives
text → data
tools
15 reads1 sends messages
_ usage and payments 30 days

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.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

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

_ what it can do 17 tools
17 never probed 0 of 17 classified

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.

  • dmarc_check reads unknown 17h ago

    Use this when the user asks about DMARC, spoofing protection, or what happens to emails that fail authentication. Returns the live DMARC record, its policy and a fix suggestion.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to check DMARC records for, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • spf_check reads unknown 21h ago

    Use this when the user asks whether a domain's SPF record is valid, which servers may send email for a domain, or why SPF fails. Returns the live SPF record, a pass/fail status and a fix suggestion.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to check SPF records for, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • smtp_check sends messages unknown never probed

    Use this only when the user explicitly asks to test an SMTP login for a mail account they control and provides its credentials. Connects to the SMTP server and reports whether connection, encryption and authentication succeed. If from_email and to_email are both given, it also sends one test email. Credentials are not stored.

    mcp-tool

    {
  "type": "object",
  "required": [
    "host",
    "port",
    "username",
    "password",
    "encryption"
  ],
  "properties": {
    "host": {
      "type": "string",
      "description": "The SMTP server hostname, e.g. smtp.gmail.com"
    },
    "port": {
      "type": "integer",
      "maximum": 65535,
      "minimum": 1,
      "description": "The SMTP port number, e.g. 587 for TLS, 465 for SSL, 25 for unencrypted"
    },
    "password": {
      "type": "string",
      "description": "The SMTP password or app-specific password"
    },
    "to_email": {
      "type": "string",
      "description": "Optional recipient email address for sending a test email"
    },
    "username": {
      "type": "string",
      "description": "The SMTP username for authentication"
    },
    "encryption": {
      "enum": [
        "ssl",
        "tls",
        "none"
      ],
      "type": "string",
      "description": "The encryption protocol: ssl, tls, or none"
    },
    "from_email": {
      "type": "string",
      "description": "Optional sender email address for sending a test email"
    }
  }
}
    arguments 47 lines
  • imap_check reads unknown never probed

    Use this only when the user explicitly asks to test an IMAP login for a mailbox they control and provides its credentials. Connects to the IMAP server and reports whether connection, encryption and authentication succeed. Credentials are not stored.

    mcp-tool

    {
  "type": "object",
  "required": [
    "imap_host",
    "imap_port",
    "username",
    "password",
    "imap_encryption"
  ],
  "properties": {
    "password": {
      "type": "string",
      "description": "The IMAP password or app-specific password"
    },
    "username": {
      "type": "string",
      "description": "The IMAP username for authentication"
    },
    "imap_host": {
      "type": "string",
      "description": "The IMAP server hostname, e.g. imap.gmail.com"
    },
    "imap_port": {
      "type": "integer",
      "maximum": 65535,
      "minimum": 1,
      "description": "The IMAP port number, e.g. 993 for SSL, 143 for unencrypted"
    },
    "imap_encryption": {
      "enum": [
        "ssl",
        "tls",
        "none"
      ],
      "type": "string",
      "description": "The encryption protocol: ssl, tls, or none"
    }
  }
}
    arguments 39 lines
  • audit_domain unknown 12h ago

    Use this when the user asks why their emails go to spam or wants a full deliverability check of a domain. Runs SPF, DKIM (finds the selector on its own), DMARC, blacklist and MX checks in one call and returns pass, warning or fail for each, an overall result, and the fixes to apply in priority order with help links. Takes about 10 seconds. mailX never changes DNS.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to audit, e.g. example.com"
    },
    "dkim_selector": {
      "type": "string",
      "description": "The DKIM selector, e.g. google (Google Workspace), selector1 or selector2 (Microsoft 365). Optional: omit it to try common selectors."
    }
  }
}
    arguments 16 lines
  • mx_lookup reads unknown 12h ago

    Use this when the user wants to know which mail servers receive email for a domain. Returns the domain's live MX records with their priorities.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to look up MX records for, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • ptr_lookup reads unknown 12h ago

    Use this when the user wants the reverse DNS (PTR) of an IP address, for example to check a sending server's reverse DNS. Returns the hostname the IP resolves to.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ip_address"
  ],
  "properties": {
    "ip_address": {
      "type": "string",
      "description": "The IP address to look up, e.g. 8.8.8.8 or 142.250.80.46"
    }
  }
}
    arguments 12 lines
  • smtp_finder reads unknown 6h ago

    Use this when the user needs the outgoing mail (SMTP) server settings for an email provider or sending service, such as Gmail, Outlook, Microsoft 365, Zoho, Amazon SES or SendGrid. Returns the host, ports with encryption, what to use to log in, and the provider's setup guide. Never asks for the user's credentials.

    mcp-tool

    {
  "type": "object",
  "required": [
    "provider_name"
  ],
  "properties": {
    "provider_name": {
      "type": "string",
      "description": "The email provider name to look up, e.g. gmail, sendgrid, mailgun, outlook"
    }
  }
}
    arguments 12 lines
  • spf_generate reads unknown 6h ago

    Use this when the user needs a new SPF record for their email provider. Returns a TXT record ready to publish, or explains what to set up instead when the provider does not need a root SPF include. mailX does not publish it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name",
    "provider",
    "hard_fail_boolean"
  ],
  "properties": {
    "provider": {
      "enum": [
        "activecampaign",
        "amazon-ses",
        "aweber",
        "bluehost",
        "brevo",
        "campaign-monitor",
        "constant-contact",
        "elastic-email",
        "fastmail",
        "freshdesk",
        "gandi",
        "getresponse",
        "godaddy",
        "google",
        "hostgator",
        "hostinger",
        "hubspot",
        "icloud",
        "infomaniak",
        "intercom",
        "ionos",
        "ionos-eu",
        "kit",
        "klaviyo",
        "mailbox-org",
        "mailchimp",
        "mailersend",
        "mailgun",
        "mailjet",
        "mandrill",
        "microsoft",
        "migadu",
        "moosend",
        "namecheap",
        "ovh",
        "postmark",
        "protonmail",
        "purelymail",
        "rackspace",
        "resend",
        "salesforce",
        "sendgrid",
        "smtp2go",
        "sparkpost",
        "titan",
        "yandex",
        "zendesk",
        "zeptomail",
        "zoho"
      ],
      "type": "string",
      "description": "Email provider identifier. Google Workspace or Gmail = google. Microsoft 365, Office 365 or Outlook = microsoft. Amazon SES = amazon-ses. Common provider names are also accepted."
    },
    "domain_name": {
      "type": "string",
      "description": "The domain to generate an SPF record for, e.g. example.com"
    },
    "hard_fail_boolean": {
      "type": "boolean",
      "description": "If true, uses strict -all policy (reject unauthorized senders). If false, uses soft ~all (mark but deliver)."
    }
  }
}
    arguments 73 lines
  • dkim_check reads unknown 17h ago

    Use this when the user wants to verify DKIM for a domain. Pass the DKIM selector if known (for example google for Google Workspace, selector1 or selector2 for Microsoft 365). If the selector is unknown, omit it: mailX then tries common selectors and returns the ones it finds. Returns the published key and its status. A miss on common selectors does not prove DKIM is absent.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to check DKIM records for, e.g. example.com"
    },
    "dkim_selector": {
      "type": "string",
      "description": "The DKIM selector, e.g. google (Google Workspace), selector1 or selector2 (Microsoft 365). Optional: omit it to try common selectors."
    }
  }
}
    arguments 16 lines
  • dmarc_generate reads unknown 17h ago

    Use this when the user needs a DMARC record. Returns the record name, value and type ready to publish. mailX does not publish it.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name",
    "email",
    "dmarc_policy"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The email address to receive DMARC aggregate reports, e.g. [email protected]"
    },
    "domain_name": {
      "type": "string",
      "description": "The domain to generate a DMARC record for, e.g. example.com"
    },
    "dmarc_policy": {
      "enum": [
        "none",
        "quarantine",
        "reject"
      ],
      "type": "string",
      "description": "The DMARC policy: none (monitor only), quarantine (mark as spam), or reject (block entirely)"
    }
  }
}
    arguments 27 lines
  • blacklist_check reads unknown 6h ago

    Use this when the user suspects their domain is blacklisted or blocked. Checks the domain against major DNS blocklists and returns the result for each list.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain name or IP address to check against blacklists, e.g. example.com or 1.2.3.4"
    }
  }
}
    arguments 12 lines
  • dns_lookup reads unknown 14h ago

    Use this when the user wants every DNS record for a domain in one view (A, AAAA, CNAME, MX, NS, TXT, SOA). Returns the live records grouped by type.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to look up all DNS records for, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • imap_finder reads unknown 14h ago

    Use this when the user needs the incoming mail (IMAP) server settings for an email provider, such as Gmail, Outlook, Yahoo, iCloud or Zoho. Returns the host, ports with encryption and the provider's setup guide. Never asks for the user's credentials.

    mcp-tool

    {
  "type": "object",
  "required": [
    "imap_provider_name"
  ],
  "properties": {
    "imap_provider_name": {
      "type": "string",
      "description": "The email provider name to look up, e.g. gmail, outlook, yahoo"
    }
  }
}
    arguments 12 lines
  • bimi_check reads unknown 14h ago

    Use this when the user asks about BIMI or showing a brand logo next to their emails in inboxes. Returns the live BIMI record, the logo URL it declares, and a fix suggestion.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to check BIMI records for, e.g. example.com"
    }
  }
}
    arguments 12 lines
  • cname_lookup reads unknown 21h ago

    Use this when the user wants to know whether a hostname is an alias of another one, for example to verify DKIM or tracking CNAMEs. Returns the live CNAME target.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to look up CNAME records for, e.g. www.example.com"
    }
  }
}
    arguments 12 lines
  • txt_lookup reads unknown 21h ago

    Use this when the user wants to see a domain's TXT records, for example to find verification tokens or check what SPF or other policies are published. Returns all live TXT records.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain_name"
  ],
  "properties": {
    "domain_name": {
      "type": "string",
      "description": "The domain to look up TXT records for, e.g. example.com"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 14975546abb282f1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/14975546abb282f1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/14975546abb282f1/badge.svg)](https://brick.blue/agent/14975546abb282f1?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
1,717ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.