QuanticData MCP server
Servidor MCP de QuanticData: proporciona acceso web en vivo a Claude, Cursor y cualquier cliente MCP
Un servidor MCP de un solo archivo y cero dependencias que pone las API de datos de QuanticData al alcance de un agente de IA: extraer una página, ejecutar una búsqueda en Google/Bing/DuckDuckGo/Yandex, mapear o rastrear un sitio, auditar una URL para SEO y ejecutar cualquiera de los 31 Collectors listos para usar con una entrada semántica.
Sin SDK, sin paso de compilación, sin node_modules. Node.js 18+ y un solo archivo.
git clone https://github.com/quantumproxies/quanticdata-mcp-server
cd quanticdata-mcp-server
QUANTICDATA_API_KEY=qd_live_your_key_here node server.mjsObtén una clave en app.quanticdata.io: hay una cuota mensual gratuita y no se requiere tarjeta; consulta los precios en quanticdata.io para conocer la cifra actual.
Instálalo en tu cliente
Claude Code
claude mcp add quanticdata \
-e QUANTICDATA_API_KEY=qd_live_your_key_here \
-- node /absolute/path/to/quanticdata-mcp-server/server.mjsClaude Desktop — claude_desktop_config.json
{
"mcpServers": {
"quanticdata": {
"command": "node",
"args": ["/absolute/path/to/quanticdata-mcp-server/server.mjs"],
"env": { "QUANTICDATA_API_KEY": "qd_live_your_key_here" }
}
}
}Cursor — .cursor/mcp.json, con la misma forma que arriba.
Cualquier cliente que hable stdio MCP funciona: el servidor implementa initialize, tools/list, tools/call y ping, que es la superficie completa para un servidor solo de herramientas.
Related MCP server: Spider MCP Server
Herramientas
Herramienta | Lo que obtiene el agente | Precio |
| una URL → Markdown / HTML / texto, extracción CSS o IA, renderizado opcional | $0.0002 |
| resultados orgánicos + búsquedas relacionadas, 4 motores, 18 verticales | desde $0.0005 |
| cada URL de un sitio desde sitemaps + enlaces de la página de inicio, con totales | $0.0005 |
| rastreo BFS asíncrono → Markdown por página | $0.0003/página |
| vista sin JS vs. vista renderizada de una URL, con diferencias, más metadatos orientados a bots | $0.0012 |
| el catálogo: esquemas, ejemplos, estado, tu precio unitario | gratis |
| ejecutar un Collector con una entrada semántica | desde $0.0004/fila |
| una ejecución y sus filas entregadas | gratis |
Todo es de pago por éxito: una llamada que falla no cuesta nada.
Pruébalo sin un cliente
node smoke-test.mjs # handshake + tools/list, no API key neededO manéjalo manualmente: es JSON-RPC delimitado por líneas nuevas en stdin:
printf '%s\n' \
'{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"cli","version":"1"}}}' \
'{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \
| node server.mjsIndicaciones que funcionan bien
"Mapea quanticdata.io, luego extrae las cinco publicaciones de blog más recientes y resume los temas."
"Busca
serp api pricingen EE. UU. y Alemania y dime en qué se diferencian los diez primeros.""Ejecuta una auditoría SEO en nuestra página de precios: ¿es indexable sin JavaScript?"
"Usa
list_collectorsy luego extrae 40 clínicas dentales en Austin conlocal_business_leads."
La última es el patrón que vale la pena interiorizar: deja que el agente lea primero el catálogo y luego elija el recolector. Los esquemas se publican precisamente para que un modelo pueda elegir correctamente.
Configuración
Variable | Valor predeterminado | Notas |
| — | obligatoria; las claves tienen el formato |
|
| apúntalo a otro lugar para un proxy o un host de ensayo |
Los errores de la API vuelven como resultados de herramienta con isError: true en lugar de errores de protocolo, para que el modelo pueda leer el mensaje y corregirse a sí mismo en lugar de que la conversación muera.
Relacionado
Con licencia MIT.
Available Tools
9 toolscollector_run_statusAInspect
Fetch one Collector run and its delivered rows by run_id.
Inputs: runId (required).
crawlAInspect
Start an asynchronous BFS crawl from a seed URL; each page comes back as Markdown. Returns a job id immediately — poll with crawl_status. $0.0003 per page, unfetched budget refunded. Prefer map + batch when you can filter the URL list first.
Inputs: url (required), depth, limit, render, +4 more.
crawl_statusAInspect
Poll a crawl job: status, pagesCrawled, pagesQueued and the pages fetched so far.
Inputs: jobId (required).
list_collectorsAInspect
List the 31 ready-made Collectors: versioned scrapers you run with a semantic input (keyword + location, ASIN, domain, handle…) instead of URLs — web_search, keyword_ideas, amazon_search, amazon_product, ebay_search, aliexpress_search, google_maps_places, place_reviews, google_jobs, linkedin_jobs, indeed_jobs, google_news, google_shopping, product_offers, hotels, youtube_search, youtube_channel, reddit_posts, instagram_profile, tiktok_profile, tiktok_video, zillow_search, app_store_apps, google_play_apps, linkedin_profile, linkedin_company, company_profile, site_contacts, local_business_leads, search_images, search_videos. Each entry carries its input and output schema, examples, health and your price per delivered row. Free to call.
Inputs: no named parameters.
mapAInspect
Discover every URL of a site in one call: robots.txt sitemaps + /sitemap.xml (including nested indexes) + same-domain homepage links, de-duplicated. Returns the list plus a site-wide total and a per-section summary. Always cheaper than crawling to find out how big a site is. $0.0005.
Inputs: url (required), limit, search, country, +2 more.
run_collectorAInspect
Run one Collector with its semantic input. Short runs return the rows directly; long runs return a run_id to poll with collector_run_status. Billed per delivered row — zero rows costs zero.
Inputs: slug (required), input (required), async.
scrapeAInspect
Fetch one URL and return it as Markdown (default), HTML or plain text, through residential proxies with real-browser TLS fingerprints. Set render:true only when the content is genuinely absent from the raw HTML. Use extract for CSS-selector JSON, or ai_prompt to have the page turned into structured data by an LLM. $0.0002 per page; a failed fetch is free.
Inputs: url (required), mode, format, render, +5 more.
searchAInspect
Structured search results from Google, Bing, DuckDuckGo or Yandex: organic rows with position, title, link, snippet and sitelinks, plus related searches and any local/news/shopping blocks the page carried. Eighteen verticals via search_type. From $0.0005 per search.
Inputs: query (required), num, lang, page, +4 more.
seo_auditAInspect
Fetch a URL twice — as a no-JS bot and fully rendered — and return both views, the diff between them (contentOnlyInJs, canonicalMissingNoJs, titleChanged…) and the bot-facing meta (robots, OG, JSON-LD types). The fastest way to answer 'is this page indexable without JavaScript'. $0.0012.
Inputs: url (required), country, no_render.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct job: single fetch, search, site discovery, crawl, crawl status, SEO audit, and collector management. Minor ambiguity exists between the `search` tool and the `web_search` collector, and between `scrape` and `seo_audit`, but the descriptions provide enough context to choose correctly.
Bare imperative verbs (`scrape`, `search`, `map`, `crawl`) sit alongside verb-noun names (`run_collector`, `list_collectors`) and noun-phrase status names (`crawl_status`, `collector_run_status`, `seo_audit`). The names are readable, but the pattern is not consistent enough to predict how a new tool would be named.
Nine tools is a well-scoped size for a data-acquisition server covering scraping, search, crawling, SEO auditing, and collector workflows. Each tool earns its place without overwhelming an agent.
The server covers scraping, search, URL discovery, crawling with status polling, SEO auditing, and collector execution/status, forming complete data-fetch workflows. Minor gaps include a referenced batch mode that is not exposed as a tool and no cancellation/list-jobs capability, but these can be worked around.
Maintenance
Related MCP Connectors
Web scraping, search, crawling, structured extraction and research for AI agents.
Web data for agents. Extract web pages, crawl websites, discover URLs, and search the web.
Web data for agents: YouTube transcripts, screenshots, Google News, WHOIS, jobs, tech stack, more.
Direct access to 60+ scraping and search tools. Extract structured data from Google (Search, Maps, Trends), Amazon, Airbnb, Social Media, and any web page directly into your AI agent.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to access real-time web data through search, markdown scraping, and browser automation while bypassing anti-bot protections. It provides tools for web research, e-commerce monitoring, and data extraction from across the globe.45MIT
- AlicenseAqualityCmaintenanceEnables AI agents to crawl, scrape, search, and automate browsers with anti-bot bypass, providing fast web access via 22 tools.2259 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to perform web searches, extract webpage content, and conduct end-to-end search-and-extract operations using multiple search providers and content extraction methods.-
- AlicenseAqualityBmaintenanceEnables AI agents to perform web searches, fetch and extract page content, and crawl sites with caching, rate limiting, and robots.txt compliance, all without needing API keys.171,855 PyPI2MIT