# proxy-scraper

> Updated 2026-09-26 · type: tool · category: data-scraping · status: active · rev 1

proxy-scraper pulls proxies from 700+ sources and verifies them with honeypot, injected-script and TLS checks, then serves a rotating proxy and an MCP server.

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing model: free
- Best for: An engineer running scraping or enrichment pipelines who wants owned proxy infrastructure — collection, verification and rotation they control — plus an MCP endpoint so an AI agent can fetch through vetted proxies, rather than paying a managed proxy vendor.
- Last verified: 2026-09-26

- **Canonical:** https://gtmstacker.com/registry/tool/proxy-scraper/
- **Source:** [maximilianfeix · GitHub](https://github.com/maximilianfeix/proxy-scraper)
- **Tags:** data-scraping, mcp-agents, self-hostable, proxies, verification, rotating-proxy
- **Repository:** https://github.com/maximilianfeix/proxy-scraper

## Is proxy-scraper open source?

Yes, proxy-scraper is open source under the MIT license.

## How much does proxy-scraper cost?

proxy-scraper is free to use.

## Can I self-host proxy-scraper?

Yes, proxy-scraper can be self-hosted (the source is available under the MIT license).

## Alternatives & related

- [DeepScrape](https://gtmstacker.com/registry/tool/deepscrape/)
- [Scrapy](https://gtmstacker.com/registry/tool/scrapy/)


---

proxy-scraper is a self-hostable proxy scraper and verifier that pulls candidate proxies from 700+ sources, then runs honeypot, injected-script and TLS checks, and can serve a rotating proxy plus an MCP server for AI agents. Open source: yes (MIT); self-hostable via pipx, pip or Docker. It has 5 stars and was created 2026-09-24.

## What it does

proxy-scraper is two stages: collection and verification. It gathers HTTP, SOCKS4 and SOCKS5 candidates from 700+ public sources, then subjects each to a verification battery — a honeypot confirmation fetch, content-tampering/injected-script detection, TLS verification for HTTPS, real-IP validation, and two independent page fetches before a proxy is trusted. Survivors can be served two ways: `--serve` stands up a local rotating proxy on port 8899 (weighted, round-robin or fastest-only), and `proxy-scraper-mcp` exposes tools (`get_proxies`, `check_proxies`, `fetch_url`) so an AI agent can route requests through vetted proxies. Open source: yes (MIT); self-hostable via pipx, pip or Docker.

## Provenance

- MIT (OSI-open); 5 stars, created 2026-09-24, last push 2026-09-26; pulls proxies from 700+ sources and verifies via honeypot, injected-script and TLS checks; ships a rotating proxy server and an MCP server; installs via pipx/pip/Docker (WebFetch 2026-09-26).
- Surfaced via studio discovery in the 2026-09-26 pass.
- Anti-hype note — load-bearing: the README's 'one in five working proxies injected a script' figure is asserted with no backing dataset in the repo; it is the tool's own unverified claim and is not stated as fact anywhere in this entry.
- Curated from the GTM Stacker signal registry (2026-09-26 pass); license/facts independently verified 2026-09-26.

## Why it matters for a GTM stack

Scraping and enrichment pipelines usually rent proxies from a managed vendor, which means recurring cost and a dependency you do not control. proxy-scraper's angle is owned proxy infrastructure: collect candidates yourself, verify them yourself, and rotate them through a local server you run — with an MCP endpoint so an agent-driven enrichment step can fetch through vetted proxies directly. For a team building agent-driven scraping or prospecting enrichment, that is the difference between a proxy line-item and infrastructure you own. Open source: yes (MIT); pricing: free; self-hostable. The honest read: at 5 stars it is early, the injected-script ratio it cites is unverified vendor framing, and public proxies carry trust and legal risk no verifier fully removes — evaluate the verification mechanics on your own traffic before relying on them.