Skip to content
Reoon Email Verifier logo

Reoon Email Verifier MCP server

Email validation service that cleans invalid, temporary & unsafe email addresses.

Reoon Email Verifier is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
3
Works with
Any MCP client
Auth
API key
License
MIT, open source
Updated
August 2026

About the Reoon Email Verifier MCP server

Connect Reoon Email Verifier once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Reoon Email Verifier and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Reoon Email Verifier tools your AI can run

Once connected, your assistant can call any of these Reoon Email Verifier actions by asking in plain language.

  • Verify Email

    Verify a single email

    2 fields

  • Create Bulk Email Verification

    Creates bulk email verification task.

    2 fields

  • Get Bulk Verification Result

    Retrieves result of bulk verification email by task ID.

    1 field

Give your assistant Reoon Email Verifier

Connect Reoon Email Verifier once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Reoon Email Verifier MCP, answered.

No. That is the point of it. One Activepieces server exposes Reoon Email Verifier alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Reoon Email Verifier in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 3 tools, including Verify Email, Create Bulk Email Verification, Get Bulk Verification Result, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.