# No2Bounce MCP > No2Bounce validates email addresses in bulk, protecting your sender reputation by identifying invalid or disposable accounts before you send a single message. Your AI agent submits large lists for processing and uses status tools to retrieve clean, deliverable data directly into your workflow. ## Overview - **Category:** marketing-automation - **Price:** Free - **Tags:** email-verification, deliverability, data-cleaning, bulk-processing, sender-reputation, api-integration ## Description Listen up. If you’re sending out emails in bulk—like, serious mailing lists—you gotta make sure they actually hit a mailbox. This isn't some quick check; this is protecting your whole sender reputation before y'all send a single damn message. That’s what **No2Bounce** does. It plugs right into your AI client and makes sure the list you're using is clean, usable data. We handle massive validation jobs for you. Your agent just submits the full batch of emails it needs checked. When you call `validate_bulk`, the system doesn't wait around for results; that’d time out every single time. Instead, it accepts your list and spits back a unique tracking ID right away. That ID is key—it’s your receipt proving the job got submitted and is now running asynchronously. So, you get that ID, and then you're done with the submission part. You don't stare at a loading bar until it crashes. Next, when you wanna check up on things, you use `get_validation_status` along with that tracking ID. This tells your agent whether the massive validation job is still churning away in the background or if it’s wrapped up and ready to go. It's purely status checking—you just need to know where we are. Once the status confirms the work is done, you use that same `get_validation_status` tool one more time, but this time, you’re pulling the final reports. This isn't just a 'yes/no' answer; it gives you the detailed breakdown of every address submitted. You see exactly which emails passed validation and—critically—it tells you *why* any other addresses failed. Why is that granular detail important? Because you need to know if an email bounced because the domain doesn’t exist, or if it’s a disposable account someone just set up for five minutes. No2Bounce catches all the nasty stuff: invalid structural formats, temporary mail services, and high-risk patterns that scream 'spam.' It keeps your sender score solid so you don't get flagged by major providers. When your agent runs this process, it’s a three-step workflow. First, submit the list using `validate_bulk` to grab that tracking ID. Second, ping the status with `get_validation_status` until the job is marked complete. Third, call `get_validation_status` again to pull the final report containing only the clean, deliverable data you can trust to use in your next campaign. It’s about reliability; it's about making sure that when your message leaves your client, it actually reaches somebody who cares. You don't wanna waste time sending mail to dead ends. ## Tools ### get_validation_status Checks the progress of an ongoing validation job or retrieves the final results using a tracking ID. ### validate_bulk Accepts a list of emails and submits them for validation, returning a unique ID to track the job. ## Prompt Examples **Prompt:** ``` Validate these emails for me: contact@company.com, support@service.io, invalid-email@test. ``` **Response:** ``` I've submitted 3 emails for validation. Your tracking ID is `nb_84729`. I'll check the status for you in a moment. ``` **Prompt:** ``` Check the status of my No2Bounce validation task nb_84729. ``` **Response:** ``` The validation for task `nb_84729` is complete. Results: 2 valid emails, 1 invalid. Would you like to see the detailed breakdown? ``` **Prompt:** ``` Submit this list of 10 emails to No2Bounce and give me the tracking ID. ``` **Response:** ``` Bulk validation started for 10 addresses. Your tracking ID is `nb_99210`. You can ask me to check the results using this ID later. ``` ## Capabilities ### Process Bulk Validation Jobs You submit lists of email addresses to start an asynchronous validation task and receive a unique tracking ID. ### Check Job Status Progress The agent uses the tracking ID to confirm if the large-scale validation job is still running or if it's complete. ### Retrieve Final Validation Reports You fetch the detailed results, seeing exactly which emails passed and why any others failed. ## Use Cases ### Launching a Quarterly Newsletter The marketing manager pulls a CSV of 20k contacts. Instead of manually checking them, they ask their agent to run `validate_bulk` on the list. The agent gets a tracking ID, waits for completion, and then uses `get_validation_status` to pull a clean subset ready for the mailing platform. ### Cleaning Scraped Lead Data The sales team scrapes 500 leads from LinkedIn. They feed that list into their agent, which executes `validate_bulk`. The resulting data is immediately filtered by your client before any outreach emails are drafted, ensuring the reps only target active accounts. ### Integrating Signups on a Website The developer needs to check signup forms. They write an agent that first calls `validate_bulk` with the submitted email, then uses `get_validation_status` to confirm validity before allowing the user to complete registration. ### Auditing a Database Dump The data team gets a dump of old contacts. They use the agent to run `validate_bulk` on the entire set, identify which records are now invalid or disposable, and export only the confirmed good leads. ## Benefits - **High Deliverability:** Don't send emails to dead addresses. Running `validate_bulk` filters out invalid or spam-trap emails, keeping your campaign metrics clean from the start. - **Saves Time on Status Checks:** You don't have to poll manually. Using a tracking ID and `get_validation_status` lets your agent wait for results efficiently without coding complex polling loops. - **Protects Sender Reputation:** Sending emails to bad addresses hurts your domain rating. No2Bounce validates lists, keeping you in good standing with major ISPs. - **Works on Huge Datasets:** The `validate_bulk` tool is built for scale. Submit thousands of records at once without bogging down your local machine or risking timeouts. - **Direct Workflow Integration:** Since the process happens entirely through your AI agent, you never have to leave your coding environment or break flow to clean data. ## How It Works The bottom line is: you start a big job, wait for confirmation on its status, then grab the final data set. 1. First, your agent calls `validate_bulk`, submitting the list of email addresses you need to check. This immediately returns a tracking ID. 2. Next, wait for processing. When prompted, call `get_validation_status` using that specific tracking ID to see if the job is done or estimate completion time. 3. Finally, once the status confirms readiness, the agent uses `get_validation_status` again to pull the complete validation results. ## Frequently Asked Questions **How do I check if my validation task is finished using No2Bounce? (get_validation_status)** You use `get_validation_status` with the tracking ID. This tool tells you if the job is 'Pending,' 'Processing,' or 'Complete.' You keep checking until it hits 'Complete' before pulling results. **Can I validate a huge list of emails at once using No2Bounce? (validate_bulk)** Yes, that's what `validate_bulk` is for. You submit the entire list in one go. This starts an asynchronous job and returns a tracking ID so you can track it later. **What happens if I forget the tracking ID with No2Bounce? (get_validation_status)** You can't retrieve status without the original tracking ID. You must capture this ID immediately after running `validate_bulk` to successfully use `get_validation_status` later. **Does No2Bounce only work for single emails? (validate_bulk)** No, that's a common mistake. While you *can* validate singles, the primary function is bulk processing. `validate_bulk` is designed to take lists of addresses. **When calling validate_bulk, what API credentials does No2Bounce require?** You need a valid No2Bounce API Token. You must pass this token through your AI client's configuration to authorize the tool call before submitting any list of emails. **If I run validate_bulk with improperly formatted email addresses, what happens?** The service performs initial input validation checks. It rejects malformed or non-standard inputs immediately and reports them in the batch summary before starting the main processing task. **Are there rate limits I need to know about when submitting data with validate_bulk?** The service handles large volumes, but usage is governed by your subscription plan. If you exceed a limit, the API will return an error code that your agent can catch and use for retries. **What specific data points does get_validation_status provide when my task finishes?** The status returns a detailed object. It provides counts for valid, invalid, disposable, and high-risk emails, plus the full breakdown you need to assess list quality. **How do I submit multiple emails for validation at once?** Use the `validate_bulk` tool and provide an array of email addresses in the `emailList` parameter. The server will return a `trackingId` which you can use to check the results. **How can I check if my bulk validation task is finished?** You can use the `get_validation_status` tool by providing the `trackingId` received during the submission. It will return the current progress or the final validation results. **Is there a way to prevent sending the same validation request twice?** Yes, when using `validate_bulk`, you can provide an optional `hashkey`. This unique string prevents duplicate requests from being processed within a 3-minute window.