# quanticdata-mcp

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/quantumproxies/quanticdata-mcp-server  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/quanticdata-mcp

## Description
Web data for AI agents: scraping, SERP, crawl/map, 74 Collectors, datasets and proxies. 25 tools.

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

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

## Documentation & README

# QuanticData MCP Server

Connect [QuanticData](https://quanticdata.io) to Claude, Cursor, Cline, 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 / Cline / any MCP client** (`claude_desktop_config.json`, `.cursor/mcp.json`, Cline's MCP settings, 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"}'
```

The endpoint accepts either header — `Authorization: Bearer qd_live_your_key_here`
(preferred) or `X-Api-Key: qd_live_your_key_here` — so clients that can't set an
`Authorization` header can send the key directly.

In a client that supports remote MCP servers, add it as an HTTP server with that
URL and your key. For **Cline** (and any client that defaults to legacy SSE),
set the transport type explicitly to `streamableHttp`:

```json
{
  "mcpServers": {
    "quanticdata": {
      "type": "streamableHttp",
      "url": "https://api.quanticdata.io/mcp",
      "headers": { "Authorization": "Bearer qd_live_your_key_here" }
    }
  }
}
```

`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/quanticdata-mcp-server/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."

## Privacy Policy

Full policy: <https://quanticdata.io/privacy>

**What this server sends.** It runs on your machine and talks only to the public
QuanticData API at `https://api.quanticdata.io/v1`, authenticated with
your own `qd_live_` key. Each call carries the arguments you (or your agent)
passed — the target URL or query, and any extraction prompt. Nothing else on your
machine is read or transmitted: the server has no filesystem, shell or clipboard
access.

**What we collect.** Account data you give us (name, email, billing details) and
a request log kept for billing, abuse prevention and support: target URL or
query, timestamp, response status, bytes transferred and the API key used. We do
**not** retain scraped page content beyond what is needed to return your result.

**Data you collect through the service.** You decide what public web data to
collect and **you are the controller of that data** — we process it on your
behalf only to fulfil your request. You are responsible for using the service
lawfully, for respecting the terms of the sites you access, and for any personal
data you collect through it.

**Sharing.** We do not sell personal data. We share it only with the processors
that run the service — payment providers, email delivery, hosting, CDN and
analytics — under contracts that bind them to protect it, and with the upstream
proxy networks that route your traffic (connection metadata only, never your
account details). We may disclose data where required by law.

**Retention.** Account data for as long as the account exists; request logs on a
rolling window for billing and abuse investigation. You can request deletion at
any time.

**Your key.** Claude Desktop stores it in the OS keychain and passes it to this
server as an environment variable. It is never written to the bundle and never
sent anywhere except the QuanticData API. Revoke or rotate it at
<https://app.quanticdata.io/api-keys>.

**Contact.** <support@quanticdata.io>