Quanticdata MCP

QuanticData MCP Server

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

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 / any MCP client (claude_desktop_config.json, .cursor/mcp.json, 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

Connect with OAuth (no key to copy)

The endpoint supports the MCP authorization spec (OAuth 2.1). In a client that supports it, add the URL above as a remote server and nothing else:

1. The client opens the QuanticData.io sign-in page.
2. You sign in (or create a free account) and click Allow access.
3. The client is connected. A key named MCP · appears on the dashboard API keys page; delete it to disconnect the client.

Under the hood: authorization server metadata at https://app.quanticdata.io/.well-known/oauth-authorization-server, protected resource metadata at https://api.quanticdata.io/.well-known/oauth-protected-resource/mcp, dynamic client registration (RFC 7591) and Client ID Metadata Documents, PKCE (S256) required, 1-hour access tokens with rotating refresh tokens, tokens bound to this endpoint (RFC 8707). Usage is billed to your balance like any key.

Or send your API key

Clients that take a bearer token can skip OAuth: the key travels per request in the Authorization header (or X-Api-Key), nothing is stored server-side.

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"}'

A request with neither a token nor a key gets 401 with a WWW-Authenticate header pointing at the metadata above: that is what makes OAuth-capable clients start the sign-in.

Self-hosting the endpoint is a second binary in this same package. With QUANTICDATA_API_KEY set it serves that one account to callers that send no credential:

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/scraper-mcp/dist/index.js"], "env": { "QUANTICDATA_API_KEY": "qd_live_your_key_here" } } } }

Env

Self-hosted remote endpoint only (quanticdata-mcp-remote), optional:

Local models (Ollama, LM Studio, Qwen, Open WebUI)

The 28 tool definitions are about 14,000 tokens. A local model on Ollama's default 4K context cannot hold them, and a 32K context loses almost half its room before the first page. Load fewer tools:

Over stdio set QUANTICDATA_TOOLS=web. On the hosted endpoint add ?tools=web to the URL and send your API key as a Bearer header: https://api.quanticdata.io/mcp?tools=web. Names can be combined: ?tools=lite,collectors.

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.