NeverBounce MCP by usefulapi
REMOTE · NEVERBOUNCE.USEFULAPI.IO
MCP server for NeverBounce — business email verification, credits and bulk jobs.
Available components
Last scanned (1 hour 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.03 → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 65
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://neverbounce.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 neverbounce.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | 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://neverbounce.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/neverbounce/ |
| http (plaintext) | http://neverbounce.usefulapi.io/mcp | Inconclusive | 302 | http://neverbounce.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 →
neverbounce_create_job Create a bulk verification job ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | yes | 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). |
No output schema declared.
No examples provided.
neverbounce_download_job_results Download job results as CSV ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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). |
No output schema declared.
No examples provided.
neverbounce_get_account_info Get account info and credits ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
neverbounce_get_job Get job status ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
No output schema declared.
No examples provided.
neverbounce_get_job_results Get job results (paged) ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items_per_page | integer | – | Results per page, 1-100 (default 25). |
| job_id | integer | yes | 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. |
No output schema declared.
No examples provided.
neverbounce_list_jobs List verification jobs ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
neverbounce_start_job Start a verification job ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
| max_credits | integer | yes | 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. |
No output schema declared.
No examples provided.
neverbounce_verify_email Verify one email address ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address_info | boolean | – | Also return the parsed address parts (addr, alias, host, domain, tld...). |
| string | yes | The one e-mail address to verify. | |
| timeout | integer | – | Seconds NeverBounce may spend before answering 'unknown' (1-60). Omit for the default. |
No output schema declared.
No examples provided.
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.
remote · neverbounce.usefulapi.io
claude mcp add --transport http io-usefulapi-neverbounce 'https://neverbounce.usefulapi.io/mcp'
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.