NeverBounce MCP by usefulapi

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.

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.

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.

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.

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.

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.

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.

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.