proxy-scraper
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@proxy-scraperget me a fresh list of working proxies"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Install · Live list · For AI agents · Proxy server · How it works · Recipes · Options · FAQ
Most free proxy lists are 95 % dead, and a good part of the rest are honeypots or proxies that inject scripts into your pages. proxy-scraper collects public HTTP, SOCKS4 and SOCKS5 proxies from 700+ sources and keeps only the ones that pass every check. It learns with every run which sources are worth it, and it can turn the result into a single rotating proxy.
Install
With pipx (recommended – gives you a proxy-scraper command in its own environment):
pipx install proxy-scraper-cli
proxy-scraperThe package is called proxy-scraper-cli on PyPI (the plain name is taken), the command is proxy-scraper.
# Docker – learned state and results stay in two folders next to you
mkdir -p proxy-data results
docker run --rm --user "$(id -u):$(id -g)" -v "$PWD/proxy-data:/data" -v "$PWD/results:/work/results" \
ghcr.io/maximilianfeix/proxy-scraper --want 50 --https-only
# pip into the current environment
pip install proxy-scraper-cli
# optional: faster event loop on macOS/Linux
pipx install "proxy-scraper-cli[fast]"
# the latest main instead of the latest release
pipx install git+https://github.com/maximilianfeix/proxy-scraper.git
# no install at all
git clone https://github.com/maximilianfeix/proxy-scraper.git
cd proxy-scraper
pip install -r requirements.txt
python3 proxy_scraper.pyEvery release also ships a wheel you can install with pip install <file>.whl, and a multi-arch image (amd64/arm64) on ghcr.io. In the container the wizard never shows up, it runs straight away. For the proxy server use --serve --serve-host 0.0.0.0 with -p 127.0.0.1:8899:8899, so the port is only open on your own machine.
Tab completion for bash, zsh and fish:
eval "$(proxy-scraper --completion zsh)" # in ~/.zshrc (after compinit), same for bash in ~/.bashrc
proxy-scraper --completion fish > ~/.config/fish/completions/proxy-scraper.fishInstalled, the learned state lives in your user data folder (~/Library/Application Support/proxy-scraper, %LOCALAPPDATA%\proxy-scraper or ~/.local/share/proxy-scraper; override with PROXY_SCRAPER_HOME) and results go to ./results. Run from a clone, both stay inside the project.
Started without arguments, a wizard asks what you are looking for:
Preset | What it does |
Find everything | all protocols, maximum yield |
Browsing & web | HTTP + SOCKS5, HTTPS-capable, at least anonymous, under 3 s |
Maximum anonymity | elite SOCKS5 with HTTPS only |
Fast & stable | proxies under 1 s only |
A few right now | stops after 25 hits |
Recheck the last hits | no collecting, takes seconds |
Proxy server right away | recheck the last hits, then serve them on :8899 |
Same as last time | your previous choice |
Custom … | protocols, countries, anonymity, HTTPS, target site, latency, amount, check mode |
Keys: ↑↓ select · Space toggle · 1–9 jump · Enter next · Esc back · q quit. In scripts and cron jobs the wizard never shows up – pass options or -y.
Related MCP server: MCP Server (fac_mcp_hub)
Live proxy list
Don't want to scan yourself? Every hour GitHub Actions runs the tool and publishes the hits to the proxy-list branch – every entry worked in the last run, fastest first.
→ Browse it on the website – search, filter by type, country, HTTPS, provider and latency, see how long each proxy has been up, copy or download exactly the proxies you need. streaks.json on the branch has the number of runs in a row for every proxy.
Every protocol and country also has its own page with a plain download, e.g. SOCKS5 or Germany (country/de/proxies.txt).
List | Format | Link |
All |
| |
HTTP · SOCKS4 · SOCKS5 |
| |
HTTPS-capable only |
| |
Elite only |
| |
With all details | latency, country, HTTPS, anonymity, exit IP |
curl -s https://raw.githubusercontent.com/maximilianfeix/proxy-scraper/proxy-list/socks5.txt | headOr let the tool start from it: proxy-scraper --recheck live downloads the list and checks it again from your network – about 30 seconds instead of a full scan (517 of 1,169 worked from here). With --serve you have a rotating proxy in under a minute.
For AI agents (MCP)
proxy-scraper-mcp is an MCP server: Claude Code, Claude Desktop, Cursor, VS Code, Codex and any other MCP client can ask for working proxies and load pages through them.
Tool | What it does |
| working proxies right now, from the hourly list – filter by protocol, country, HTTPS, elite, no datacenter, not blocklisted, stable, latency |
| checks proxies from your own network, so they work from where your code runs (30–90 s, reports progress) |
| loads a page through a verified proxy, switches proxies by itself when one fails, returns readable text – HTTPS only through proxies with verified TLS |
Things to ask your agent: "Load bbc.com/news as seen from the UK", "Give me 5 SOCKS5 proxies from Germany that aren't in a datacenter", "Check which of these sites block free proxies".
Needs uv – it fetches a suitable Python by itself if yours is older than 3.10. Claude Code:
claude mcp add proxy-scraper -- uvx --python ">=3.10" --from "proxy-scraper-cli[mcp]" proxy-scraper-mcpClaude Desktop, Cursor and most other clients – add this to the MCP config (Claude Desktop: Settings → Developer → Edit Config, Cursor: ~/.cursor/mcp.json):
{
"mcpServers": {
"proxy-scraper": {
"command": "uvx",
"args": ["--python", ">=3.10", "--from", "proxy-scraper-cli[mcp]", "proxy-scraper-mcp"]
}
}
}VS Code – .vscode/mcp.json:
{
"servers": {
"proxy-scraper": {
"type": "stdio",
"command": "uvx",
"args": ["--python", ">=3.10", "--from", "proxy-scraper-cli[mcp]", "proxy-scraper-mcp"]
}
}
}Codex – ~/.codex/config.toml:
[mcp_servers.proxy-scraper]
command = "uvx"
args = ["--python", ">=3.10", "--from", "proxy-scraper-cli[mcp]", "proxy-scraper-mcp"]Without uv: pipx install --python python3.12 "proxy-scraper-cli[mcp]" (any Python 3.10+), then use proxy-scraper-mcp as the command.
It's also in the official MCP registry as io.github.maximilianfeix/proxy-scraper, so clients that browse the registry can install it from there.
The server tells agents what it tells you: free proxies are run by strangers, so no logins, cookies or personal data through them. Local and private addresses are refused, and results go to proxy-scraper's data folder, not into the project you're working in.
Features
Setup wizard Started without arguments, the tool asks what you need using the arrow keys – a preset or step by step. At the end it shows the matching command line.
Fast
700+ sources fetched in parallel, large lists parsed on all CPU cores, hand-written HTTP/SOCKS handshakes directly on asyncio with 2000+ checks at once.
Real verification Every hit has to fetch two independent pages – that weeds out honeypots that only answer check requests (in some runs 5 out of 6 “hits”). A third request catches proxies that tamper with content: in our measurements one in five working proxies injected a script into a plain HTML page. Plus: HTTPS through a tunnel with verified TLS, anonymity level elite / anonymous / transparent and the country of the exit IP.
Learns with every run
Hit rate per source, history of working proxies, automatic removal of dead and stale lists. With -l 5000 you get the best 5000 candidates, not just any.
Finds new sources by itself Searches GitHub for actively maintained proxy lists and reads source lists maintained by others. Spam clone farms and plain mirrors are detected.
Filters & target sites
With --target google.com a proxy only counts if it really reaches the site – many public proxies are blocked by Google, Discord & co. Filter by country, HTTPS, anonymity and latency, and stop with --want 50 as soon as enough matching proxies are found. Filters even speed things up: with --max-latency 1000 slow proxies are given up after 1 s instead of 8 s.
Live dashboard Speed chart, latency histogram, protocols, countries and the latest hits in real time. Ctrl+C stops at any time and saves everything.
Rotating proxy server
--serve turns the hits into a local proxy that sends every connection through a different one – with automatic failover when one hangs.
Runs everywhere
macOS, Linux and Windows, Python 3.9 to 3.13. Only two dependencies: rich and certifi. It even notices when a firewall blocks proxies.
Thoroughly tested
450+ tests run offline against real mini proxies and honeypots on localhost – on Linux, macOS and Windows with Python 3.9, 3.11 and 3.13.
Why not just download a list?
Typical proxy list repo | proxy-scraper | |
Proxies checked right before you use them | ❌ | ✅ |
Honeypots that fake a successful check filtered out | ❌ | ✅ |
Proxies that inject scripts or ads filtered out | ❌ | ✅ |
HTTPS tested with verified TLS | rarely | ✅ |
Anonymity level and country per proxy | sometimes | ✅ |
Only proxies that reach your target site | ❌ | ✅ |
Learns which sources are worth it | ❌ | ✅ |
Usable as a single rotating proxy | ❌ | ✅ |
Ready-made list without running anything | ✅ |
Examples
# 50 proxies that can do HTTPS – then stop
proxy-scraper --want 50 --https-only
# only Germany, Austria and Switzerland, the 20,000 most promising candidates
proxy-scraper --country DE,AT,CH -l 20000
# fast elite SOCKS5 proxies
proxy-scraper --types socks5 --anonymity elite --max-latency 1500
# 20 proxies that really reach Google AND Discord
proxy-scraper --target google.com --target discord.com --want 20
# only recheck the last hits (plus history) – takes seconds
proxy-scraper --recheck
# wizard with defaults – it keeps what you already passed
proxy-scraper -i --country DE
# which sources deliver the most?
proxy-scraper --list-sourcesRunning from a clone? Replace proxy-scraper with python3 proxy_scraper.py.
From Python
from proxyscraper import check_proxies, find_proxies
if __name__ == "__main__": # needed on macOS/Windows, the parser uses a process pool
for p in find_proxies(want=20, https=True, countries=["DE", "NL"], no_datacenter=True):
print(p.url, p.latency, p.country, p.org)
alive = check_proxies(["socks5://1.2.3.4:1080", "5.6.7.8:3128"]) # your own listSame run as the command line – sources, learning, every check, result files – just without terminal output. Each result has url, latency, exit_ip, https, anonymity, country, asn, org and hosting. There's an async version of both (find_proxies_async, check_proxies_async).
Rotating proxy server
A list is nice – but usually you just want to enter one proxy that always works:
proxy-scraper --recheck --serve # recheck the last hits, then go – takes secondscurl -x http://127.0.0.1:8899 https://api.ipify.org # a different IP every time
curl -x socks5h://127.0.0.1:8899 https://api.ipify.org # SOCKS5 on the same port
curl -x http://country-de:x@127.0.0.1:8899 https://api.ipify.org # only German exits
curl -x http://session-cart42:x@127.0.0.1:8899 https://shop.example # same proxy for this session
curl http://127.0.0.1:8899/__proxy-scraper/status # pool and counters as JSON
curl http://127.0.0.1:8899/__proxy-scraper/metrics # the same for Prometheus/GrafanaLike commercial rotating proxies, the username carries what you want: country-XX, type-http|socks4|socks5 and session-NAME, combinable (country-us-type-socks5-session-a). It works for HTTP (Proxy-Authorization) and SOCKS5 (username/password auth). By default the password is ignored and the server only listens on 127.0.0.1.
To reach it from other machines, give it a password – every client then has to send it, over HTTP and SOCKS5 alike, and the status page wants it as Basic auth:
export PROXY_SCRAPER_SERVE_PASSWORD=$(openssl rand -hex 16) # the env var keeps it out of `ps`
proxy-scraper --recheck --serve --serve-host 0.0.0.0
curl -x "http://country-de:$PROXY_SCRAPER_SERVE_PASSWORD@your-server:8899" https://api.ipify.orgWithout a password, --serve-host means anyone who reaches the port can use it. The ready-made compose.yaml starts the server in Docker from the live list, with a password, a health check and learned state in a volume: put PROXY_PASSWORD=… into .env, then docker compose up -d.
Option | What it does |
| default: fast and proven proxies more often, everyone gets a chance |
| evenly, at random or in turn |
| always the fastest one that isn't busy |
| the same site keeps its proxy for 5 minutes (logins, carts) |
every connection goes through a different proxy (unless sticky); fast and proven ones are preferred
CONNECTfor HTTPS and plain HTTP requests; HTTP, SOCKS4 and SOCKS5 proxies can sit behind it (SOCKS5 with DNS through the proxy)HTTPS only uses proxies that passed the test with verified TLS – no broken encryption
if a proxy stays silent inside the tunnel or returns an error page instead of TLS, the same first packet quietly goes to the next one
three failures in a row and a proxy leaves the rotation – every 5 minutes those get re-checked and come back if they work again
--serve-refill 6checks fresh proxies every 6 hours in the background (the live list with--recheck live, otherwise the last run + history) with the same checks and filters, and adds the hits – a server that runs for days doesn't run drylistens on
127.0.0.1only (unless--serve-hostsays otherwise), optionally with a password; live view with requests, success rate, pool and the latest connections
In testing: 20 of 20 HTTPS requests succeeded, over 15 different exit IPs. In the wizard this is Proxy server right away.
Discord bot
The live list can also come to you: bot/ is a Discord bot that posts every run into a server – a summary with the fastest proxies, the full lists per protocol as files, and slash commands like /proxies type:socks5 country:DE https:true. It sets up its own read-only channels when you invite it, and a GitHub Action deploys it to a server as a systemd service. Setup in bot/README.md.
How it works
flowchart LR
A[sources.json<br/>meta lists<br/>GitHub discovery] --> B[Fetch & parse<br/>in parallel on all cores]
B --> C[Prioritize<br/>history → good sources → rest]
C --> D[Check<br/>HTTP · SOCKS4 · SOCKS5]
D --> E[Details<br/>HTTPS · anonymity · country]
E --> F[results/]
D -. hit rate per source .-> G[(learned state)]
G -. next run .-> CSources – the curated list in
sources.json, meta sources (other projects that maintain lists of proxy sources) and, once a day, a GitHub search for actively maintained repos. Every search adds to what earlier ones found; a list the search hasn't seen for three weeks drops out.Collect – plain text, HTML tables, JSON APIs and
type://ip:portlines are recognized; private and reserved address ranges are dropped. Lists that haven't changed since the last run answer304and come from a local cache – a second run right after the first loads 0 MB instead of ~160 MB.Prioritize – known working proxies first, then by the learned hit rate of their sources.
Check – every proxy has to fetch its exit IP from a check target (
checkip.amazonaws.com, withifconfig.me,ipinfo.io,wtfismyip.comandident.meas reserves – none of them behind Cloudflare) and return a valid, foreign IP. If the target goes down mid-run, the tool switches and re-checks the proxies that were affected, so the statistics don't learn from an outage. Anyone passing your own IP through is out. Then comes the confirmation viahttpbin.org: fake proxies that only answer the first check with “200 + IP” fail here. Finally a static HTML page has to arrive byte for byte as it does without a proxy – anyone injecting ads or scripts is out.Countries and providers – looked up offline in the free DB-IP databases, including the provider (ASN) and whether it's probably a datacenter (about 45 % of working proxies are) (downloaded once a month, ~2 µs per lookup); ip-api.com is only asked for the few addresses it doesn't know.
Blocklists – one DNS lookup per exit IP against SpamCop, cached for the run: about 29 % of working proxies exit from a listed IP, and sites that use the list show those captchas or block them.
--no-blocklisteddrops them. If your DNS resolver is refused by SpamCop (large public resolvers are), the lookup is skipped instead of guessing.Learn – hit rates and history are stored. Sources without hits, with content unchanged for a week or permanently unreachable are skipped.
Output
Every run gets its own folder; results/latest.txt always names the newest one (on macOS/Linux there is also the symlink results/latest):
results/2026-09-24_18-42-07/
├── all.txt socks5://203.0.113.10:1080 (fastest first)
├── http.txt 203.0.113.20:8080 (plain ip:port lists per type)
├── socks4.txt
├── socks5.txt
├── proxies.json latency, country, HTTPS, anonymity, exit IP
└── proxies.csvRecipes
Use the fastest proxy from the last run – free proxies die quickly, so --recheck first if the run is older than a few minutes
proxy-scraper --recheck -y
curl -x "$(head -1 results/latest/all.txt)" http://api.ipify.orgFor HTTPS, pick a proxy with "https": true from proxies.json – like the Python example below does.
Python requests (pip install "requests[socks]" for SOCKS)
import json
from pathlib import Path
import requests
run = Path("results") / Path("results/latest.txt").read_text().strip() # works on every OS
proxies = json.loads((run / "proxies.json").read_text()) # fastest first
for p in proxies:
if not p["https"]:
continue
try:
r = requests.get("https://api.ipify.org", proxies={"http": p["url"], "https": p["url"]}, timeout=8)
print(p["url"], "→", r.text)
break
except requests.RequestException:
continue # free proxies come and go – just take the next oneproxychains, Clash / Mihomo – ready-made configs with --export
proxy-scraper --want 30 -y --export proxychains,clash
proxychains4 -f results/latest/proxychains.conf curl https://api.ipify.orgclash.yaml has all HTTP and SOCKS5 proxies plus a url-test group that always picks the fastest. Both configs leave out HTTP proxies that can't tunnel (CONNECT), because these tools tunnel everything.
In a pipe – -o - prints the hits to stdout, the interface moves to stderr
proxy-scraper --recheck live --want 20 -y -o - | grep '^socks5://' > socks.txtAny tool, through the rotating server
proxy-scraper --recheck --serve &
export HTTPS_PROXY=http://127.0.0.1:8899 HTTP_PROXY=http://127.0.0.1:8899
pip download requests # git, pip, npm & co. now go through the poolWithout installing anything – straight from the live list
curl -s https://raw.githubusercontent.com/maximilianfeix/proxy-scraper/proxy-list/https.txt | head -5The shell snippets are for macOS and Linux, where results/latest points to the newest run. On Windows, results/latest.txt holds the folder name instead – in PowerShell:
$run = "results\$(Get-Content results\latest.txt)"
curl.exe -x (Get-Content "$run\all.txt" -TotalCount 1) http://api.ipify.orgOptions
Option | Description |
| setup wizard (shown automatically without arguments) |
| start right away without the wizard |
| only these protocols |
| only check the N most promising proxies |
| stop as soon as N matching proxies are found |
| only these countries |
| only proxies that can tunnel HTTPS |
| minimum anonymity ( |
| maximum latency |
| skip proxies whose exit is (probably) in a datacenter – those get blocked sooner |
| skip proxies whose exit IP is on the SpamCop blocklist – those often get captchas |
| skip the blocklist lookup |
| only proxies that reach this site (repeatable) |
| only check proxies from a file, the last run, or the public live list |
| skip the HTTPS test (confirmation and anonymity still run) |
| skip the country lookup |
| simultaneous checks (default: 2000) |
| timeout per proxy (default: 8 s) |
| search GitHub for new sources right now |
| download every list again (unchanged ones are normally skipped via ETag) |
| show the source ranking |
| where the proxy server listens (default |
| clients must send this password in the proxy login; better set |
| how the proxy server picks proxies, see above |
| while serving, check fresh proxies every HOURS and add the hits to the pool |
| afterwards serve as a rotating proxy on |
| also write all hits to this file; |
| extra files for other tools: |
| print the version |
| print the tab completion script for bash, zsh or fish |
Everything else: proxy-scraper --help
For the GitHub search a logged-ingh or the GITHUB_TOKEN environment variable is enough. Without a token the API limit is 60 requests per hour, and only 40 repos are searched.
GitHub Actions
The repo does part of the work itself:
Workflow | What it does |
3 operating systems × 3 Python versions, plus a built and installed package – on every push and pull request | |
| |
security analysis on every push and once a week | |
every hour: collect, check, publish to | |
builds the image on every change and runs a real scan inside it; on a version tag it publishes | |
on a version tag: test, build, smoke-test and publish a GitHub release with the wheel | |
tests the bot and deploys it to the server on every change in | |
Dependabot | keeps the action versions up to date |
FAQ
Many company, school and university networks block proxy connections. The tool notices a hit rate below 0.2 % and warns you – a different network such as a phone hotspot helps. The learned statistics are not downgraded in such a run.
Yes, in PowerShell and Windows Terminal. uvloop doesn't exist there and is skipped automatically. In the old cmd.exe window some symbols may be missing depending on the font.
Because only proxies that pass every check are kept. Many lists count anything that accepts a TCP connection; here a proxy must fetch two independent pages and show a foreign IP. That's usually a few hundred out of a million candidates – but they work.
Lines like socks5://user:pass@1.2.3.4:1080 keep their login: HTTP proxies get a Proxy-Authorization header, SOCKS5 uses username/password auth (RFC 1929), SOCKS4 the user ID. The same works for --recheck with your own list. The result files keep the credentials, the terminal only shows user:•••.
It's rebuilt every hour; the “updated” badge shows the last run. Free proxies come and go quickly, so for anything important run proxy-scraper --recheck right before use.
Only for things that don't matter. Public proxies are run by strangers who can read everything that isn't encrypted. Never send passwords or personal data through them, and only use them for legal purposes.
Roadmap
What's next is tracked in the milestone v1.8 – ideas and wishes are welcome as an issue. During Hacktoberfest there are beginner-friendly issues with pointers on where to start.
Shipped in v1.7: an MCP server so AI agents get working proxies and can load pages through them, 28 new sources and a GitHub search that runs daily and keeps what it found, and a cleaner website.
Shipped in v1.6: spam blocklist check for every exit IP, a live list refreshed every hour, pages per protocol and country, an optional password for the proxy server and a pool that refills itself while it runs, compose.yaml, -o - for pipes, a Discord bot, and a new website and README – everything in English now.
Shipped in v1.5: content tampering check, live list website with trend and stable proxies, provider/datacenter info, a much bigger proxy server (rotation strategies, sticky sessions, SOCKS5 inbound, status and Prometheus metrics), --recheck live, Python API, shell completion. Measured and dropped earlier: protocol detection with an extra connection (#3) and IPv6 (#1).
Contributing
Bug reports, new sources and pull requests are very welcome – see CONTRIBUTING.md, and docs/ARCHITECTURE.md for how the pieces fit together. The short version:
pip install -e ".[dev]"
python3 -m pytest # runs offline – fake proxies on localhost
ruff check .
python3 docs/make_demo.py # regenerate the images in this READMEproxy_scraper.py entry point when run from a clone
bot/ Discord bot for the live list (own requirements, deployed by GitHub Actions)
proxyscraper/
├── cli.py arguments, wizard or direct start
├── app.py one run in phases: network → jobs → check → learn & report
├── options.py RunOptions + Filters – all settings in one place
├── pipeline.py collect sources, prioritize, check loop
├── checker.py checks, honeypot confirmation, HTTPS test
├── handshake.py HTTP/SOCKS4/SOCKS5 handshakes incl. login
├── judges.py check targets, Cloudflare filter, failover
├── sources.py source lists, meta sources, GitHub discovery, statistics
├── sources.json curated sources
├── fetchcache.py ETag cache for unchanged lists
├── parsing.py find proxies in text, HTML and JSON
├── history.py history of working proxies
├── geo.py countries: offline first, ip-api.com as fallback
├── asndb.py DB-IP provider database, datacenter heuristic
├── geodb.py DB-IP country database (monthly, binary search)
├── targets.py target sites for --target
├── output.py result files
├── exporters.py proxychains, Clash and curl formats (--export)
├── server/ rotating proxy server (--serve): pool · http · upstream · socks · status · core
├── api.py find_proxies() / check_proxies() for Python
├── agent.py MCP tools without the SDK: live list, filters, fetch through proxies
├── mcp_server.py MCP server (proxy-scraper-mcp) for AI agents
├── publish.py live list for GitHub Actions
├── paths.py where state and results are stored
├── compat.py differences between Unix and Windows
├── netio.py small HTTP client on asyncio
└── ui/ widgets · dashboard · report · wizard · serve · keysAcknowledgements
proxy-scraper stands on the work of the people who publish free proxy lists. Thanks to everyone listed in sources.json, and especially to
monosans/proxy-scraper-checker and gfpcom/free-proxy-list, whose curated source collections are read as meta sources
Textualize/rich, which draws the whole terminal UI
IP Geolocation by DB-IP – the free country database (CC BY 4.0) used for offline country lookups
httpbin, checkip.amazonaws.com, ifconfig.me, ipinfo.io, wtfismyip.com, ident.me and ip-api.com, used as check targets and for country lookups
Disclaimer
This tool only collects publicly listed proxies and checks whether they work. You are responsible for how you use them – respect the terms of the sites you visit and the laws where you live.
Made in Germany by @maximilianfeix · MIT License · Changelog · Security · Contributing
If proxy-scraper saves you time, a ⭐ helps others find it.
This server cannot be deployed
Maintenance
Related MCP Connectors
Reliable web access for AI agents: smart HTTP, rotating proxies, and full-browser rendering.
Real-time Amazon, WIPO & PACER data for AI agents — 19 tools via the MCP protocol.
Free web search for AI agents. No API key required. Hosted MCP in active development.
Free remote MCP server for fetching public web pages through a rotating proxy pool.
Related MCP Servers
AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI agents to fetch live web content with JavaScript rendering, proxy rotation, and anti-bot evasion.942 npm58MIT- FlicenseNot gradedqualityDmaintenanceEnables AI models to seamlessly integrate with external tools and data sources via the Model Context Protocol, extending functionality without modifying the core model.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and control real, isolated browser profiles with engine-level fingerprinting and per-profile proxies, providing antidetect browsing capabilities through a Model Context Protocol interface.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely interact with local files, live internet search, databases, and development tools through the Model Context Protocol, turning them into autonomous production-ready assistants.5MIT