@pipeworx/millionverifier

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/millionverifier’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 1

Verify a single email address via MillionVerifier (millionverifier.com). Part of enrich-waterfall’s enrich_verify_email ordered verifiers (fleet #2860).

Tools

• millionverifier_verify(email, timeout?, _apiKey) — result (ok/catch_all/disposable/invalid/unknown), explicit catch_all boolean, quality, free/role flags.

Auth

BYO only. Pass your MillionVerifier API key as _apiKey (sent as the api QUERY PARAM on a GET request). Find your key at https://app.millionverifier.com/api. No platform key (D4).

Data sources

• https://api.millionverifier.com/api/v3/ — single email verify.

Verification notes (fleet #2860, 2026-10-08, no vendor key held)

• TRAP, confirmed live by edge probe: MillionVerifier returns HTTP 200 on an auth failure. Invalid key:

  GET https://api.millionverifier.com/api/v3/?api=invalidkey123&[email protected]
  -> HTTP 200
  {"email":"[email protected]","result":"error","resultcode":4,"subresult":"",
   "free":false,"role":false,"didyoumean":"","credits":0,"executiontime":0,
   "error":"Apikey not found","livemode":true}

  A res.ok check alone would not catch this — the pack checks result === 'error' (or a present error string) and throws, rather than handing back result: "error" as though it were a verdict about the email address. This is exactly the silent-200 shape the house rules flag: a 200 with a payload that LOOKS like a normal result but means “the call itself failed.”
• Response field names and catch_all representation confirmed from vendor docs (https://developer.millionverifier.com/, read 2026-10-08): result includes catch_all as a first-class value (not a separate flag on top of “ok”) — this pack derives catch_all: result === 'catch_all' so the caller still gets a stable boolean field.
• Not verified (no key held): the full enumeration of result values beyond what the docs and the error probe showed (ok, catch_all, unverified, invalid, unknown, disposable, error were all that surfaced); exact resultcode -> result mapping.

Tools

• millionverifier_verify — Verify a single email address with MillionVerifier. Returns result (ok/catch_all/disposable/invalid/unknown), a quality label, and free/role flags. Example: millionverifier_verify({ email: “jane@strip