proxy302-mcp
Related Servers
Alternatives to proxy302-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to pull live free proxy lists filtered by country, protocol, and anonymity, run real liveness and anonymity checks against candidate proxies, and look up geolocation, ASN, and network details for public IP addresses. All tools are read-only and require no API key or installation.MIT
Litport MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables coding agents and chat clients to inspect proxy tokens, usage, pools, geo targeting, and build ready-to-use proxy connection URLs via the Litport account API, while remaining read-only.60 npmMIT- AlicenseAqualityCmaintenanceProvides AI agents with access to a global residential proxy network covering over 190 countries for web fetching and scraping. It enables pay-per-request transactions using USDC on the Base network via the x402 protocol.366 npm2MIT

ScrapeOps MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI agents to browse the web, bypass anti-bots, render JavaScript, take screenshots, and perform structured data extraction using the ScrapeOps Proxy API.37 npmMIT
2extract MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to create and manage residential and mobile proxies with granular geo-targeting, traffic and spend limits, access restrictions, and usage/cost reporting.1MIT- AlicenseNot gradedqualityDmaintenanceEnables agents to autonomously route traffic through real 4G/5G mobile and residential IPs by country, with tools to check live proxy stock, obtain ready-to-use proxy URLs, and monitor remaining data usage.12 npmMIT
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.