BounceBan MCP by usefulapi
REMOTE · BOUNCEBAN.USEFULAPI.IO
Check BounceBan credits, verify emails and read asynchronous bulk verification results.
Available components
Last scanned (2 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 −45
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_credits_and_account_limits” functional
- New prompt “review_an_existing_bulk_task_s_results” functional
- New prompt “verify_a_contact_list_in_bulk” functional
- New prompt “verify_a_single_contact_address” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.2 → 1.1.0 functional
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.1 → 1.0.2 functional
- Server version: 1.0.0 → 1.0.1 functional
- 29 Oct 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bounceban.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bounceban.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bounceban.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/bounceban/ |
| http (plaintext) | http://bounceban.usefulapi.io/mcp | Inconclusive | 302 | http://bounceban.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bounceban_account Read BounceBan credits and rate limits ~34
Read verification credit balance and account rate limits without starting verification. Limits and credit balance are shared across the account's API keys.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bounceban_bulk_results Read one page of BounceBan bulk results ~102
Read up to 100 existing email results and a cursor for the next page. Results are retained for 90 days. No verification is started and no following page is fetched automatically. Omit state to get all processed results while a task is running; filtering by state can omit in-progress results. A pending response means wait and check the existing task later.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| id | string | yes | – |
| state | string | – | – |
No output schema declared.
No examples provided.
bounceban_bulk_status Read BounceBan bulk task progress ~57
Read progress and aggregate results of an existing bulk task. Does not start verification. Wait between polls and honor account rate limits. importing/verifying status is still pending; finished means the task has ended.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
bounceban_create_bulk_verification Create a BounceBan bulk verification ~124
Submit 1–1,000 emails for regular-mode asynchronous verification. Starts a task and can consume verification credits; requires confirm:true. Check the dashboard before resubmitting after a lost/invalid response. greylisting_bypass:auto balances speed and accuracy; speed may yield more risky results; robust waits longer. No callbacks or automatic polling are configured.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| disable_catchall_verify | boolean | – | – |
| emails | array | yes | – |
| greylisting_bypass | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
bounceban_single_status Read a BounceBan single verification ~75
Read an existing single verification ID without spending verification credits. Returns success, verifying or queue. Honor try_again_at when provided; poll no more than 10 times for an ID within 5 minutes, then stop. Results remain available for 90 days. This tool never starts another verification.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
bounceban_verify_email Start BounceBan email verification ~120
Verify one email in regular mode. Costs verification credits on each request, including repeats, and requires confirm:true. Uses the standard API's 15-second result window; returns a final result or a queue/verifying task ID. Read that existing ID with bounceban_single_status later. Never resubmit simply because it is still pending. Basic-only mode can return unknown with score -1 for catch-all/SEG-protected addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| disable_catchall_verify | boolean | – | – |
| string | yes | – |
No output schema declared.
No examples provided.
How do I install the BounceBan MCP by usefulapi server?
BounceBan MCP by usefulapi is a hosted endpoint at https://bounceban.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bounceban.usefulapi.io
claude mcp add --transport http io-usefulapi-bounceban 'https://bounceban.usefulapi.io/mcp'
What is the BounceBan MCP by usefulapi server?
BounceBan MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bounceban. Check BounceBan credits, verify emails and read asynchronous bulk verification results. This page covers its hosted endpoint (https://bounceban.usefulapi.io/mcp).
Is the BounceBan MCP by usefulapi server safe to use?
BounceBan MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BounceBan MCP by usefulapi server expose?
BounceBan MCP by usefulapi exposes 6 tools: bounceban_account, bounceban_verify_email, bounceban_single_status, bounceban_create_bulk_verification, bounceban_bulk_status, bounceban_bulk_results. Their descriptions and schemas cost roughly 512 tokens of context every time the server is loaded.
Does the BounceBan MCP by usefulapi server require authentication?
Its publisher declares no required credentials for BounceBan MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the BounceBan MCP by usefulapi server still maintained?
BounceBan MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.