proxy_check_ip
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.
LABSCO SUMMARY
Geo-targeted fetching where you can verify the exit before trusting the result.
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.
What it is
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.
What you get
- 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
Requirements
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. 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.
Setup effort
One command plus a key — npx proxyclaw-mcp-server, then supply credentials
USE CASES
01
Seeing what a page shows to visitors in another country
Confirm the exit location first, then fetch the URL with that country set.
02
Comparing regional pricing on the same page
Fetch the same URL twice with different country codes and read the difference.
03
Keeping a multi-step flow on one identity
Pass the same session id across the requests so the exit IP stays put.
04
Getting unblocked after a rate limit
Force a rotation in the country you need and take the new exit IP that comes back.
05
Finding the right country code before scripting a run
List the available countries and take the two-letter code from there.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
proxy_fetch
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.
proxy_list_countries
List all 195+ countries available for routing through the ProxyClaw residential network.
proxy_rotate
Force IP rotation by fetching with a new random session. Returns the new exit IP to confirm rotation worked.
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. proxy_fetch_stealth, proxy_render, proxy_scrape and proxy_extract belong to the sibling Python server; use that one for JS-rendered pages, anti-detection and structured extraction.
Requires
- npx on PATH
- IPLOOP_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx proxyclaw-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"proxyclaw": {
"command": "npx",
"args": [
"-y",
"proxyclaw-mcp-server"
],
"env": {
"IPLOOP_API_KEY": "<YOUR_IPLOOP_API_KEY>"
}
}
}
}
