proxy-finder-mcp
Related Servers
Alternatives to proxy-finder-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.44 npmMIT

Novada Proxyofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to route HTTP requests through millions of real residential IPs, bypassing anti-bot systems and geo-targeting by country or city.4MIT- AlicenseNot gradedqualityCmaintenanceRoutes AI agent HTTP requests through residential proxies to bypass anti-bot systems, geo-target by country/city, and maintain sticky sessions across multi-step workflows.18 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA geo-distributed HTTP proxy for AI agents, enabling web fetching from multiple global regions (Frankfurt, Sydney, New York, San Francisco) with support for screenshots, scraping, and JS rendering.MIT
- AlicenseBqualityCmaintenanceEnables MCP-compatible clients to list verified free HTTP, SOCKS4, and SOCKS5 proxies, pick top-ranked ones, and summarize the current proxy snapshot through three read-only tools, without forwarding traffic or accepting arbitrary URLs.339 npmMIT

quantumproxies-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to scrape, search, map, and crawl the web through residential proxies with real-browser TLS fingerprints, and to generate ready-to-use proxy endpoints of various types for any HTTP client.25183 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: find_proxy discovers and live-tests proxies, check_proxy validates one specific proxy, list_proxies returns cached listings without live testing, and list_countries enumerates coverage. The descriptions explicitly guide when to use find_proxy versus list_proxies or check_proxy, eliminating overlap.
All names follow a consistent snake_case verb_noun pattern (find/check/list + resource). The only minor deviation is list_proxies using plural while find_proxy and check_proxy use singular, but this is natural and predictable.
Four tools are well-scoped for a proxy-finding service: discovery, validation, listing, and country lookup. Each tool earns its place and none feels redundant or excessive.
The toolset covers the core discover-validate-list lifecycle for proxies and provides country enumeration. Minor gaps like detailed proxy metadata (e.g., response times, source) or a batch validation tool exist, but agents can work around them.