Claude
- Open Add custom connector ↗
- Name it Domain Mail Check and paste the URL
- Click Add, then ask away
https://mailcheck.openkrill.app/mcp
Mail delivery and DNS check
Check how a domain is set up for email, whether Gmail and Outlook are likely to accept its mail, and who it is registered with, from public DNS, free blocklists and registry data.
Ask "will Gmail accept mail from example.com sent from 203.0.113.7?", "is DMARC set up correctly for github.com?", "check SPF and DKIM for example.com", "which mail provider does acme.io use?" or "when does openai.com expire?".
The email check reads the domain's SPF record (following include and redirect, counting DNS lookups against the limit of 10), its DMARC policy, the MX records and, when you give a DKIM selector, whether the DKIM key is published. It returns a grade from A to F for protection against spoofing, the problems it found and a short list of fixes. The DNS records tool reads A, AAAA, MX, TXT, CAA and NS records with their TTLs, which also shows which mail provider a domain uses and which certificate authorities may issue for it. The registration tool reads the domain's registry record over RDAP: registrar, creation and expiry dates, status flags and name servers.
The delivery check gives one verdict for Gmail and Outlook, the top 3 causes and one fix for each. It tests the published sender rules (SPF listing the sending IP, DKIM, DMARC, reverse DNS of the IP, key length) and reads 6 free blocklists (SpamCop, PSBL, UCEPROTECT level 1, Mailspike and NordSpam for the IP and the domain). Each rule and each list names its official source.
The cold-email launch score gives a score from 0 to 100 for a new sending domain, with a verdict of ready, almost or not_ready and the 5 fixes to make first. It tests SPF, DKIM, DMARC, reply mail, a domain blocklist, the domain's age from the registry record and the shape of its name. Each rule names its source and is labelled standard (a published requirement) or opinion (common advice nobody requires, which never decides not_ready).
The DNS hygiene check finds 4 faults beyond SPF, DKIM and DMARC: no CAA record (any certificate authority may issue for the domain), DNSSEC that is off or broken, mail servers that do not offer STARTTLS (mail arrives unencrypted), and dangling CNAMEs on 20 common subdomains such as www, shop and help, which point at a name that no longer exists, some of which anyone can register or create. For STARTTLS it reads only the greeting and EHLO answer of up to 2 mail servers and never sends mail; a server it cannot reach is reported as not read, not as a fault.
DNS answers come from Cloudflare's DNS over HTTPS service with Google Public DNS as a fallback, and registration data from the registry of the domain's ending, found through IANA's RDAP directory. Every answer names its source and the date it was read.
It does not send a test message or read mailboxes, so a good verdict means no published rule is broken, not a promise of the inbox; it does not read sender reputation, discover subdomains beyond a fixed list of common names, or return who owns a domain: registrant and contact details are never read or returned. It checks the exact domain you give, so a parent domain's SPF or DMARC record is not inherited. The domains you ask about are not stored; the only lasting record is a daily count of calls per tool.
https://mailcheck.openkrill.app/mcphttps://mailcheck.openkrill.app/mcpmailcheck.openkrill.appThe AI reads these server instructions before using this connector, every time.
Domain Mail Check: Mail delivery and DNS check. Call when the user asks whether mail will reach Gmail or Outlook, or why it is rejected or marked spam. Pass the domain and the sending IP when known, and mail_from when the user gives the Return-Path domain of a sent message. Give the verdict, then the top causes with fixes, then the source links. likely_accepted means no published rule is broken, not that the inbox is certain. Mention not_checked items only when they matter. Call when the user asks whether a new or secondary domain is ready for cold email. Give the score, the verdict and the fix_first list, and say whether each fix is standard or opinion. Never present an opinion as a requirement, and say the score does not promise the inbox. A domain under 14 days old fails an opinion rule: tell the user to wait and warm up, not that the domain is broken. Call when the user asks about CAA, DNSSEC, STARTTLS or encrypted mail delivery, dangling CNAMEs or subdomain takeover, or for a wider DNS security check than SPF, DKIM and DMARC. Give the faults with their fixes first. A dangling CNAME is a risk to fix, not proof that someone took the subdomain over. could_not_connect or refused on a mail server means it was not read, never that STARTTLS is missing. Call for SPF, DMARC, DKIM and a spoofing grade, for A, AAAA, MX, TXT, CAA or NS records, and for registrar, dates and name servers. Pass dkim_selectors only when the user or their mail provider names them. DKIM cannot be found without a selector, so unknown is not a failure. Give the grade with its issues and fixes, and the source and as_of date. When something fails, give the records_to_paste as they are, each with its name, value and whether it replaces a record, then the fix_steps; a record marked later is the next step, not a fix. returns a page link to a web page with the same check: give it when the user may want to see the result in a browser or send it to the domain's owner. unavailable means a lookup failed: say so and do not guess. not_found means the name does not exist in DNS. registered false means the registry has no record, so the domain is usually free to register. These tools never return registrant or owner details: decline requests for an owner's name, email or phone and offer the registrar instead. They do not discover subdomains or send mail; tests published rules and blocklists, not a real message. This server allows 60 tool calls a minute per network and 5,000 a day for all callers together; the day count resets at 00:00 UTC. If a tool fails, gives a wrong answer, or a tool you need is missing, call with one short message (kind, message, tool); reads the answer.
None in the store listings or on the server
Mail delivery and DNS check. Check how a domain is set up for email, whether Gmail and Outlook are likely to accept its mail, and who it is registered with, from public DNS, free blocklists and registry data. Ask "will Gmail accept mail from example.
Open its listing in the app's connector directory and connect. No sign-in is needed. Step-by-step setup for each app is on this page.
The Domain Mail Check MCP server URL is https://mailcheck.openkrill.app/mcp. Paste it as a custom connector in Claude, ChatGPT, Gemini or Grok, or add it to Claude Code, Cursor or any MCP client. Setup steps.
Yes. Domain Mail Check is published or run by HIẾU VŨ TRUNG NGUYEN, so it is the official MCP server. See other official connectors.
It is listed in 1 store: ChatGPT. Apps where it is not listed can usually still add it as a custom connector.
It is ranked 13,505 of 15,719 in the ChatGPT directory. A rank is the store's own order, not a usage count. How we track ranks.
It has 8 tools: 7 read data and 1 change data. See every tool and its inputs.
It can change data but not delete it. 1 tool can create or update things, for example:
None that we found. None in the store listings or on the server.
No. Its answers come back as text in the chat. Connectors with interactive UI.
This page updates every day. To ask about Domain Mail Check from Claude, ChatGPT or a coding agent, connect the Agent Ready MCP server: it tracks ranks, tools and new listings across the AI plugin stores.