Four proxy tools in one MCP server · Residential from $0.80/GB
MCP server for proxies: your AI agent generates residential, mobile, ISP and datacenter proxies
A proxy MCP server gives an AI agent tools to get proxies on its own. QuanticData's MCP server has four: list_proxies reads your plans, proxy_locations the valid countries, states, cities and ISPs, generate_proxies returns ready-to-use proxy strings with credentials, whitelist_ip manages IP sign-in. Generating costs nothing: the plan's traffic pays.
OAuth sign-in or API key · Generating proxies is free · HTTP or SOCKS5
list_proxies
Every proxy plan on the account, any type, with traffic left, expiry, whitelisted IPs and the orderId to generate from.
proxy_locations
Valid targeting values for a plan type: countries, states, cities, ASNs, or the full tree down to ISP codes.
generate_proxies
Ready-to-use proxy strings: country, state, city, ISP or ASN, rotating or sticky up to 1,440 minutes, HTTP or SOCKS5.
whitelist_ip
Add, list or remove a whitelisted IP, so a machine uses the proxies with no username or password.
- $0.80/GB
- Residential proxies, lowest published price
- $2.30/GB
- Mobile proxies, lowest published price, on 500 GB
- $2.50/IP
- ISP proxies, lowest published price
- $0.50/GB
- Datacenter proxies, lowest published price
By Aldo Morese, founder of QuanticData · Published · The calls shown were run on 18 November 2026
Definition
What a proxy MCP server is, and what it is not
A proxy MCP server is a Model Context Protocol server whose tools hand out proxies. The agent reads the tool schemas, picks the plan, the country and the session type, and gets back proxy strings it can pass straight to an HTTP client, a headless browser or a scraper. No dashboard, no copy and paste: the agent does it inside the conversation.
Search engines use the same words for something else. An "MCP proxy" or "MCP gateway" is software that sits between an MCP client and other MCP servers and forwards their traffic. That is not this page. This page is about proxies in the networking sense: residential, mobile, ISP and datacenter IP addresses that an agent requests through MCP.
The proxy tools live in the same server as search, scrape, crawl and the other web-data tools: one connection, twenty-nine tools, described on the MCP server page.
Tools
The four proxy tools, with their real parameters
Names and parameters as the server's tools/list returns them on 18 November 2026. The agent normally calls them in this order: plans first, then locations, then the strings.
| Tool | What it does | Parameters | Returns |
|---|---|---|---|
list_proxies | Lists the account's proxy services of every type: Residential Basic, Premium and Private, Mobile, Mobile V2, Datacenter (static or traffic-based), ISP, IPv6. | active, planType, limit, offset | Plan type, traffic left, expiry, whitelisted IPs, the orderId. Passwords are not listed. |
proxy_locations | Valid geo-targeting values for one plan type, before generating. | planType (required), level: countries, states, cities, asns or tree; country, state | Names and codes, or the location tree with ISP codes. |
generate_proxies | Builds ready-to-use proxy strings, credentials included, from one active plan. | orderId (required), country, state, city, isp, asn, rotation: rotating, sticky or static (IPv6), sessionTime 1 to 1,440 minutes, protocol: http or socks5, format, quantity up to 10,000, filter, gateway, ip, strict | The strings, the host and port, the targeting applied, traffic left. |
whitelist_ip | IP sign-in on Residential Basic, Datacenter, ISP, IPv6 and Mobile plans. | action: add, list or remove; orderId, ip; for Mobile also ports_count, protocol, country, region, city, isp, sticky, ttl | The whitelist entries of the plan. |
Parameters a plan type does not support are ignored. Residential Premium and Private sign in with username and password and do not need a whitelist.
Proof
A real call and its real response
The same session as the animation at the top, run on 18 November 2026 against a Mobile plan of our own account. Only the username, the password and the order id are replaced.
1. The agent reads the plans
tool call · list_proxies { "active": true } → excerpt of the answer
{
"proxies": [
{
"orderId": "YOUR_ORDER_ID",
"planType": "mobile_v2",
"planTypeName": "Mobile Proxies",
"bandwidthGB": 5,
"bandwidthLeftGB": 4.940959,
"isActive": true,
"daysRemaining": 41,
"whitelistedIPs": [],
"password": "hidden: call generate_proxies with this orderId for ready-to-use credentials"
}
],
"pagination": { "total": 10, "limit": 10, "offset": 0, "hasMore": false }
}2. It checks a location code (here: US states on Residential Basic)
tool call · proxy_locations { "planType": "residentialbasic", "level": "states", "country": "us" }
{
"states": [
{ "name": "Alabama", "code": "alabama", "country": "US" },
{ "name": "California", "code": "california", "country": "US" },
{ "name": "New York", "code": "newyork", "country": "US" },
…
],
"country": "US",
"planType": "residentialbasic"
}3. It generates the proxies
tool call · generate_proxies
{
"orderId": "YOUR_ORDER_ID",
"country": "us",
"rotation": "sticky",
"sessionTime": 10,
"quantity": 2,
"format": "http://user:pass@host:port"
}answer
{
"orderId": "YOUR_ORDER_ID",
"quantity": 2,
"protocol": "http",
"format": "http://user:pass@host:port",
"rotation": "sticky",
"sessionTime": 10,
"superSticky": false,
"udp": false,
"geoTargeting": { "country": "us", "state": null, "city": null },
"bandwidth": 5,
"bandwidthLeft": 4.940959,
"port": "8080",
"gateway": "ww",
"whitelist": [],
"host": "mobile.quanticdata.io",
"proxies": [
"http://USERNAME-country-us-type-mobile-sid-xc5dqvj86n-ttl-10m:[email protected]:8080",
"http://USERNAME-country-us-type-mobile-sid-k02y3xzc7b-ttl-10m:[email protected]:8080"
]
}The username of each string carries its targeting and its session (country-us, sid-…, ttl-10m): to change country or session the agent generates new strings rather than editing them. Each string then works in any client, for example curl -x "http://USERNAME-…:[email protected]:8080" https://example.com.
Setup
Connect the agent: OAuth sign-in or an API key
The hosted server is https://api.quanticdata.io/mcp (Streamable HTTP). A client with MCP authorization, such as a Claude custom connector, adds the URL and the person signs in with OAuth 2.1: no key is copied. Config files, scripts and CI use an API key (qd_live_…) in the Authorization: Bearer or X-Api-Key header, or the local package.
Claude Code, local package
claude mcp add quanticdata \
-e QUANTICDATA_API_KEY=qd_live_your_key_here \
-- npx -y quanticdata-mcpAny client, hosted endpoint
{
"mcpServers": {
"quanticdata": {
"type": "http",
"url": "https://api.quanticdata.io/mcp",
"headers": { "Authorization": "Bearer qd_live_your_key_here" }
}
}
}Leave headers out and the endpoint answers 401, so a client with MCP authorization opens the sign-in. Tokens, scopes and disconnecting a client: OAuth on the MCP server page. An agent with no account yet can register itself with the person's verified email: agent self-registration.
Payment
How the agent pays for proxies
Generating strings is free. What costs money is the plan: proxies are sold by traffic (residential, mobile, datacenter) or by IP (ISP), and the traffic is counted when the proxies are used. The plan is bought in one of two ways.
The person buys
On the dashboard, by card, PayPal or crypto. An assistant can prepare the package first: the buying guide for AI agents asks a few questions and hands the person one link with the live price.
The agent buys from the balance
Over REST with its key: a UCP checkout session for one plan from GET /v1/public/plans, completed with the account balance at 0% VAT, or POST /v1/public/purchase. If the balance is short the session returns a continue_url for the person. Step by step: let an agent buy proxies.
The balance itself can be topped up by the agent, within the cap the person set: when a call answers 402 INSUFFICIENT_FUNDS, the answer carries an x402 offer (USDC on Base) and a Stripe MPP challenge (a one-time Shared Payment Token). Limits and code: x402 and Stripe MPP for agents. The agent never needs a card number or a password.
Choose
Which proxy type the agent should generate
| Type | Published price | Typical agent task | planType |
|---|---|---|---|
| Residential | from $0.80/GB | Scraping public pages, prices and listings from home IPs, by country, state, city or ISP | residentialbasic, residentialpremium |
| Mobile | from $2.30/GB on 500 GB | Social platforms and mobile-first sites, sticky sessions by carrier | mobile_v2 |
| ISP | from $2.50/IP | One fixed IP that stays the same for logins and accounts | isp |
| Datacenter | from $0.50/GB | Bulk traffic to targets that accept datacenter IPs | datacenter, datacentertraffic |
Prices as published on each product page on 18 November 2026; the dashboard and GET /v1/scraper/billing show the live list. A longer comparison by what an agent needs: proxies for AI agents.
Would the agent rather not handle proxies at all? The scrape, search and unlock tools of the same server fetch through the proxy network and return Markdown or JSON, billed per successful call. Search results as JSON: Google AI Overview API and the SERP API.
FAQ
What is a proxy MCP server?
A Model Context Protocol server whose tools give an AI agent proxies: it lists the plans, finds valid locations and returns ready-to-use proxy strings with credentials. QuanticData's MCP server does this with four tools: list_proxies, proxy_locations, generate_proxies and whitelist_ip.
Is it the same thing as an MCP proxy or MCP gateway?
No. An MCP proxy or gateway forwards traffic between MCP clients and other MCP servers. A proxy MCP server, as on this page, hands the agent residential, mobile, ISP or datacenter IP addresses to route its own web requests through.
Does generating proxies through MCP cost anything?
No. generate_proxies is free and is not billed as a Data API call. The plan pays: its traffic is counted when the proxies are used, or the IPs on an ISP plan.
Can an AI agent buy the proxy plan by itself?
Yes, when the account balance covers it: over REST, a UCP checkout session for one plan completed with the balance, or POST /v1/public/purchase. When the balance is short, the session returns a link where the person pays. The agent never asks for a card number.
Can the agent choose the country, city or carrier?
Yes. proxy_locations returns the valid countries, states, cities, ASNs and ISP codes for a plan type, and generate_proxies takes them as country, state, city, asn and isp. What each plan supports is in the tool description; unsupported values are ignored.
Rotating or sticky proxies from MCP?
Both. rotation rotating gives a new IP on every request, sticky keeps one IP for sessionTime minutes, from 1 to 1,440, and static is a fixed session on IPv6. protocol picks HTTP or SOCKS5.
Which MCP clients can use the proxy tools?
Any MCP client: Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, Cline and others, through the local npx package or the hosted endpoint https://api.quanticdata.io/mcp with OAuth 2.1 or an API key.
Let your agent generate its own proxies
$2 of free API usage every month, no card. Add the MCP server, buy a plan, and the agent does the rest.
Get my free API key