No user-submitted related servers found.
Scored across 3 tools
get_proxies and check_proxies both return proxy lists and could be confused at a glance, but the descriptions clearly delineate cached-public-list vs. locally-verified, and fetch_url is a distinct consumer action. Boundaries are recoverable without much risk of misselection.
All three tools use a clean snake_case verb_noun pattern (get_proxies, check_proxies, fetch_url) with consistent imperative verbs. No mixed conventions or vague naming.
Three tools is slightly lean but each earns its place: acquire a list, verify locally, then use a proxy to fetch. The small surface fits a narrow proxy-scraping domain rather than feeling arbitrarily truncated.
The core workflow (list, validate, use) is fully covered, but the toolset mentions updating local statistics that no tool can read back, and there is no filtering by protocol/country or proxy-detail retrieval. These are minor gaps an agent can work around.