Reoon MCP server

@pipeworx/reoon

Verify a single email address via Reoon Email Verifier (reoon.com), with an explicit catch-all flag in "power" mode. Part of enrich-waterfall's enrichverifyemail ordered verifiers (fleet #2860).

Part of Pipeworx — an MCP gateway connecting AI agents to 1745+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

only), score, disposable/role/disabled/spamtrap/free flags.

• reoonverify(email, mode?, apiKey) — status, catch-all (power mode

Auth

BYO only. Pass your Reoon API key as _apiKey (sent as the key QUERY PARAM, not a header — this is how Reoon's own docs specify it). Create a key at https://emailverifier.reoon.com/ -> API Settings. No platform key (D4).

Data sources

(quick/power mode).

• https://emailverifier.reoon.com/api/v1/verify — single email verify

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

{"reason":"Invalid API key.","status":"error"} — confirms the endpoint, that key is read as a query param, and that a bad key fails cleanly.

• Edge-probed live with an invalid key: HTTP 401

read 2026-10-08) — no successful live call made (no key held):

• Response shape from vendor docs (https://www.reoon.com/articles/api-documentation-of-reoon-email-verifier/,

isvalidsyntax, isdisposable, isroleaccount, mxacceptsmail, isspamtrap, isfreeemail, verification_mode: "quick" }

• quick: { email, status: valid|invalid|disposable|spamtrap,

catchall|roleaccount|spamtrap|unknown, overallscore, issafetosend, isvalidsyntax, isdisposable, isroleaccount, iscatchall, isdeliverable, isdisabled, isspamtrap, verificationmode: "power" } Only power mode exposes iscatchall — this pack defaults mode to "power" so enrichverifyemail always gets the field it needs; quick mode reports catchall: null rather than guessing.

• power: { email, status: safe|invalid|disabled|disposable|inbox_full|

overallscore; whether status: "unknown" (power mode) ever coincides with iscatch_all: true or is a separate signal.

• Not verified (no key held): exact scoring thresholds behind

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "reoon": {
      "url": "https://gateway.pipeworx.io/reoon/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/reoon/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1745+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

Shortened. The full README is on GitHub.