Email Address Validator ($6/1000 verifications) avatar
Email Address Validator ($6/1000 verifications)

Under maintenance

Pricing

$6.00 / 1,000 emails

Go to Store
Email Address Validator ($6/1000 verifications)

Email Address Validator ($6/1000 verifications)

Under maintenance

Developed by

blg

blg

Maintained by Community

Fast & Accurate Email Address Validator. Only $6 for 1000 validations.

5.0 (4)

Pricing

$6.00 / 1,000 emails

1

Total users

6

Monthly users

6

Runs succeeded

81%

Last modified

2 days ago

You can access the Email Address Validator ($6/1000 verifications) programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/sse?actors=overpowered/verify-email",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Email Address Validator ($6/1000 verifications)

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-remote from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).

  • Set up the connection directly in your MCP client UI by providing the URL https://mcp.apify.com/sse?actors=overpowered/verify-email along with an API token (or use OAuth).

  • Connect to mcp.apify.com via Server-Sent Events (SSE), as shown below:

{
"mcpServers": {
"apify": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=overpowered/verify-email",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.