Email Address Validator avatar
Email Address Validator

Pricing

$15.00/month + usage

Go to Store
Email Address Validator

Email Address Validator

Developed by

Web Harvester

Web Harvester

Maintained by Community

A powerful tool for validating and assessing the quality of email addresses. This Actor provides comprehensive information about email deliverability, format validity, and classification.

5.0 (1)

Pricing

$15.00/month + usage

3

Total users

155

Monthly users

125

Runs succeeded

91%

Last modified

3 months ago

You can access the Email Address Validator 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=web.harvester/email-address-validator",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Email Address Validator

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=web.harvester/email-address-validator 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=web.harvester/email-address-validator",
"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.