
Advanced Website Email, Phone and Social Media Scraper
Pricing
$10.00/month + usage

Advanced Website Email, Phone and Social Media Scraper
This advanced contact scraper is an ALL-IN-ONE scraper that navigates pages likely to contain contact data, extracting emails, phone numbers, and social media links, with precision and speed. This scraper can bypass cloudflare and captchas. Very good scraper for lead generation.
2.0 (1)
Pricing
$10.00/month + usage
8
Total users
278
Monthly users
50
Runs succeeded
>99%
Last modified
7 months ago
You can access the Advanced Website Email, Phone and Social Media Scraper 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=perfectscrape/actor", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Advanced All In One Email, Phone and Social Media Scraper
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-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=perfectscrape/actor
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=perfectscrape/actor", "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.