proxy302-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY302_API_KEY | Yes | Required. Your Proxy302 API key, either as `<key id>:<secret>` or a `Basic ...` token. Alternatively, when used with PROXY302_API_SECRET, this may hold only the key id. | |
| PROXY302_BASE_URL | No | Optional. Base URL for the Proxy302 API. | https://proxy302.com |
| PROXY302_API_SECRET | No | Optional. Use with PROXY302_API_KEY holding only the key id. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_account_usageA | Show the account tied to the API key, wallet balance (PTC), remaining prepaid traffic, and traffic used per day for the last N days. Read-only. |
| list_countriesA | List countries Proxy302 can target. Optional name filter (substring). Returns ids usable in other tools. Read-only. |
| list_regionsA | List states of a country, or cities of a state. Pass either country (name/code/id) or state_id. Read-only. |
| list_productsA | Describe the proxy products and list the static IP plans (data center and residential) with their plan ids. Read-only; prices are shown on proxy302.com. |
| get_dynamic_proxyA | Return a ready-to-use rotating residential proxy URL for a country (optionally state/city). Reuses an existing matching proxy of yours; with create_if_missing=true it creates a new credential if none exists (creating is free, traffic is billed only when used from your prepaid pool). |
| list_my_proxiesA | List proxies on the account: dynamic or static, billed by traffic or by IP. Passwords are masked unless include_credentials=true. Read-only. |
| fetch_urlA | Request a URL from your machine through one of your Proxy302 proxies (optionally exiting in a given country) and return the page as Markdown, plain text or raw. No JavaScript rendering: for JS-heavy sites use a browser with the proxy URL from get_dynamic_proxy. Uses your proxy traffic. |
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 7 tools
Most tools are cleanly separated by resource and action: geo lookups (list_countries/list_regions), catalog (list_products), account state (get_account_usage/list_my_proxies), and actions (get_dynamic_proxy/fetch_url). The only mild overlap is between get_dynamic_proxy and list_my_proxies, since get_dynamic_proxy may reuse an existing proxy, but the descriptions make the boundary (return a usable URL vs. enumerate proxies) clear enough.
All names follow a consistent snake_case verb_noun pattern (get_*, list_*, fetch_url). The verb choice matches read-only vs. action semantics predictably. Minor quirks like 'my' in list_my_proxies don't break the pattern.
Seven tools is a tight, well-scoped surface for a proxy service: discovery, account state, credential retrieval, and a fetch helper. Every tool maps to a distinct step in a plausible workflow, with no obvious filler.
The read/lookup and proxy-use lifecycle is covered, but there are notable gaps: list_products exposes static IP plan ids yet there is no tool to order/purchase a static plan, and there is no delete/revoke operation for proxies or credentials. Agents can still accomplish core scraping workflows but hit dead ends on provisioning and cleanup.