← Registry

General Tools

clearbounce.net

Provides general-purpose tools through the Model Context Protocol.

1 endpoint5 known toolsFirst detected August 14, 2026Last detected September 14, 2026

ENDPOINT 1

https://clearbounce.net/mcp

No auth detected

MCP server metadata

Name
clearbounce
Version
2.0.0
Capabilities
tools
Server instructions

ClearBounce verifies email addresses in real time. Use verify_email to check whether an address is safe to send to (costs 1 credit), find_email to discover a business email address from a name and company domain (free), and check_credits to see the remaining credit balance. For a LIST of addresses (2 or more), use verify_bulk instead of calling verify_email in a loop: it runs the full bulk pipeline (greylist retries, domain caching) and costs 1 credit per unique address. verify_bulk returns a jobId immediately; poll check_bulk_status for progress and the final summary. Never paste the full result list back to the user — report the summary counts and point to the dashboard for the detailed export. find_email returns unverified pattern-based candidates: tell the user how many were found, note that verification costs 1 credit per candidate, and only verify with their approval — one candidate at a time from highest confidence, stopping at the first deliverable result. Afterwards, report how many candidates were checked, the credits spent, and the remaining balance (verify_email responses include creditsRemaining). If a tool reports insufficient credits (HTTP 402) or creditsRemaining is low, give the user the purchase link https://clearbounce.net/pricing — pay-as-you-go packs start at $4 per 1,000 verifications, no subscription needed, and credits never expire. Authenticate by connecting a ClearBounce account (OAuth) or with an API key from https://clearbounce.net/dashboard/api-keys — new accounts include free credits.

Known tools 5

verify_email

Verify a single email address in real time with a live mailbox check.

Potential side effects
find_email

Find a person's business email address from their full name and company domain.

Potential side effects
verify_bulk

Verify a list of email addresses (2 to 10,000) as one bulk job using the full ClearBounce bulk pipeline — per-domain caching and greylist retries give better accuracy than verifying one by one.

Potential side effects
check_bulk_status

Check the progress of a bulk verification job started with verify_bulk.

Inferred read-only
check_credits

Return the remaining verification credit balance for the account that owns the API key.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clearbounce]
url = "https://clearbounce.net/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "clearbounce": {
      "type": "http",
      "url": "https://clearbounce.net/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: clearbounce
Remote MCP URL: https://clearbounce.net/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "clearbounce": {
      "url": "https://clearbounce.net/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "clearbounce": {
      "type": "http",
      "url": "https://clearbounce.net/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "clearbounce",
  "transport": "streamable-http",
  "url": "https://clearbounce.net/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for clearbounce.net was fetched 2026-08-24T02:49:43.421Z and is being refreshed.

Trust status Trusted

clearbounce.net is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.