NeverBounce MCP by usefulapi is an MCP server published by io.usefulapi, hosted at neverbounce.usefulapi.io. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 8 tools, including neverbounce_get_account_info, neverbounce_verify_email, neverbounce_list_jobs, neverbounce_get_job, neverbounce_get_job_results.
MCP server for NeverBounce — business email verification, credits and bulk jobs.
4,160 connections through 5 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
No parameters.
{
"name": "neverbounce_get_account_info",
"title": "Get account info and credits",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "Get account info and credits",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| email * | string | The one e-mail address to verify. |
| timeout | integer | Seconds NeverBounce may spend before answering 'unknown' (1-60). Omit for the default. |
| address_info | boolean | Also return the parsed address parts (addr, alias, host, domain, tld...). |
{
"name": "neverbounce_verify_email",
"title": "Verify one email address",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"maxLength": 254,
"minLength": 3,
"description": "The one e-mail address to verify."
},
"timeout": {
"type": "integer",
"maximum": 60,
"minimum": 1,
"description": "Seconds NeverBounce may spend before answering 'unknown' (1-60). Omit for the default."
},
"address_info": {
"type": "boolean",
"description": "Also return the parsed address parts (addr, alias, host, domain, tld...)."
}
}
},
"annotations": {
"title": "Verify one email address",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
}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.
| Parameter | Type | Description |
|---|---|---|
| page | integer | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| job_id | integer | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
| filename | string | Exact filename of the job. |
| job_status | string | Only jobs in this status. |
| items_per_page | integer | Results per page, 1-100 (default 25). |
{
"name": "neverbounce_list_jobs",
"title": "List verification jobs",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"page": {
"type": "integer",
"maximum": 100000,
"description": "Page number, from 1 (default 1). Pass the previous reply's next_page.",
"exclusiveMinimum": 0
},
"job_id": {
"type": "integer",
"maximum": 2147483647,
"description": "NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).",
"exclusiveMinimum": 0
},
"filename": {
"type": "string",
"maxLength": 255,
"minLength": 1,
"description": "Exact filename of the job."
},
"job_status": {
"enum": [
"under_review",
"queued",
"failed",
"complete",
"running",
"parsing",
"waiting",
"waiting_analyzed",
"uploading"
],
"type": "string",
"description": "Only jobs in this status."
},
"items_per_page": {
"type": "integer",
"maximum": 100,
"description": "Results per page, 1-100 (default 25).",
"exclusiveMinimum": 0
}
}
},
"annotations": {
"title": "List verification jobs",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| job_id * | integer | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
{
"name": "neverbounce_get_job",
"title": "Get job status",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"job_id"
],
"properties": {
"job_id": {
"type": "integer",
"maximum": 2147483647,
"description": "NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).",
"exclusiveMinimum": 0
}
}
},
"annotations": {
"title": "Get job status",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| page | integer | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| job_id * | integer | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
| items_per_page | integer | Results per page, 1-100 (default 25). |
{
"name": "neverbounce_get_job_results",
"title": "Get job results (paged)",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"job_id"
],
"properties": {
"page": {
"type": "integer",
"maximum": 100000,
"description": "Page number, from 1 (default 1). Pass the previous reply's next_page.",
"exclusiveMinimum": 0
},
"job_id": {
"type": "integer",
"maximum": 2147483647,
"description": "NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).",
"exclusiveMinimum": 0
},
"items_per_page": {
"type": "integer",
"maximum": 100,
"description": "Results per page, 1-100 (default 25).",
"exclusiveMinimum": 0
}
}
},
"annotations": {
"title": "Get job results",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| job_id * | integer | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
| valids | boolean | Include valid addresses (default true). |
| invalids | boolean | Include invalid addresses (default true). |
| unknowns | boolean | Include unknown addresses (default true). |
| catchalls | boolean | Include catch-all addresses (default true). |
| disposables | boolean | Include disposable addresses (default true). |
{
"name": "neverbounce_download_job_results",
"title": "Download job results as CSV",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"job_id"
],
"properties": {
"job_id": {
"type": "integer",
"maximum": 2147483647,
"description": "NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).",
"exclusiveMinimum": 0
},
"valids": {
"type": "boolean",
"description": "Include valid addresses (default true)."
},
"invalids": {
"type": "boolean",
"description": "Include invalid addresses (default true)."
},
"unknowns": {
"type": "boolean",
"description": "Include unknown addresses (default true)."
},
"catchalls": {
"type": "boolean",
"description": "Include catch-all addresses (default true)."
},
"disposables": {
"type": "boolean",
"description": "Include disposable addresses (default true)."
}
}
},
"annotations": {
"title": "Download job results as CSV",
"readOnlyHint": true,
"openWorldHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| emails * | array | 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). |
{
"name": "neverbounce_create_job",
"title": "Create a bulk verification job",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"emails"
],
"properties": {
"emails": {
"type": "array",
"items": {
"type": "string",
"maxLength": 254,
"minLength": 3
},
"maxItems": 100,
"minItems": 1,
"description": "The e-mail addresses to verify, 1-100."
},
"filename": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Name shown in the NeverBounce dashboard (default: a timestamped name)."
},
"leverage_historical_data": {
"type": "boolean",
"description": "Default true. Set false to use real-time verification only (no historical data)."
}
}
},
"annotations": {
"title": "Create a bulk verification job",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| job_id * | integer | NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job). |
| run_sample | boolean | Run only the free sample analysis instead of the full verification. |
| max_credits * | integer | The most credits you accept to spend (1-1000); the job is refused if its billable count is higher. |
{
"name": "neverbounce_start_job",
"title": "Start a verification job",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"job_id",
"max_credits"
],
"properties": {
"job_id": {
"type": "integer",
"maximum": 2147483647,
"description": "NeverBounce job id (from neverbounce_list_jobs or neverbounce_create_job).",
"exclusiveMinimum": 0
},
"run_sample": {
"type": "boolean",
"description": "Run only the free sample analysis instead of the full verification."
},
"max_credits": {
"type": "integer",
"maximum": 1000,
"minimum": 1,
"description": "The most credits you accept to spend (1-1000); the job is refused if its billable count is higher."
}
}
},
"annotations": {
"title": "Start a verification job",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": false,
"destructiveHint": true
}
}Tools for NeverBounce, hosted by usefulapi.io. If the user is new or asks what this server can do, suggest requests such as: "How many NeverBounce verification credits do I have left?"; "Show the progress and bounce estimate of my latest bulk verification job."; "Create a bulk job from the business email addresses I provide, without starting verification.". Read-only tools never change data; ask the user before a tool that creates, changes or deletes NeverBounce data. Free plan: 50 tool calls per month. Run neverbounce_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run neverbounce_request_feature to record the request. Paid plans: Pro (10,000 tool calls a month, $9/month or $90/year, for normal use) and Pro+ (100,000 tool calls a month, $39/month or $390/year, for automations and heavy use). A plan can be cancelled at any time and then runs to the end of the paid period, so it also suits a one-time job. When the user wants more calls or reaches the limit, run neverbounce_upgrade without a plan: it returns both plans, each with a payment link for the user to open. neverbounce_cancel_subscription cancels Pro at the end of the paid period.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.