Skip to main content
ClaudeWave
quantumproxies avatar
quantumproxies

quanticdata-mcp-server

Ver en GitHub

Single-file, zero-dependency MCP server giving Claude, Cursor and any MCP client live web access.

MCP ServersRegistry oficial0 estrellas0 forksTypeScriptMITActualizado today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/26/2026
Install in Claude Code / Claude Desktop
Method: NPX · quanticdata-mcp
Claude Code CLI
claude mcp add quanticdata -- npx -y quanticdata-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "quanticdata": {
      "command": "npx",
      "args": ["-y", "quanticdata-mcp"],
      "env": {
        "QUANTICDATA_API_KEY": "<quanticdata_api_key>"
      }
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Detected environment variables
QUANTICDATA_API_KEY
Casos de uso

Resumen de MCP Servers

# QuanticData MCP Server

Connect [QuanticData](https://quanticdata.io) to Claude, Cursor, and any
MCP client. Gives an AI agent live web access — scrape, search, map, and crawl —
through residential proxies with real-browser TLS fingerprints, so pages that
block ordinary bots come back clean. It also hands the agent raw proxy
endpoints of every type (residential, mobile, datacenter, ISP, IPv6) from your
active plans, ready to plug into any HTTP client.

It calls the **public** QuanticData Scraper API with your own `qd_live_` key,
so there are no internal secrets and you run it locally.

## Tools

| Tool | What it does |
|------|--------------|
| `scrape` | Scrape one URL → Markdown/HTML/text, including PDF/Office documents. Supports multi-format output, absolute link collection, JSON-LD metadata, structured CSS extraction, AI prompt/JSON-schema extraction, and `mode: summary`. |
| `seo_audit` | Fetch a URL as a no-JS bot **and** fully rendered, return both SEO views + the diff (JS-only content, changed title/description, missing canonical) and bot-facing meta (robots, OG, JSON-LD). |
| `search` | Structured Google/Bing/DuckDuckGo results. Set `render: true` for Google AI Overview, PAA, Knowledge Graph and other JS enrichments. |
| `search_and_read` | SERP → fetch top pages → numbered citation-ready sources and one token-bounded context string ready for an AI prompt. |
| `search_bulk` / `search_bulk_status` | Async multi-page pagination with merged organic results and page-one AI/zero-click enrichments. |
| `map` | Fast URL discovery (sitemaps + homepage links), no full crawl. Compact by default: up to `limit` URLs (100) plus site-wide `total` and per-section `summary`; `group_by: path` for the path tree. |
| `crawl` / `crawl_status` | Async BFS site crawl → Markdown per page; poll for progress. |
| `batch` / `batch_status` | Scrape many URLs asynchronously; `mode: summary` for metadata-only items. Incremental polling via `since` cursor; page content only with `include_content`. |
| `create_dataset` / `dataset_status` | Prompt-driven structured dataset collection with budget and row limits. |
| `list_collectors` / `run_collector` / `collector_run_status` | Ready-made Collectors: run a versioned scraper with a semantic input (keyword + location, place id, product id, domain…) instead of URLs — Google Maps places, place reviews, Google Jobs/News/Shopping, product offers, hotels, local business leads, site contacts, company profile. Priced per delivered row; async runs poll by `run_id`, rows exportable as CSV. |
| `list_proxies` | List your proxy services of every type — Residential Basic/Premium/Private, Mobile, Mobile V2, Datacenter, ISP, IPv6 — with bandwidth left, expiry and the `orderId` used to generate. |
| `generate_proxies` | Ready-to-use proxy strings (credentials included) from any active plan: geo targeting (country/state/city/ISP/ASN), rotating or sticky sessions, HTTP or SOCKS5, several output formats. |
| `proxy_locations` | Valid geo-targeting values per plan type: countries, states, cities, ASNs, or the full location tree with ISP codes. |
| `whitelist_ip` | Manage IP-auth whitelisting (add/list/remove) for plans that support it, including the Mobile V2 IP-auth proxy list. |

## Quick start

No install needed — `npx` fetches [quanticdata-mcp](https://www.npmjs.com/package/quanticdata-mcp) on demand (Node.js 18+).

**Claude Code** (one command):

```bash
claude mcp add quanticdata \
  -e QUANTICDATA_API_KEY=qd_live_your_key_here \
  -- npx -y quanticdata-mcp
```

**Claude Desktop / Cursor / any MCP client** (`claude_desktop_config.json`, `.cursor/mcp.json`, or `.mcp.json`):

```json
{
  "mcpServers": {
    "quanticdata": {
      "command": "npx",
      "args": ["-y", "quanticdata-mcp"],
      "env": { "QUANTICDATA_API_KEY": "qd_live_your_key_here" }
    }
  }
}
```

## Hosted endpoint (remote MCP)

The same server also runs as a hosted **Streamable HTTP** endpoint, for clients
that prefer a URL over a local package:

```
https://api.quanticdata.io/mcp
```

Your key travels per request in the `Authorization` header, so nothing is
stored server-side and one endpoint serves every account:

```bash
curl -X POST https://api.quanticdata.io/mcp \
  -H "Authorization: Bearer qd_live_your_key_here" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

In a client that supports remote MCP servers, add it as an HTTP server with
that URL and a bearer token. `initialize` and `tools/list` answer without a
key so directories and inspectors can introspect the server; tool calls need
one.

Self-hosting the endpoint is a second binary in this same package:

```bash
QUANTICDATA_API_KEY=qd_live_… PORT=9310 npx -y quanticdata-mcp-remote
```

## Run from source (development)

```bash
npm install
npm run build
```

Then point the client at the local build instead of npx:

```json
{
  "mcpServers": {
    "quanticdata": {
      "command": "node",
      "args": ["/absolute/path/to/scraper-mcp/dist/index.js"],
      "env": {
        "QUANTICDATA_API_KEY": "qd_live_your_key_here"
      }
    }
  }
}
```

## Env

| Var | Default | Notes |
|-----|---------|-------|
| `QUANTICDATA_API_KEY` | — | **Required.** Your `qd_live_` key. |
| `QUANTICDATA_API_BASE` | `https://api.quanticdata.io/v1` | Override for staging/self-host. |

## Example prompts

- "Scrape the pricing page at example.com and give me the plans and prices."
- "Search Google Shopping for 'nintendo switch oled' in the US and list the cheapest 5."
- "Map docs.example.com, then crawl only the /guides/ pages and summarize them."
- "List my proxy plans and generate 5 sticky US residential proxies as socks5 URLs."
- "Get me a rotating mobile proxy in Germany and whitelist my server IP 203.0.113.7."
ai-agentsclaudecursormcpmodel-context-protocolnodejsweb-scraping

Lo que la gente pregunta sobre quanticdata-mcp-server

¿Qué es quantumproxies/quanticdata-mcp-server?

+

quantumproxies/quanticdata-mcp-server es mcp servers para el ecosistema de Claude AI. Single-file, zero-dependency MCP server giving Claude, Cursor and any MCP client live web access. Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-08-25.

¿Cómo se instala quanticdata-mcp-server?

+

Puedes instalar quanticdata-mcp-server clonando el repositorio (https://github.com/quantumproxies/quanticdata-mcp-server) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar quantumproxies/quanticdata-mcp-server?

+

Nuestro agente de seguridad ha analizado quantumproxies/quanticdata-mcp-server y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene quantumproxies/quanticdata-mcp-server?

+

quantumproxies/quanticdata-mcp-server es mantenido por quantumproxies. La última actividad registrada en GitHub es del 2026-08-25, con 0 issues abiertos.

¿Hay alternativas a quanticdata-mcp-server?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega quanticdata-mcp-server en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: quantumproxies/quanticdata-mcp-server
[![Featured on ClaudeWave](https://claudewave.com/api/badge/quantumproxies-quanticdata-mcp-server)](https://claudewave.com/repo/quantumproxies-quanticdata-mcp-server)
<a href="https://claudewave.com/repo/quantumproxies-quanticdata-mcp-server"><img src="https://claudewave.com/api/badge/quantumproxies-quanticdata-mcp-server" alt="Featured on ClaudeWave: quantumproxies/quanticdata-mcp-server" width="320" height="64" /></a>

Más MCP Servers

Alternativas a quanticdata-mcp-server