Skip to content

ClearBounce Email Verification MCP server

net.clearbounce/email-verificationclearbounce.netstreamable-httpv1.0.0Scanned

Verify email addresses in real time and find business email addresses with live mailbox checks.

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ClearBounce Email Verification MCP server can do

The ClearBounce Email Verification MCP server is published by clearbounce.net, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: verify_email and verify_bulk), but cannot delete data. 4 tools only read.

1 tool reads private data (find_email); 3 tools bring in text other people can write (verify_email, find_email and verify_bulk).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • verify_bulkVerify 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 verifyin…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. Costs 1 credit per unique address; duplicates are removed for free. Returns a jobId immediately (the job runs in the background, roughly 1-10 minutes depending on size). Use check_bulk_status with the jobId to get progress and the final summary. Before starting a large list, confirm with the user that spending that many credits is intended.

    Annotations the server declares

    • title: Verify Email List (Bulk)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • verify_emailVerify a single email address in real time with a live mailbox check.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify a single email address in real time with a live mailbox check. Returns status (deliverable, undeliverable, risky, unknown), a sub-status reason, a 0-100 quality score, and detailed checks (syntax, MX records, disposable, role-based, catch-all, typo detection). Costs 1 credit per call.

    Annotations the server declares

    • title: Verify Email Address
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • check_bulk_statusCheck the progress of a bulk verification job started with verify_bulk.No findings

    Why it is in this group

    • The name "check_bulk_status" says "status": a word for reading.
    Description, as the server wrote it
    Check the progress of a bulk verification job started with verify_bulk. Free. Returns status (pending, processing, completed, failed), percent progress, and — once completed — the summary counts (deliverable, undeliverable, risky, unknown, catch-all). Report the summary to the user; when they need the result for each address, call get_bulk_results. The full result file can also be downloaded from the ClearBounce dashboard.

    Annotations the server declares

    • title: Check Bulk Job Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_creditsReturn the remaining verification credit balance for the account that owns the API key.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Return the remaining verification credit balance for the account that owns the API key. Free.

    Annotations the server declares

    • title: Check Credit Balance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_emailFind a person's business email address from their full name and company domain.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "find_email" says "find": a word for reading.

    What it can reach

    • private-dataThe name "find_email" says "find" and "email": it reads mail.
    • private-dataThe description's first sentence says "find" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "find_email" says "find" and "email": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Find a person's business email address from their full name and company domain. Returns candidate addresses with confidence scores, based on published sources and common company address patterns. Finding is free, but candidates are pattern-based guesses until verified. After showing the candidates, tell the user that confirming deliverability costs 1 credit per candidate checked, and ask before verifying. With approval, call verify_email on candidates one at a time starting from the highest confidence, and stop at the first deliverable result.

    Annotations the server declares

    • title: Find Business Email Address
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_bulk_resultsGet the per-address results of a completed verify_bulk job: status, sub-status and score for each address.No findings

    Why it is in this group

    • The name "get_bulk_results" says "get": a word for reading.
    Description, as the server wrote it
    Get the per-address results of a completed verify_bulk job: status, sub-status and score for each address. Free — no credits. Use this when the user needs to know which addresses passed or failed; do not re-verify them with verify_email. Optionally filter by status, and page through large jobs with offset (up to 500 results per call).

    Annotations the server declares

    • title: Get Bulk Job Results
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://clearbounce.net/.well-known/oauth-protected-resource/mcp
Authorization servers
https://clearbounce.net
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://clearbounce.net/mcp: tools/list returned 6 tools to an anonymous client, including verify_email (write), verify_bulk (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http email-verification https://clearbounce.net/mcp --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http email-verification https://clearbounce.net/mcp --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__email-verification__find_email",
      "mcp__email-verification__check_bulk_status",
      "mcp__email-verification__get_bulk_results",
      "mcp__email-verification__check_credits"
    ],
    "ask": [
      "mcp__email-verification__verify_email",
      "mcp__email-verification__verify_bulk"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as email-verification. Review it before you use it.

Capability tags behind 3 rules
  • mcp__email-verification__verify_email untrusted-input
  • mcp__email-verification__find_email private-data, untrusted-input
  • mcp__email-verification__verify_bulk untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.clearbounce/email-verification/verify?hash=5ec35bb081c56583366da93af3a8e406c8b1ffc380749b6adc455797bf2f074a" | jq -e '.changed == false'

Pinned hash 5ec35bb081c5, from Nov 18, 2026, 19:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.clearbounce/email-verification/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.clearbounce/email-verification
[![Anlyon Radar](https://radar.anlyon.com/badge/net.clearbounce/email-verification.svg)](https://radar.anlyon.com/servers/net.clearbounce/email-verification)

Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.

ClearBounce Email Verification MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ClearBounce Email Verification MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ClearBounce Email Verification MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ClearBounce Email Verification MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ClearBounce Email Verification MCP server have?

6 tools: 2 write, 4 read. verify_email, verify_bulk, find_email, check_bulk_status, get_bulk_results and check_credits.

Does the ClearBounce Email Verification MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ClearBounce Email Verification MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ClearBounce Email Verification MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 5, 2026. Every change is on this page and in its Atom feed.