Route web requests through 175M+ residential IPs across 195+ countries directly from MCP-compatible clients (Claude Desktop, Cursor, Zed, etc.).
proxy_fetch: Fetch any URL through residential proxies with geo-targeting by country, city, or ISP (ASN), sticky session support, and configurable timeouts. Bypasses anti-bot measures like Cloudflare, DataDome, and PerimeterX using real residential IPs.
proxy_check_ip: Verify your current exit IP address and geo-location through the proxy.
proxy_list_countries: Browse all 195+ countries available for routing, including 2-letter country codes.
proxy_rotate: Force an immediate IP rotation to a new residential IP, optionally within a specific country — useful when rate-limited or blocked.
Sticky sessions let you maintain the same IP across multiple requests using session IDs. Setup requires only a single API key environment variable, and a free tier includes 0.5 GB bandwidth with access to all countries — no credit card required.
Supports running the MCP server via Docker.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ProxyClaw MCP Server Check what Amazon shows from a US IP"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Model Context Protocol (MCP) server for ProxyClaw by IPLoop.
Route web requests through 175M+ residential IPs across 195+ countries — directly from Claude Desktop, Cursor, Zed, or any MCP-compatible client.
The only residential proxy network with an MCP server. Your AI can now browse from real homes, not datacenters.
195+ countries — Route requests through real residential IPs
Anti-bot bypass — Cloudflare, DataDome, PerimeterX can't tell the difference
Zero config — One environment variable, four powerful tools
Sticky sessions — Same IP across multiple requests
City & ISP targeting — Pinpoint precision when you need it
Related MCP server: Novada Proxy
We ship two MCP servers. Choose based on what you need:
This repo (Node.js) | ||
What it does | Proxy routing + fetch | Full anti-bot + headless render + structured extraction |
Best for | Simple fetches, geo-targeting | Scraping protected sites (Amazon, eBay, LinkedIn), JS-rendered pages |
Anti-detection | Chrome fingerprint headers | TLS JA3 spoofing + Playwright anti-detection |
Install |
|
|
Tools | 4 (fetch, check_ip, list_countries, rotate) | 6 (+ stealth fetch, render, scrape, extract) |
→ Use Node.js if you just need to route requests through residential IPs.
→ Use Python if you're scraping hard targets (Cloudflare, SPAs, React sites) or need structured data extraction from 60+ supported sites.
Both use the same proxy network — just different levels of power.
Sign up at iploop.io/signup — 0.5 GB free, no credit card.
Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"proxyclaw": {
"command": "npx",
"args": ["-y", "proxyclaw-mcp-server"],
"env": {
"IPLOOP_API_KEY": "your_api_key_here"
}
}
}
}Restart Claude Desktop. Done.
Ask Claude:
"Check my exit IP through the proxy"
Claude will call proxy_check_ip and show you the residential IP you're routing through.
proxy_fetchFetch any URL through a residential proxy.
{
"url": "https://example.com",
"country": "US",
"city": "newyork",
"session": "my-session-id",
"timeout": 30
}Use when: Scraping geo-restricted sites, checking prices by region, bypassing bot detection.
proxy_check_ipCheck which IP and country you're exiting from.
{
"country": "DE"
}Use when: Verifying your proxy location before scraping.
proxy_list_countriesList all 195+ available countries.
{}Use when: You need to know the exact 2-letter code for Madagascar.
proxy_rotateForce a new IP rotation.
{
"country": "GB"
}Use when: Your current IP got rate-limited and you need a fresh one.
You: "Check what Amazon.com shows from a US IP"
Claude: [calls proxy_fetch with country=US, returns HTML]
You: "Now check the same page from Japan"
Claude: [calls proxy_fetch with country=JP, returns different pricing/content]
You: "List all countries where I can route through"
Claude: [calls proxy_list_countries, returns 195+ countries]
You: "My current IP is blocked. Rotate to a new UK IP"
Claude: [calls proxy_rotate with country=GB, confirms new IP]
API key is passed via environment variable — never hardcoded
All traffic to target sites is TLS-encrypted
Proxy auth is plaintext to our proxy gateway only (same as any HTTP proxy)
No data is logged or stored by the MCP server
npm install -g proxyclaw-mcp-server
# Run directly
IPLOOP_API_KEY=your_key proxyclaw-mcp-serverOr with Docker:
docker run -e IPLOOP_API_KEY=your_key proxyclaw/mcp-server0.5 GB bandwidth included
All 195+ countries available
No credit card required
Upgrade anytime at iploop.io.
Website: proxyclaw.ai
Platform: iploop.io
GitHub: github.com/Iploop/proxyclaw-mcp
MCP Docs: modelcontextprotocol.io
Built with ⚡ by IPLoop
Check the current exit IP address and geo-location when routing through the proxy. Useful to verify which country/region your requests are coming from.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | 2-letter country code to check exit IP from (optional, auto-rotate if omitted) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries burden. It mentions 'auto-rotate if omitted' which is a key behavioral trait. However, it does not disclose whether the tool is read-only, potential side effects (e.g., token consumption), or error states.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, concise and to the point. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool is simple (1 optional param, no output schema). Description covers purpose and key behavior (auto-rotation). Could mention return format (IP, geo) but not critical for a simple check tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (country param described). Description adds context that country is optional and auto-rotation occurs if omitted, which goes beyond schema. However, no other parameters exist, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool checks 'exit IP address and geo-location' and its purpose to 'verify which country/region' the proxy is using. Distinct from siblings like proxy_fetch or proxy_rotate.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
States when to use: to verify proxy location. Does not explicitly mention when not to use or alternatives, but the context is clear enough. Siblings like proxy_list_countries or proxy_rotate imply alternatives for different needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Fetch a URL through the ProxyClaw residential proxy network. Routes the request through real residential IPs in 195+ countries. Use for geo-restricted content, anti-bot bypass, or multi-country research.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to fetch (must start with http:// or https://) | |
| country | No | 2-letter country code to route through (e.g., US, DE, JP). Auto-rotate if omitted. | |
| city | No | City name for city-level targeting (optional) | |
| session | No | Session ID for sticky IP (same IP across requests with same session ID) | |
| asn | No | ASN number for ISP-level targeting (optional) | |
| timeout | No | Request timeout in seconds (1-120, default: 30) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that it routes through residential IPs in 195+ countries, and mentions auto-rotation of IP if no country specified. However, since no annotations are provided, it should also mention potential side effects (e.g., cost, rate limits, IP rotation impact) which are missing. No contradiction with annotations as none exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences with no wasted words. It is front-loaded with the core action and then adds value with use cases.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 6 parameters (100% cover), no output schema, and no annotations, the description covers the main behavioral aspects. It could include a note about response format or potential failures, but overall it provides enough context for a competent agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the description does not need to repeat parameter details. The description adds context about country targeting and session stickyness but does not significantly expand beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches a URL through a residential proxy network, with specific use cases like geo-restricted content and anti-bot bypass. It distinguishes from siblings like proxy_check_ip (which checks own IP) and proxy_list_countries (which lists countries).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions when to use the tool (geo-restricted content, anti-bot bypass, multi-country research), but does not explicitly state when not to use it or provide alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List all 195+ countries available for routing through the ProxyClaw residential network.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It clearly states the tool returns a list of 195+ countries with routing capability, indicating a read-only operation. However, it does not disclose details like pagination, rate limits, or output format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It conveys the essential purpose efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters, no output schema, and performs a straightforward listing operation, the description is nearly complete. It could be improved by explicitly stating the return data structure or confirming it is a read operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has no parameters, so there is nothing to describe. The description adds value by indicating the tool lists all countries without need for input.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('countries available for routing through the ProxyClaw residential network'), and clearly distinguishes the tool from its siblings (e.g., proxy_check_ip, proxy_fetch, proxy_rotate) by its unique purpose of listing countries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies that the tool is meant to retrieve a list of all supported countries for routing, but does not explicitly state when to use it over alternatives. Provides no guidance on prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Force IP rotation by fetching with a new random session. Returns the new exit IP to confirm rotation worked.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | 2-letter country code (optional) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description discloses that the tool forces rotation and returns the new IP, which is sufficient behavioral context. However, it does not mention any side effects like invalidating existing sessions or rate limits. Since no annotations are provided, the description carries full burden, but it adequately covers the core behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, zero waste: states what it does and what it returns. Optimal for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity (1 optional param, no output schema, no nested objects), the description is sufficiently complete. It covers purpose, action, and outcome. Minor gap is lack of explicit statement about any prerequisites.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one optional parameter with 100% schema coverage; description does not add meaning beyond schema's '2-letter country code (optional).' Baseline 3 is appropriate as schema already explains the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool's action ('force IP rotation'), method ('fetching with a new random session'), and outcome ('returns the new exit IP to confirm rotation'). It is distinct from siblings like proxy_check_ip which checks current IP, and proxy_fetch which likely fetches a page.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Description implies when to use (when a new IP is needed) and provides confirmation mechanism. It does not explicitly state when not to use or mention alternatives, but the purpose is self-evident given sibling names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0proxy_check_ipproxy_fetchproxy_list_countriesproxy_rotateEach tool has a distinct purpose: check IP, fetch URL, list countries, and rotate IP. There is no overlap between these functions.
All tools follow a consistent 'proxy_verb' pattern (e.g., proxy_check_ip, proxy_fetch), making them easy to understand and remember.
The set of 4 tools covers the core proxy operations (check, fetch, list, rotate) without unnecessary extras, well-scoped for the proxy domain.
Core proxy workflows are covered: checking IP, fetching through proxy, listing countries, and rotating IP. One minor gap might be the lack of a tool to set the country explicitly, but rotation and checks suffice.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Crawl, scrape, search the web, and automate browsers at scale with anti-bot bypass.
Reliable web access for AI agents: smart HTTP, rotating proxies, and full-browser rendering.
The most accurate web access API. Stop getting blocked.
Enable language models to perform advanced AI-powered web scraping with enterprise-grade reliabili…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Iploop/proxyclaw-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
