Provide an email or domain to review its mail routing and risk flags before deciding what needs correction.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Explain normalization and disposable, alias, or role-account signals.
/oo Mailcheck: Check [email address] with UserCheck. Explain the normalized address, MX result, and disposable, alias, role-account, and spam signals. Keep any correction suggestion separate from the original.
Review MX records and domain risk indicators.
/oo Mailcheck: Check domain [domain] with UserCheck. Summarize its MX records and providers and explain any disposable, forwarding, or spam flags.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a UserCheck API key.
Connect Mailcheck →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
The Mailcheck connection uses UserCheck for single-email and domain checks, plus account status and usage. It reports risk and MX signals rather than sending a test email.
Read normalized email details, domain risk signals, and mail-routing records.
Retrieve account information, plan details, and current API usage.
Retrieve UserCheck account information, plan details, and current API usage.
Leina 
Wanta 
mailcheck.get_status Validate a single email address and return UserCheck deliverability and risk signals.
mailcheck.verify_email Validate a domain and return UserCheck domain-level risk and MX signals.
mailcheck.validate_domain No matching tools.
Treat normalization and typo suggestions as results to review. Compare them with the supplied address before changing another system’s record.
It describes domain mail routing and recognized providers. It does not prove that a particular mailbox accepts messages.
Yes. Ask for account status to read usage and plan information available to the key.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.