QuanticData MCP Server

Connect QuanticData 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

Quick start

No install needed — npx fetches quanticdata-mcp on demand (Node.js 18+).

Claude Code (one command):

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):

{
  "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:

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:

{
  "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:

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

Run from source (development)

npm install
npm run build

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

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

Env

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