ClearBounce Email Verification
net.clearbounce/email-verification
Verify email addresses in real time and find business email addresses with live mailbox checks.
— the operator's own registry description reported
Publisher net.clearbounce · first seen 2026-08-14 · endpoint https://clearbounce.net/mcp
Dependency rating derived
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
Cluster mid-solo · distinctiveness 0.331 (typical). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.
🔏 Signed receipt rr_bb863461e83a0eec1763223b · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (5 shown, 2026-08-14 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (2 events)
| date | type | what changed |
|---|---|---|
| 2026-08-30 | outcome | ok_tools (was auth_required) |
| 2026-08-14 | outcome | first probe: auth_required |
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| retrieval-public | 4 | serves public facts | truth-checkable against a public source — the V-ladder applies in full |
| action | 1 | changes the world | no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions |
Tools last seen observed
Harness readiness observed
Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.
| legibility check | tools passing | ok |
|---|---|---|
| name is clear & specific | 5/5 | ✓ |
| has a description | 5/5 | ✓ |
| description is substantive | 5/5 | ✓ |
| parameters are typed | 5/5 | ✓ |
| parameters are described | 5/5 | ✓ |
5 of 5 tools graded · 5 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Protocol conformance observed
Capabilities: tools
Drift observed
No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-09-06T06:17:51Z | ok_tools | 200 | 348 | 2025-06-18 |
| 2026-08-30T06:17:38Z | ok_tools | 200 | 348 | 2025-06-18 |
| 2026-08-23T06:14:49Z | auth_required | 401 | 318 | |
| 2026-08-16T06:14:11Z | auth_required | 401 | 311 | |
| 2026-08-14T20:00:32Z | auth_required | 401 | 315 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/net.clearbounce/email-verification)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.
Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →