# BounceBan MCP by usefulapi (remote · bounceban.usefulapi.io)

Check BounceBan credits, verify emails and read asynchronous bulk verification results.

- Trust score: 18/100 (low)
- Change this week: −41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `bounceban.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-bounceban/bounceban.md), [page](https://verifymcp.io/servers/io-usefulapi-bounceban/bounceban)

## Channel facts

- Endpoint: `https://bounceban.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-bounceban 'https://bounceban.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-bounceban": {
      "url": "https://bounceban.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-bounceban": {
      "type": "http",
      "url": "https://bounceban.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-bounceban]
url = "https://bounceban.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-bounceban": {
      "type": "remote",
      "url": "https://bounceban.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-bounceban --url 'https://bounceban.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-bounceban:
    url: "https://bounceban.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-bounceban": {
      "Transport": "http",
      "Url": "https://bounceban.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-bounceban -t streamable-http -u 'https://bounceban.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-bounceban": {
      "type": "http",
      "url": "https://bounceban.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 18, −45)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 63, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] 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

### 2026-10-30 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.1 → 1.0.2
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-29 (score 59)

First indexed and scored.

## MCP tools (6)

### `bounceban_account` (~34 tokens)

Read BounceBan credits and rate limits

Read verification credit balance and account rate limits without starting verification. Limits and credit balance are shared across the account's API keys.

### `bounceban_verify_email` (~120 tokens)

Start BounceBan email verification

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.

Input parameters:

- `confirm` (boolean)
- `disable_catchall_verify` (boolean)
- `email` (string, required)

### `bounceban_single_status` (~75 tokens)

Read a BounceBan single verification

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.

Input parameters:

- `id` (string, required)

### `bounceban_create_bulk_verification` (~124 tokens)

Create a BounceBan bulk verification

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.

Input parameters:

- `confirm` (boolean)
- `disable_catchall_verify` (boolean)
- `emails` (array, required)
- `greylisting_bypass` (string)
- `name` (string)

### `bounceban_bulk_status` (~57 tokens)

Read BounceBan bulk task progress

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.

Input parameters:

- `id` (string, required)

### `bounceban_bulk_results` (~102 tokens)

Read one page of BounceBan bulk results

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.

Input parameters:

- `cursor` (string)
- `id` (string, required)
- `state` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-bounceban/bounceban#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 63
- 2026-10-30: 60
- 2026-10-29: 59

## Common questions

### 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.

## Links

- Remote endpoint: https://bounceban.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/bounceban/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-bounceban/bounceban.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-bounceban/bounceban.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-bounceban/bounceban