MCP server for NeverBounce — business email verification, credits and bulk jobs. For B2B sales, marketing, recruiting and business development teams with a NeverBounce account. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"neverbounce": {
"url": "https://neverbounce.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"neverbounce": {
"type": "http",
"url": "https://neverbounce.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
Read your credit balance and the number of jobs in each processing state.
neverbounce_get_account_info
List jobs, inspect a selected job and page through its verification results.
neverbounce_list_jobs neverbounce_get_job neverbounce_get_job_results
Create a bulk job from the addresses you provide without starting paid verification. Start it separately with a maximum credit allowance.
Changes data · neverbounce_create_job neverbounce_start_job
Check one address at its point of entry. Each check spends vendor credits; existing lists should use bulk jobs.
Changes data · neverbounce_verify_email
The login page asks for your NeverBounce API key.
Create a Custom Integration app in the NeverBounce dashboard (Apps → Custom Integration) and copy the key (secret_...) from its overview page. Use a V4 key; old V3 credentials do not work. Verifying addresses and starting jobs spends your NeverBounce credits. Use a dedicated Custom Integration key; only connect systems authorized to process these business contacts. Requested addresses, job results and account-credit information pass to your chosen AI client and its LLM provider; verifying addresses sends them to NeverBounce and spends vendor credits. Three write tools verify one address, create a bulk job, or start/sample a job; they do not send email. Single checks are for point-of-entry use, not loops over lists. Review NeverBounce data-contribution privacy settings and terms, which govern its use of business contact data. Reset this app key in NeverBounce to stop access. Billing is per key and changes if it is reset.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your NeverBounce API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the NeverBounce connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
neverbounce_get_account_info | read | 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 | write | 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. |
neverbounce_list_jobs | read | 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. |
neverbounce_get_job | read | 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. |
neverbounce_get_job_results | read | 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. |
neverbounce_download_job_results | read | 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. |
neverbounce_create_job | write | 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. |
neverbounce_start_job | write | 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. |
neverbounce_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
neverbounce_request_feature | Request a missing feature Tell usefulapi that the user needs something the NeverBounce tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
neverbounce_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on NeverBounce (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
neverbounce_cancel_subscription | Cancel the Pro subscription Cancel the caller's NeverBounce Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run neverbounce_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper Custom Integration API key | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this NeverBounce server only. Subscribe with neverbounce_upgrade (it returns a Stripe Checkout link). Cancel any time with neverbounce_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running neverbounce_upgrade before then undoes the cancel. Or write to [email protected].
Check remaining verification credits. Review a bulk verification job. Prepare a business contact list. Verify a newly entered business email. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by NeverBounce. The server calls the NeverBounce API with your own NeverBounce access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your NeverBounce API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your NeverBounce API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the NeverBounce API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in NeverBounce.
Yes, if you approve it. 3 of the 8 NeverBounce tools can create or change data. The other 5 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this NeverBounce server only. Cancel any time: Pro then runs to the end of the paid period. Run neverbounce_usage_status to see how many calls you used.
Ask the AI to run neverbounce_upgrade: it returns a Stripe Checkout link. To cancel, run neverbounce_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with neverbounce_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.