Reoon

io.github.pipeworx-iov0.1.0更新于 Oct 9, 2026

Reoon MCP — wraps the Reoon Email Verifier API (reoon.com)

已验证Streamable HTTP可网页运行Business & Commerce Data & Analytics

概览

AI 生成的概览

通过 Reoon Email Verifier API 验证单个电子邮件地址，返回状态、catch-all、评分和可投递性标记。

功能: 将 Reoon Email Verifier API 封装为一个工具 reoon_verify，接收电子邮件地址和可选的 mode 参数。它返回状态、总体评分，以及一次性邮箱、角色账户、已停用、垃圾陷阱、免费邮箱、语法有效性和 MX 接受等标记。power 模式还会额外提供 is_catch_all 和 is_deliverable；该包默认使用 power 模式，因此始终会报告 catch-all。远程端点还会列出共享的网关元工具，例如 ask_pipeworx、discover_tools 和 remember/recall。
适用场景: 当助手需要在发送前检查电子邮件地址是否可投递，或通过过滤无效、一次性、角色或 catch-all 地址来清理地址列表时使用。它适合单地址检查即可满足的丰富化和潜在客户验证工作流。
运行要求: 需要 Reoon API 密钥，通过 _apiKey 参数传入，并以 key 查询参数发送。远程端点为 Pipeworx 账户；本地 stdio 版本可通过 npx @pipeworx/mcp-reoon 运行，需要 Node.js。需要访问 Reoon API 的网络连接。

安装前请注意

Reoon API 密钥以名为 key 的查询参数传递，因此可能出现在 URL 和日志中。验证会将待检查的电子邮件地址发送给第三方服务 Reoon。README 说明该集成是非官方的，与上游提供商无关联，并且测试期间未进行成功的实际调用，因此文档所述响应结构之外的细节尚未验证。

安装

在 SourceWeft 中

打开控制台中的 Reoon，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

README

@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 enrich_verify_email 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

reoon_verify(email, mode?, _apiKey) — status, catch-all (power mode only), score, disposable/role/disabled/spamtrap/free flags.

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

https://emailverifier.reoon.com/api/v1/verify — single email verify (quick/power mode).

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

Edge-probed live with an invalid key: HTTP 401 {"reason":"Invalid API key.","status":"error"} — confirms the endpoint, that key is read as a query param, and that a bad key fails cleanly.
Response shape from vendor docs (https://www.reoon.com/articles/api-documentation-of-reoon-email-verifier/, read 2026-10-08) — no successful live call made (no key held):
- quick: { email, status: valid|invalid|disposable|spamtrap, is_valid_syntax, is_disposable, is_role_account, mx_accepts_mail, is_spamtrap, is_free_email, verification_mode: "quick" }
- power: { email, status: safe|invalid|disabled|disposable|inbox_full| catch_all|role_account|spamtrap|unknown, overall_score, is_safe_to_send, is_valid_syntax, is_disposable, is_role_account, is_catch_all, is_deliverable, is_disabled, is_spamtrap, verification_mode: "power" } Only power mode exposes is_catch_all — this pack defaults mode to "power" so enrich_verify_email always gets the field it needs; quick mode reports catch_all: null rather than guessing.
Not verified (no key held): exact scoring thresholds behind overall_score; whether status: "unknown" (power mode) ever coincides with is_catch_all: true or is a separate signal.

Quick Start

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

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 — ask_pipeworx, discover_tools, 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:

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

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/reoon_verify. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

json

{  "mcpServers": {    "reoon": {      "command": "npx",      "args": ["-y", "@pipeworx/mcp-reoon"]    }  }}

{  "mcpServers": {    "reoon": {      "command": "npx",      "args": ["-y", "@pipeworx/mcp-reoon"]    }  }}

Or run it directly to confirm it starts:

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

The gateway picks the right tool and fills the arguments automatically.

License

MIT

来源：README.md，提交 5f101b8

工具

工具元数据尚未被收录。

版本历史

v0.1.0最新Oct 9, 2026