QuanticData MCP Server is a single-file, zero-dependency MCP (Model Context Protocol) server that provides real-time web access capabilities for Claude, Cursor, and any MCP-compatible client. Through residential proxies and real browser TLS fingerprints, it allows pages that would otherwise block ordinary bots to be returned cleanly.
Main capabilities include: web scraping and conversion to Markdown, SERP search, sitemap generation and crawling, and generating ready-made scrapers and datasets from natural language prompts. In addition, it can obtain various raw proxy endpoints (residential, mobile, datacenter, ISP, IPv6) from the user's active plan, which can be plugged directly into any HTTP client.
Usage: The server calls the public QuanticData Scraper API, using the user's own qd_live_ key, contains no internal secrets, and runs entirely locally. No installation is required; npx will fetch quanticdata-mcp on demand (requires Node.js 18+). It supports multiple access methods: a one-command setup for Claude Code; Claude Desktop / Cursor / other MCP clients via configuration files (claude_desktop_config.json, .cursor/mcp.json, or .mcp.json); hosted endpoints (remote MCP) running as Streamable HTTP, suitable for clients that prefer a URL over a local package; OAuth 2.1 authorization is supported (no need to copy keys), and directly sending a Bearer token or X-Api-Key header is also supported. The self-hosted endpoint, as a second binary in the same package, can serve that account for callers that do not send credentials once QUANTICDATA_API_KEY is set. It can also be run from source for development.
For local models (Ollama, LM Studio, Qwen, Open WebUI), the 28 tool definitions are about 14,000 tokens, which may exceed the default 4K context. Fewer tools can be loaded via QUANTICDATA_TOOLS=web or the URL parameter ?tools=web, and names can be combined such as ?tools=lite,collectors.
Example prompts include: scrape the example.com pricing page and list the plans and prices; search "nintendo switch oled" on Google Shopping in the United States and list the 5 cheapest; map docs.example.com and then crawl only the /guides/ pages and summarize; list proxy plans and generate 5 socks5 URLs for sticky US residential proxies; obtain German rotating mobile proxies and whitelist the server IP 203.0.113.7.
Privacy and data: The server runs on the user's machine and communicates only with https://api.quanticdata.io/v1 , authenticating with the user's own qd_live_ key. Each call carries only the parameters passed in by the user or the agent (target URL or query, extraction prompt), does not read or transmit anything else on the machine, and has no filesystem, shell, or clipboard access. QuanticData collects account data (name, email, billing information) as well as request logs used for billing, abuse prevention, and support (target URL or query, timestamp, response status, bytes transferred, API key used), and does not retain scraped page content beyond what is needed to return results. Public web data collected by the user through the service is controlled by the user as the controller, who must use it lawfully and comply with the terms of the websites accessed. Personal data is not sold, and only the minimum necessary data is shared with processors running the service (payment, email, hosting, CDN, analytics) and upstream proxy networks. Account data is retained for the life of the account, request logs are retained on a rolling window, and deletion can be requested at any time. Keys are stored by Claude Desktop in the operating system keychain, passed to the server as environment variables, are not written into the package, and are not sent anywhere other than the QuanticData API. They can be revoked or rotated at https://app.quanticdata.io/api-keys .
Limitations: Requires Node.js 18+; requires a QuanticData account and API key (or authorization via OAuth); local models need to be mindful of context length limits; use is subject to the QuanticData privacy policy (https://quanticdata.io/privacy）。
