Dataify MCP
dataify-server/mcp
Desbloqueio web, SERP e scraping integrados ao MCP
Ver no GitHubServidor MCP que expõe ferramentas de desbloqueio web, SERP e construtor de scrapers da plataforma Dataify. Suporta endpoints MCP hospedados, uso local via npx e seleção de ferramentas por variáveis de ambiente, integrando-se nativamente com clientes MCP como Claude.
Instalação
npx convez-ai dataify-server/mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Extrair dados de múltiplos mecanismos de busca (Google, Bing, DuckDuckGo, Yandex)
- Desbloquear e fazer scraping de sites com proteção anti-bot
- Coletar dados estruturados de plataformas (Amazon, YouTube, LinkedIn, Airbnb, etc)
- Construir pipelines de extração de dados sem código adicional
Veredito

Solução robusta e bem-integrada ao ecossistema MCP para scraping e busca de dados em larga escala. Flexível entre uso hospedado e local, mas requer token Dataify e tem limitações em modo local para ferramentas dependentes de backends internos.
README
A tradução para o português deste README ainda está na fila.
Dataify MCP
Dataify MCP exposes Dataify web unlocker, SERP, and scraper builder tools to MCP clients. The package supports Dataify hosted MCP endpoints, local npx stdio usage, and environment-based tool selection.
Quick Start
Use Dataify hosted MCP when your client supports remote streamable HTTP:
https://mcp.dataify.com/mcp?token=YOUR_DATAIFY_TOKEN&tools=user_info,web_unlocker,google_serp,yandex_serp,duckduckgo_serp,bing_serp,amazon,youtube,facebook,instagram,reddit,walmart,google,booking,indeed,airbnb,google_play_store,github,tiktok,linkedin,glassdoor,twitter,crunchbase,zillow,ebay
If your client needs SSE, use the matching SSE endpoint:
https://mcp.dataify.com/sse?token=YOUR_DATAIFY_TOKEN&tools=user_info,web_unlocker,google_serp,yandex_serp,duckduckgo_serp,bing_serp,amazon,youtube,facebook,instagram,reddit,walmart,google,booking,indeed,airbnb,google_play_store,github,tiktok,linkedin,glassdoor,twitter,crunchbase,zillow,ebay
Use the local npm package when your MCP client starts tools through stdio:
{
"mcpServers": {
"dataify": {
"command": "npx",
"args": ["@dataify/dataify-mcp"],
"env": {
"DATAIFY_API_TOKEN": "YOUR_DATAIFY_TOKEN",
"GROUPS": "web_unlocker,google_serp,bing_serp,youtube"
}
}
}
}
Local Setup
npm install
npm run start
npm run start starts a stdio MCP server and waits for an MCP client. It is expected to keep running.
Tool Selection
The local package supports environment-based tool selection:
GROUPS: comma-separated Dataify tool groups.TOOLS: comma-separated individual tool names.DATAIFY_TOOLS: backward-compatible alias forTOOLS.
If no selection is provided, all local tools are registered.
Supported groups:
user_info, web_unlocker, google_serp, yandex_serp, duckduckgo_serp, bing_serp,
amazon, youtube, facebook, instagram, reddit, walmart, google, booking,
indeed, airbnb, google_play_store, github, tiktok, linkedin, glassdoor,
twitter, crunchbase, zillow, ebay
Examples:
GROUPS=web_unlocker,google_serp npm run start
GROUPS=youtube TOOLS=google_search npm run start
Environment
DATAIFY_API_TOKEN: Dataify API token used by the local stdio package.DATAIFY_WEB_UNLOCKER_URL: defaults tohttps://webunlocker.dataify.com.DATAIFY_SERP_API_URL: defaults tohttps://scraperapi.dataify.com.DATAIFY_SCRAPER_API_URL: defaults tohttps://scraperapi.dataify.com.DATAIFY_TIMEOUT_MS: defaults to120000.GROUPS: optional comma-separated tool groups.TOOLS: optional comma-separated individual tool names.DATAIFY_TOOLS: optional compatibility alias forTOOLS.
Hosted vs Local
https://mcp.dataify.com/mcp and https://mcp.dataify.com/sse are the full hosted Dataify MCP services. They are backed by the Go dataify_mcp_api service and can expose internal tools such as user information, balance, task status, statistics, and tool permissions.
This npm package is a local stdio MCP package. It calls public Dataify APIs directly. Tool names that depend on internal MySQL, ClickHouse, or Redis stores are kept visible for compatibility, but return a clear unsupported message locally.
@modelcontextprotocol/sdk is pinned to 1.10.2 because fastmcp@1.27.7 is not compatible with newer SDK completion capability checks.