Integration

Clearout integration

Clearout verifies and finds email addresses. Verify one address in real time (deliverability, safe-to-send verdict, sub-status, disposable, free, role and gibberish flags), run the catch-all or business-account check alone, find a person's email from a name and a company domain, look up a company's domains, MX records and WHOIS record, reverse-lookup a LinkedIn profile, email or domain, validate a person's name, read credits, plan and rate limits, and follow, download, cancel or remove bulk verify and bulk finder lists. Uploading a new bulk list (a multipart file upload) is left to the Clearout app, the standalone disposable, free, role and gibberish checks are left out (verify_email returns those flags), and the legacy credits route is replaced by get_remaining_credits. Authentication is an API token created in the Clearout app (Developer, API) and sent as Authorization: Bearer <token>.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Clearout.Built from the 25 Clearout tools below, on the connection you add once.

What you can do with Clearout

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Bulk finder list, 4 operations

  • cancel_bulk_finder_listCancel bulk finder listPOSTCancel a bulk finder list that is still running, by list_id.
  • get_bulk_finder_progressGet bulk finder progressGETGet the progress of a bulk finder list by its list_id: data.progress_status and data.percentage (the percentage done). When complete, call download_bulk_finder_result.
  • list_bulk_finder_listsList bulk finder listsPOSTList your bulk finder lists with cursor pagination: pass page_info.last_cursor as start_after for the next page.
  • remove_bulk_finder_listRemove bulk finder listPOSTPermanently remove a bulk finder list and its results, by list_id. Removal is refused while a download is in progress unless ignore_result is true.

Bulk verify list, 4 operations

  • cancel_bulk_verify_listCancel bulk verify listPOSTCancel a bulk verify list that is still running, by list_id.
  • get_bulk_verify_progressGet bulk verify progressGETGet the progress of a bulk verify list by its list_id: data.progress_status and data.percentile (the percentage done). When complete, call download_bulk_verify_result.
  • list_bulk_verify_listsList bulk verify listsPOSTList your bulk verify lists, newest first, with cursor pagination: pass page_info.last_cursor as start_after for the next page. Filter by date range, verification status or source.
  • remove_bulk_verify_listRemove bulk verify listPOSTPermanently remove a bulk verify list and its results, by list_id. Removal is refused while a download is in progress unless ignore_result is true.

Email, 4 operations

  • find_emailFind emailPOSTFind a person's email from their name and a company domain or name. If the search times out, error.additional_info.queue_id is returned: pass it as qid to get_email_finder_queue_status.
  • verify_business_emailVerify business emailPOSTCheck only whether an email address belongs to a business (work) account rather than a free mailbox. For a full deliverability verdict use verify_email.
  • verify_catch_all_emailVerify catch all emailPOSTCheck only whether an email address's domain is catch-all (its mail server accepts every address). For a full deliverability verdict use verify_email.
  • verify_emailVerify emailPOSTVerify one email address in real time and get its status, safe_to_send verdict, sub_status and disposable, free, role and gibberish flags.

Company, 2 operations

  • autocomplete_companyAutocomplete companyGETFind the website domains matching a company name, domain or URL, with a confidence score and logo for each. A free API per the vendor; it works without a token.
  • reverse_lookup_domainReverse lookup domainGETGet company information (name, LinkedIn page, location) from a domain name.

Lead, 2 operations

  • reverse_lookup_emailReverse lookup emailGETGet lead information (name, title, company, location) from an email address.
  • reverse_lookup_linkedinReverse lookup linkedinGETGet lead information (name, title, company, location) from a LinkedIn profile URL.

Bulk finder result, 1 operation

  • download_bulk_finder_resultDownload bulk finder resultPOSTGet a download URL (data.url) for the results file of a completed bulk finder list, by list_id.

Bulk verify result, 1 operation

  • download_bulk_verify_resultDownload bulk verify resultPOSTGet a download URL (data.url) for the results file of a completed bulk verify list, by list_id.

Credit, 1 operation

  • get_remaining_creditsGet remaining creditsGETGet the account's remaining credits: total, and the split between subscription and bonus credits.

Domain mx, 1 operation

  • find_domain_mxFind domain mxPOSTGet the MX records of a domain, highest priority first.

Domain whois, 1 operation

  • find_domain_whoisFind domain whoisPOSTGet the WHOIS record of a domain as JSON: registrar, registrant and its admin and tech contacts, status codes and creation date.

Email finder queue, 1 operation

  • get_email_finder_queue_statusGet email finder queue statusGETGet the result of a find_email search that timed out and continued in the background, by its queue id (qid).

Limit, 1 operation

  • get_service_limitsGet service limitsGETGet the account's rate limits (requests per minute) and bulk concurrency limits per service, with what remains.

Name, 1 operation

  • validate_nameValidate namePOSTCheck whether a person's name looks legitimate: returns a status plus profanity and gibberish flags for the name.

Plan, 1 operation

  • get_plans_and_addonsGet plans and addonsGETGet the account's current plan and add-ons: name, status, type, charge and next renewal dates.

Use Clearout from Claude Code, Cursor or Codex

Connect Clearout in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Clearout operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Clearout

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Clearout once

    Add your Clearout connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Clearout integration FAQ

What can you do with the Clearout integration?

LiveContext exposes 25 operations on Clearout, covering bulk finder list, bulk verify list, email and company.

Popular integrations

Browse the whole catalog