The pairing that matters is check-then-fetch: confirm which country and IP you are exiting from, then request the page, so a result attributed to "a US visitor" actually came from one. Sticky sessions keep a sequence of requests on one IP when a site expects continuity, and forced rotation is the way out when the current one gets rate-limited.
A fetch tool routed through the ProxyClaw residential proxy network. You give it a URL and a country, and the request leaves from a residential IP there.
- Any URL fetched through a residential exit, targeted by country and optionally by city or ASN
- Sticky sessions — pass a session id and subsequent requests keep the same IP
- A timeout you set per request
- The current exit IP and its geo-location, so you can confirm where a request will appear to come from before making it
- The 195+ countries available for routing, which is how you get the exact two-letter code
- Forced rotation to a new random session, returning the new exit IP as confirmation
An IPLoop account and an API key from iploop.io, passed as IPLOOP_API_KEY — it is the one required setting. The free tier includes 0.5 GB of bandwidth with all countries available and no credit card. Run it with npx -y proxyclaw-mcp-server over stdio, from the npm package proxyclaw-mcp-server, currently 1.0.4, or from the published Docker image. Bandwidth is what you pay for, so the cost of a run scales with what you fetch. This is the Node.js server, which does proxy routing and fetching; a separate Python one adds headless rendering and structured extraction.
One command plus a key — npx proxyclaw-mcp-server, then supply credentials