# NeverBounce MCP by usefulapi (remote · neverbounce.usefulapi.io)

MCP server for NeverBounce — business email verification, credits and bulk jobs.

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

## Components

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

## Channel facts

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

## 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 NeverBounce MCP by usefulapi server?

NeverBounce MCP by usefulapi is a hosted endpoint at https://neverbounce.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-neverbounce 'https://neverbounce.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-neverbounce": {
      "type": "http",
      "url": "https://neverbounce.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-02 (score 18, −47)

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

### 2026-11-01 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 65)

First indexed and scored.

## MCP tools (8)

### `neverbounce_get_account_info` (~48 tokens)

Get account info and credits

Credits left (paid and free), credits used, and how many verification jobs are completed, queued, processing or under review. Free: it spends no credits. POST /account/info.

### `neverbounce_verify_email` (~198 tokens)

Verify one email address

WRITE: SPENDS 1 of your NeverBounce credits per call. Verifies ONE e-mail address and returns result (valid, invalid, disposable, catchall or unknown), flags (e.g. has_dns_mx, role_account, free_email_host), a suggested correction for typos like gmal.com, and optionally the parsed address parts. NeverBounce's usage rules: use this for a single address at the point of entry; do NOT call it in a loop over a list or database (the account can be locked) - use neverbounce_create_job for lists. POST /single/check.

Input parameters:

- `address_info` (boolean): Also return the parsed address parts (addr, alias, host, domain, tld...).
- `email` (string, required): The one e-mail address to verify.
- `timeout` (integer): Seconds NeverBounce may spend before answering 'unknown' (1-60). Omit for the default.

### `neverbounce_list_jobs` (~170 tokens)

List verification jobs

Bulk verification jobs of the account (most recent first as NeverBounce returns them) with id, status, filename, timestamps, totals per result (valid, invalid, catchall, disposable, unknown, duplicates, bad_syntax), bounce estimate and percent complete. Filter by id, exact filename or status. POST /jobs/search.

Input parameters:

- `filename` (string): Exact filename of the job.
- `items_per_page` (integer): Results per page, 1-100 (default 25).
- `job_id` (integer): NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).
- `job_status` (string): Only jobs in this status.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `neverbounce_get_job` (~106 tokens)

Get job status

One verification job: status (waiting, parsing, running, complete, failed, under_review...), failure reason, timestamps, totals (records, billable = credits it will use, processed, valid, invalid, catchall, disposable, unknown, duplicates, bad_syntax), bounce estimate and percent complete. Poll this until status is complete. POST /jobs/status.

Input parameters:

- `job_id` (integer, required): NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).

### `neverbounce_get_job_results` (~132 tokens)

Get job results (paged)

Per-address results of a job: the submitted row (data) and its verification (result, flags, suggested_correction, address info). Paged; use neverbounce_download_job_results for a CSV. The job must be complete. POST /jobs/results.

Input parameters:

- `items_per_page` (integer): Results per page, 1-100 (default 25).
- `job_id` (integer, required): NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `neverbounce_download_job_results` (~169 tokens)

Download job results as CSV

The results of a complete job as CSV text (the submitted columns plus email_status), cut at 200000 characters with a note when longer (use neverbounce_get_job_results to page through large jobs). By default every result type is included; set a type to false to leave it out. POST /jobs/download.

Input parameters:

- `catchalls` (boolean): Include catch-all addresses (default true).
- `disposables` (boolean): Include disposable addresses (default true).
- `invalids` (boolean): Include invalid addresses (default true).
- `job_id` (integer, required): NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).
- `unknowns` (boolean): Include unknown addresses (default true).
- `valids` (boolean): Include valid addresses (default true).

### `neverbounce_create_job` (~180 tokens)

Create a bulk verification job

WRITE: creates a bulk verification job from up to 100 e-mail addresses given in this call, and has NeverBounce parse it. It does NOT start the verification and spends NO credits; run neverbounce_start_job afterwards (that spends 1 credit per billable address). Put ALL the addresses of one list into ONE job: NeverBounce's rules allow 10 concurrent jobs and 50 runs a day, and many small jobs in a short time can get the account locked. Returns the job_id. POST /jobs/create.

Input parameters:

- `emails` (array, required): The e-mail addresses to verify, 1-100.
- `filename` (string): Name shown in the NeverBounce dashboard (default: a timestamped name).
- `leverage_historical_data` (boolean): Default true. Set false to use real-time verification only (no historical data).

### `neverbounce_start_job` (~195 tokens)

Start a verification job

WRITE: STARTS a created job and SPENDS 1 credit per billable address (shown as total.billable in neverbounce_get_job); it cannot be stopped or undone. Safety: you must pass max_credits, and the job is refused when its billable count is above it or above 1000 (start bigger jobs in the NeverBounce dashboard). The job must be in status waiting or waiting_analyzed. With run_sample true it only runs the free sample analysis (estimated bounce rate) and spends nothing. POST /jobs/start.

Input parameters:

- `job_id` (integer, required): NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).
- `max_credits` (integer, required): The most credits you accept to spend (1-1000); the job is refused if its billable count is higher.
- `run_sample` (boolean): Run only the free sample analysis instead of the full verification.

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 65
- 2026-10-31: 65

## Common questions

### What is the NeverBounce MCP by usefulapi server?

NeverBounce MCP by usefulapi is listed in the public MCP registry as io.usefulapi/neverbounce. MCP server for NeverBounce, business email verification, credits and bulk jobs. This page covers its hosted endpoint (https://neverbounce.usefulapi.io/mcp).

### Is the NeverBounce MCP by usefulapi server safe to use?

NeverBounce 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 NeverBounce MCP by usefulapi server expose?

NeverBounce MCP by usefulapi exposes 8 tools: neverbounce_get_account_info, neverbounce_verify_email, neverbounce_list_jobs, neverbounce_get_job, neverbounce_get_job_results, and 3 more. Their descriptions and schemas cost roughly 1,198 tokens of context every time the server is loaded.

### Does the NeverBounce MCP by usefulapi server require authentication?

Its publisher declares no required credentials for NeverBounce 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 NeverBounce MCP by usefulapi server still maintained?

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

### What did VerifyMCP test on the NeverBounce MCP by usefulapi server?

VerifyMCP ran 4 checks on NeverBounce MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about NeverBounce MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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