proxy-scraper

Get working proxies

get_proxies

Read-onlyIdempotent

Retrieve working free proxies from an hourly refreshed list, filtered by protocol, country, HTTPS, speed, stability, and site compatibility.

Instructions

Get working free proxies right now, fastest first.

Instant: comes from a public list that is re-checked every hour from GitHub's servers, so a proxy may have died since, and some behave differently from this machine's network. Use check_proxies when they must work from here right now. Every result has a ready-to-use url like socks5://1.2.3.4:1080.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	How many to return (fastest first)
`protocol`	No	Proxy protocol. socks5 works for any TCP traffic, http is what most HTTP clients expect.	any
`works_on`	No	Only proxies that got through to all of these sites in the last hourly check (most free proxies get a captcha or a 403 there)
`countries`	No	Two-letter country codes of the exit IP, e.g. ['DE', 'NL']. Empty = any country.
`elite_only`	No	Only proxies the target can't recognize as proxies
`https_only`	No	Only proxies that tunnel HTTPS with verified TLS. Needed for https:// sites.
`stable_only`	No	Only proxies that have worked for 24 h or more
`max_latency_ms`	No	Maximum response time, 0 = any
`min_speed_kbps`	No	Only proxies that downloaded at least this many KiB/s in the last hourly check, e.g. 300 for loading real pages
`exclude_datacenter`	No	Skip exits in datacenters (blocked by many sites)
`min_uptime_percent`	No	Only proxies that passed at least this share of the last 7 days' hourly checks, e.g. 90 for the most reliable
`exclude_blocklisted`	No	Skip exits on the SpamCop blocklist (fewer captchas)

Output Schema

TableJSON Schema

Name	Required	Description
`note`	Yes	What to do if fewer proxies matched than asked for
`matched`	Yes	How many proxies in the list pass the filters (limit cuts the rest)
`proxies`	Yes	Fastest first
`list_updated`	Yes	When the list was last checked (ISO 8601, UTC)
`list_age_minutes`	Yes	Minutes since that check

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.25.0Oct 6, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover readOnly/openWorld/idempotent safety. The description adds genuinely non-structured traits: hourly re-verification, possible staleness, and network-dependent behavior, plus the return shape ('ready-to-use url like socks5://1.2.3.4:1080'). It stops short of failure modes (rate limits, empty results), so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the purpose and the routing advice. The 'Instant:' fragment slightly re-states the opening 'right now', a minor redundancy, but nothing is wasted overall.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, no-required-argument retrieval tool with a full output schema and annotation coverage, the description supplies freshness caveats, the alternative tool, and result format. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across all 12 parameters, so the schema already carries the parameter burden. The description only restates the ordering guarantee ('fastest first') that the limit field documents, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get working free proxies') plus a scope qualifier ('right now, fastest first'). The agent can immediately distinguish this from check_proxies and fetch_url, which is reinforced by the explicit routing sentence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the alternative ('Use check_proxies when they must work from here right now') and states the condition that selects it, i.e. that this list is re-checked remotely and may not reflect the local network. This is a clear when/when-not rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server