Reoon

What Reoon MCP server does

The Reoon MCP server exposes one email-verification operation through MCP: reoon_verify. It connects to Reoon's single-address verification endpoint at https://emailverifier.reoon.com/api/v1/verify and returns the provider's classification and verification fields.

The tool supports two modes. Quick mode reports statuses such as valid, invalid, disposable, or spamtrap, along with syntax, disposable, role-account, MX, spamtrap, and free-email indicators. Power mode returns statuses including safe, invalid, disabled, disposable, inbox full, catch-all, role account, spamtrap, and unknown. It also provides an overall score, delivery-related fields, and the catch-all flag.

How it works

Call reoon_verify with an email address, optionally select quick or power, and provide your own Reoon API key through _apiKey. The key is sent in the key query parameter rather than an HTTP header, matching Reoon's documented API behavior.

Power is the default mode. This preserves the is_catch_all field needed when distinguishing catch-all mailboxes from other results. Quick mode does not determine catch-all status; its catch-all value is null rather than an inferred result.

The package can run as a local stdio MCP server or through the Pipeworx gateway. The gateway's Reoon endpoint lists this pack's tool together with shared Pipeworx meta-tools. A full gateway connection exposes the catalog through the same routing layer, while the local package exposes only the Reoon tool.

Setup and configuration

For a local connection, configure an MCP client to run:

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

The Reoon MCP server does not require a Pipeworx account when used locally. Install or run @pipeworx/mcp-reoon with npx; it communicates over standard input and output.

You can instead use the hosted endpoint:

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

Create a Reoon API key in the Reoon Email Verifier API settings and pass it as _apiKey when calling the tool. The integration does not provide a vendor key or platform key.

Tools and capabilities

• reoon_verify(email, mode?, _apiKey): verifies one email address.
• Quick verification with syntax, MX, disposable, role-account, spamtrap, free-email, and status fields.
• Power verification with deliverability indicators, disabled and inbox-full states, an overall score, and catch-all detection.
• Hosted access through Pipeworx or standalone local stdio execution.
• Optional use of the gateway's ask_pipeworx routing tool when connected through Pipeworx.

Limitations and notes

The integration is unofficial and is not affiliated with, endorsed by, or published by Reoon. It verifies one address per tool call based on the documented single-email endpoint.

A valid Reoon API key is required for successful verification. Testing with an invalid key returned HTTP 401 and an “Invalid API key” response, confirming that authentication failures are reported cleanly.

The exact thresholds used for power-mode overall_score are not established in the available material. The relationship between a power-mode unknown status and a true catch-all result is also not verified. The hosted pack endpoint includes shared Pipeworx schemas in addition to the Reoon tool; the local package does not include those meta-tools.