Verify one email—or an entire list
Use the real-time API inside your product or upload CSV and TXT files from the dashboard. Choose the depth that fits each workflow.
Verify one address in real time or clean an entire list. Get the evidence your team needs—from basic domain checks to SMTP mailbox confirmation—without paying for inconclusive API results.
Low-risk address with mailbox evidence
Protect more than one send
Repeated hard bounces can signal poor list hygiene and put sender reputation at risk. Verify before sending so avoidable bad addresses never reach the send queue.
A verification system, not a black box
Choose the right amount of evidence for each decision, then carry the result into your product, list workflow, or AI tool.
Use the real-time API inside your product or upload CSV and TXT files from the dashboard. Choose the depth that fits each workflow.
Go beyond a pass/fail label with syntax, MX, disposable, role-based, TLD, provider, authentication, blocklist, WHOIS, and parked-domain signals.
Deepcheck adds SMTP mailbox and catch-all verification for high-value sends—without sending an email to the recipient.
Connect the MailTooth MCP server and let supported AI tools verify an address before outreach, CRM entry, or messaging.
Invite teammates, manage workspace permissions, create scoped API keys, and inspect usage and verification activity in one place.
Unknown API outcomes and failed executions are automatically refunded. Purchased credits never expire, so unused budget stays yours.
Progressive verification
A form validation and a high-value outbound email should not cost—or wait—the same.
Form checks and large first-pass lists
Fast address and domain screening before data enters your system.
CRM hygiene and campaign preparation
A richer domain-trust profile without an SMTP mailbox check.
High-value outreach and critical sends
The complete check, including mailbox-level deliverability evidence.
Unknown API outcomes and failed executions are automatically refunded.
From raw address to clear next step
Start in the dashboard, integrate the endpoint, or place verification inside an AI workflow. The same tiered model keeps decisions consistent.
Read the product docsOne address via API or MCP, or a CSV/TXT file in the dashboard.
Quick, Standard, or Deepcheck—based on the decision you need to make.
Keep, reject, retry, or review using address, mailbox, and risk evidence.
MCP for agentic workflows
Connect the MailTooth Streamable HTTP MCP server and verification becomes a native tool call. Your agent can check an address, receive structured evidence, and choose the next action before it writes to a CRM, starts outreach, or triggers a message.
Before creating this CRM contact, I need to confirm the address.
{ email: "alex@northstar.io", type: "deepcheck" }Create contact and continue the approved workflow.
The agent receives address status, mailbox status, risk, disposable and role-based flags, credit usage, and the complete structured result.
Tell the agent when to use Quick, Standard, or Deepcheck and which outcomes require review.
The agent calls the same verification engine used by the API and bulk workflows.
Verify a discovered address before the agent creates a CRM contact, assigns an owner, or starts an outreach sequence.
Run Deepcheck for high-value recipients and let mailbox, catch-all, and risk signals decide whether to send, review, or stop.
Use a fast address check before an automated workflow accepts a user, sends an invitation, or starts onboarding.
Recheck stale records and route explicit invalid, unknown, disposable, role-based, and risky outcomes to different actions.
Works with compatible Streamable HTTP MCP clients and agent frameworks—including Claude Code, Cursor, VS Code, Windsurf, OpenAI Agents, and custom clients.
Built around real workflows
Explore focused playbooks for preventing bad data, reducing avoidable bounces, and choosing the right verification depth.
Cleaner product data
More confident outreach
Repeatable client hygiene
Reach the right candidates
Fewer unreachable customers
Evidence-rich data products
Pay once. Verify when needed.
No monthly plan to babysit. Start with 100 credits, then buy a pack that fits your workload. Purchased credits never expire.
The verification field guide
Product guidance and deliverability fundamentals from the team building the verification engine.
Connect verification as a native agent tool, then use structured address, mailbox, and risk signals to make safer workflow decisions.
Read articleA practical framework for balancing speed, evidence, and credit usage across forms, lists, and high-value sends.
Read articleA simple, repeatable process for preparing CSV or TXT contact data without losing the reasoning behind each result.
Read articleGood questions deserve direct answers
Still deciding how verification fits your workflow? Start free and inspect real results before buying credits.
Get 100 free creditsDepending on the selected depth, checks include syntax, domain and MX records, disposable and role-based addresses, personal or professional classification, TLD risk, provider detection, parked domains, SPF/DKIM/DMARC, blocklists, WHOIS, SMTP mailbox status, and catch-all behavior.
No. New accounts receive 100 verification credits and can begin without adding a card.
No. Credit packs are one-time purchases and purchased credits do not expire.
Unknown API outcomes and failed executions are automatically refunded, so those checks do not consume your credit balance.
Yes. Upload a CSV or TXT file in the dashboard, select the email column and verification depth, follow the job progress, and download the completed results.
Yes. Create a scoped API key and call the single-email verification endpoint. The product documentation includes request and response examples for all three depths.
Yes. The Streamable HTTP MCP endpoint exposes a verify_email tool for compatible AI clients and agent frameworks, using the same tiered verification model, structured results, and API-key authentication.
Repeated hard bounces can signal poor list hygiene and put domain and sender reputation at risk. Verifying before a send reduces avoidable bad-address attempts, but it should complement—not replace—consent, authentication, and responsible sending practices.
No. Deepcheck uses SMTP-level signals without sending a message to the address being checked.
Your first 100 credits are free
Start without a card. Add credits only when the product has proved its value to your workflow.