fusionproxy-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FUSION_PASS | Yes | Proxy password. | |
| FUSION_USER | Yes | Proxy username (main user or a sub-user). | |
| FUSION_COUNTRY | No | Default country when a call does not pass one. | |
| FUSION_GATEWAY | No | Gateway host:port, default resi.fusionproxy.net:12286. | resi.fusionproxy.net:12286 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Fetch public web pages through Fusion Proxy residential IPs. Use fetch_page when a site blocks direct requests, shows different content by country, or rate-limits. Pass a two-letter country code to see the page as a visitor from that country, and the same session name to keep one IP.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_pageA | Fetch a public web page through a residential IP and return its content. Args: url: http(s) URL of the page. country: two-letter country code of the exit IP (for example "us", "de", "jp"). Optional. session: any name; calls with the same name keep the same IP for 10 minutes. Optional. output: "markdown" (default, readable), "text" or "html" (raw). max_chars: cut the result to this many characters (default 20000). |
| check_exit_ipB | Show the IP address, location and network that websites see through the proxy. Args: country: two-letter country code of the exit IP. Optional. session: session name to check a sticky IP. Optional. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
fetch_page retrieves page content while check_exit_ip is a pure diagnostic that reports the exit IP/geo; their purposes are unmistakably distinct despite sharing the optional country/session parameters. An agent would never confuse the two.
Both tools follow the same snake_case verb_noun convention (fetch_page, check_exit_ip), with verbs that accurately describe the action. No mixing of styles or vague names.
Two tools is on the thin side; fetch plus a single diagnostic leaves little room for related operations. The scope is coherent, but the surface is closer to a minimal wrapper than a well-rounded toolset.
The core operation (proxied page fetch) and the key verification step (exit IP check) are both present, covering the main workflow. Minor gaps exist: no non-GET requests, no session management (list/clear/expire), and the sticky-IP duration is fixed.