Clearout

io.clearoutPublished by clearout.ioOfficial publisherv1.0.0Updated Oct 29, 2026

Email verification, email finder and name validation from Clearout.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Clearout MCP server that lets an assistant verify email addresses, find email addresses and validate names through Clearout's service.

What you can do
  • Verify email addresses for validity and deliverability
  • Find email addresses associated with a person or company
  • Validate personal names
  • Available as a hosted remote endpoint or as a local npm package over stdio
When to use it
Useful when an assistant needs to clean or check contact lists, look up email addresses for outreach, or confirm that names and addresses in a CRM or dataset are valid before sending.
Requirements
A Clearout account and API token, supplied as the CLEAROUT_API_TOKEN environment variable. Either connect to the hosted remote endpoint or run the local npm package with Node.js. OAuth authentication is declared as required. Network access to Clearout's service.
Before you install
The API token is a secret and grants access to your Clearout account and any credits it holds; keep it out of shared configs. Email addresses and names submitted for lookup are sent to Clearout's third-party service, so avoid sending personal data you are not permitted to share. Lookups may consume paid account credits.

Installation

In SourceWeft

  1. Open Clearout in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.clearout%2Fclearout/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "clearout": {
      "type": "http",
      "url": "https://mcp.clearout.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.