Provides AI agents with live web access for scraping, searching, crawling, and managing residential proxies.
Also known as quantumproxies/quanticdata-mcp-server, quanticdata-mcp-server
- Stars
- 0
- Tools
- 12
- Downloads, 30 days
- —
- Latest version
- 0.11.5
- Last commit
- Oct 3, 2026
- License
- MIT
What is QuanticData MCP?
QuanticData provides AI agents with live web access for scraping, searching, crawling, and managing residential proxies. It exposes 12 tools, such as scrape, unlock, seo_audit.
Summary generated from the project's README
About QuanticData MCP server
Providing AI agents with live web access for scraping, searching, and crawling is what quanticdata-mcp enables for developers using Claude, Cursor, or other MCP clients. It allows agents to bypass bot detection by using residential proxies with real-browser TLS fingerprints. Users can run the server locally via npx or connect to a hosted remote endpoint using OAuth 2.1 or a bearer token.
The server includes a wide array of specialized tools such as scrape for extracting Markdown or HTML, search for structured results from Google and Bing, and ai_visibility to audit how LLMs like ChatGPT or Perplexity cite specific pages. It also manages proxy infrastructure, allowing users to list services, generate proxy strings with geo-targeting, and manage IP whitelisting. For large-scale tasks, the batch and crawl tools enable asynchronous processing of multiple URLs or entire sites.
To use the server, you must provide a qd_live_ API key. Developers working with local models like Ollama can use tool presets like lite, web, or research to manage the token footprint of the tool definitions.
What you can do with it
- 1Perform SEO and AI visibility auditsCheck if specific web pages are being read and cited by major AI engines like Claude or Google AI Overview.
- 2Extract structured data from websitesScrape a specific URL to retrieve content in Markdown, HTML, or text formats including PDF and Office documents.
- 3Automate large scale web crawlingRun an asynchronous breadth-first search crawl of a website to collect Markdown content from every page.
- 4Manage and generate proxy credentialsCreate ready-to-use proxy strings with specific geo-targeting for residential, mobile, or datacenter plans.
Written from the project's README. Every use case is checked against a quote from it.
How to install QuanticData MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall QuanticData MCP in Claude Code
$ claude mcp add --env 'QUANTICDATA_API_KEY=<YOUR_QUANTICDATA_API_KEY>' quanticdata-mcp-server -- npx -y quanticdata-mcpInstall QuanticData MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"quanticdata-mcp-server": {
"command": "npx",
"args": [
"-y",
"quanticdata-mcp"
],
"env": {
"QUANTICDATA_API_KEY": "<YOUR_QUANTICDATA_API_KEY>"
}
}
}
}Install QuanticData MCP in VS Code
.vscode/mcp.json
{
"servers": {
"quanticdata-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"quanticdata-mcp"
],
"env": {
"QUANTICDATA_API_KEY": "<YOUR_QUANTICDATA_API_KEY>"
}
}
}
}Install QuanticData MCP in VS Code CLI
$ code --add-mcp '{"name":"quanticdata-mcp-server","type":"stdio","command":"npx","args":["-y","quanticdata-mcp"],"env":{"QUANTICDATA_API_KEY":"<YOUR_QUANTICDATA_API_KEY>"}}'Install QuanticData MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"quanticdata-mcp-server": {
"command": "npx",
"args": [
"-y",
"quanticdata-mcp"
],
"env": {
"QUANTICDATA_API_KEY": "<YOUR_QUANTICDATA_API_KEY>"
}
}
}
}Install QuanticData MCP in Codex
$ codex mcp add quanticdata-mcp-server --env 'QUANTICDATA_API_KEY=<YOUR_QUANTICDATA_API_KEY>' --env 'QUANTICDATA_API_KEY=<YOUR_QUANTICDATA_API_KEY>' -- npx -y quanticdata-mcpInstall QuanticData MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.quanticdata-mcp-server] command = "npx" args = ["-y", "quanticdata-mcp"] [mcp_servers.quanticdata-mcp-server.env] QUANTICDATA_API_KEY = "<YOUR_QUANTICDATA_API_KEY>"
Install QuanticData MCP in Gemini CLI
$ gemini mcp add -s user -e 'QUANTICDATA_API_KEY=<YOUR_QUANTICDATA_API_KEY>' -e 'QUANTICDATA_API_KEY=<YOUR_QUANTICDATA_API_KEY>' quanticdata-mcp-server npx -- -y quanticdata-mcpInstall QuanticData MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"quanticdata-mcp-server": {
"command": "npx",
"args": [
"-y",
"quanticdata-mcp"
],
"env": {
"QUANTICDATA_API_KEY": "<YOUR_QUANTICDATA_API_KEY>"
}
}
}
}QuanticData MCP tools 12
Detected from the READMEscrapeunlockseo_auditai_visibilitysearchsearch_and_readmaplist_proxiesgenerate_proxiesproxy_locationswhitelist_ipreport
| scrape | — | |
| unlock | — | |
| seo_audit | — | |
| ai_visibility | — | |
| search | — | |
| search_and_read | — | |
| map | — | |
| list_proxies | — | |
| generate_proxies | — | |
| proxy_locations | — | |
| whitelist_ip | — | |
| report | — |
Configuration
QUANTICDATA_API_KEYRequiredSecretAPI key from https://app.quanticdata.io/api-keys — $2 of free API usage every month, no card required
QUANTICDATA_API_KEYRequiredSecretAPI key from https://app.quanticdata.io/api-keys — $2 of free API usage every month, no card required
| Name | Description | |
|---|---|---|
| QUANTICDATA_API_KEY | API key from https://app.quanticdata.io/api-keys — $2 of free API usage every month, no card required | RequiredSecret |
| QUANTICDATA_API_KEY | API key from https://app.quanticdata.io/api-keys — $2 of free API usage every month, no card required | RequiredSecret |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablequantumproxies/quanticdata-mcp-server is public and reachablegithub.com/quantumproxies/quanticdata-mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-03github.com/quantumproxies/quanticdata-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from quanticdata-mcpPass
- No critical advisory in the package or its dependencies103 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model12 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubQuanticData 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
| 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. |
unlock |
Web Unlocker: replay any HTTP request (method, headers, body) through a residential exit with a real browser TLS fingerprint, retry on a fresh IP, escalate a blocked GET to a real browser. Returns the raw response (status, headers, body); a still-blocked page comes back flagged (blocked, blockClass, vendor), never as a silent 200. Interactive captchas are not solved (blockClass: "captcha"). |
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). |
ai_visibility |
Can ChatGPT, Claude, Perplexity, Google AI Overview and Bing Copilot read and cite a page? On-page audit (24 AI crawlers in robots.txt, Content-Signal, a fetch as GPTBot, noindex/nosnippet/noai, text without JS, JSON-LD entities, answer-shaped copy, dates with age, author, sources) scored per pillar with blockers, evidence and fixes — plus an optional citation panel that asks the engines and reports cited / mentioned / rank, share of voice and who wins the questions you are absent from. |
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. |
report |
Send feedback to the team from inside the agent: a bug (wrong/empty result, error, blocked page), a missing feature or collector, a question. Works without an API key. |
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:
- The client opens the QuanticData.io sign-in page.
- You sign in (or create a free account) and click Allow access.
- The client is connected. A key named
MCP · <client>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
| Var | Default | Notes |
|---|---|---|
QUANTICDATA_API_KEY |
— | Required. Your qd_live_ key. |
QUANTICDATA_API_BASE |
https://api.quanticdata.io/v1 |
Override for staging/self-host. |
QUANTICDATA_TOOLS |
all 28 | Load only some tools: names (search,scrape) or a preset (lite, web, research, collectors, proxies). See below. |
Self-hosted remote endpoint only (quanticdata-mcp-remote), optional:
| Var | Default | Notes |
|---|---|---|
MCP_OAUTH_RESOURCE |
https://api.quanticdata.io/mcp |
This endpoint as an OAuth resource. |
MCP_OAUTH_ISSUER |
https://app.quanticdata.io |
Authorization server advertised in the resource metadata. |
MCP_OAUTH_INTROSPECT_URL |
http://127.0.0.1:3090/api/v1/internal/oauth/introspect |
Where OAuth access tokens are checked. |
MCP_INTERNAL_TOKEN |
— | Secret for the introspection call. Unset = only API keys are accepted. |
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:
| Preset | Tools | Definition tokens |
|---|---|---|
lite |
search_and_read | ~360 |
web |
search, search_and_read, scrape | ~4,200 |
research |
web + map, batch, batch_status | ~5,100 |
collectors |
list_collectors, run_collector, collector_run_status | ~830 |
proxies |
list_proxies, generate_proxies, proxy_locations, whitelist_ip | ~1,800 |
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. support@quanticdata.io
QuanticData MCP questions
How do I add QuanticData MCP to Claude Code?
Run claude mcp add --env 'QUANTICDATA_API_KEY=<YOUR_QUANTICDATA_API_KEY>' quanticdata-mcp-server -- npx -y quanticdata-mcp in your terminal. Add --scope user to make it available in every project.
How do I add QuanticData MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does QuanticData MCP provide?
It exposes 12 tools, including scrape, unlock, seo_audit, ai_visibility, search.
Does the server solve interactive captchas?
No, interactive captchas are not solved; if a page is blocked by a captcha, it will be flagged as such.
Is my data private when using the local server?
Yes, the server runs locally and only communicates with the public QuanticData API; it has no access to your filesystem, shell, or clipboard.