Your internet,
extended to your
agents. Not theirs.
freeproxy is an open-source rotating proxy that pools the network access you already pay for — home, work, school, mobile — and serves it back to your AI agents over a private mesh. The web you can reach, your agents can reach. No data-center IPs. No silent throttles. No 403s aimed at the model, not you.
The open web was built on the principle that any user could reach any page.
Then it got gated. Cloudflare challenges. CAPTCHA walls. IP reputation lists. Bot scores.
These systems do not, in fact, block bots. They block users without enough trust score — and AI providers, sharing a tiny pool of data-center IPs, have none.
You, however, have plenty. Your phone, your home connection, your laptop on the office wifi — they all see the open web just fine.
It is your right to extend that access to the agents you run.
Pool the connections you already have. Rotate them through a private mesh.
Add nodes from anywhere you have internet.
Run the agent on a laptop, a phone, a Raspberry Pi at home, a spare VPS. Every node joins your private mesh over a Tailscale-style WireGuard tunnel. No port forwarding, no firewall surgery.
Requests are dispatched across nodes per a policy you control.
Round-robin. Sticky-by-domain. Geo-pin. Exclude work-vpn from social media. The rota engine handles failover, health checks, and retries — your agent just sees a single proxy endpoint.
Point your agent at a single endpoint.
HTTP/SOCKS5 proxy on localhost:7777, or speak MCP directly. Works with Claude Desktop, Cursor, Cline, custom Python — anything that can use a proxy or call a tool.
Inspect every hop. Revoke any node, instantly.
The dashboard shows live traffic per node, per agent, per domain. Block, throttle, or rotate any node on demand. Your network — your rules. Logs stay local; nothing phones home.
Nine guarantees. One binary.
Open source. Self-hostable.
Apache 2.0. Audit the binary, fork the protocol, run the whole stack on your own metal. No mandatory cloud.
Free as in freedom.
Not a freemium tier waiting to be metered. The right framing is civic, not commercial: your access, extended.
Use the access you already pay for.
Your home fiber. The phone plan you stopped using. The cafe wifi. Existing connections become a resource for your agents.
Bypass blocks aimed at AI providers.
Most provider-side 403s are reputation, not policy. Routing through your own residential IPs makes your agent look like… you.
First-class MCP integration.
Native Model Context Protocol server. Tools for fetch, crawl, authed_session, and explicit choose_node for policy-aware agents.
Tailscale + Cloudflare-style mesh.
WireGuard under the hood. NAT-traversed. End-to-end encrypted. Builds on the patterns that already work for private networks.
Your traffic stays yours.
No central proxy. No shared exit pool. No telemetry. Logs are local-first; export only if you say so.
Multi-device by design.
One control plane, many trust zones. Tag nodes home, work, school, mobile and route by tag.
Agent-first, not browser-first.
Designed for headless workloads: long-lived sessions, structured retries, deterministic IP selection, programmable from the agent side.
A dashboard that treats your nodes like infrastructure, not contacts.
Overview
5 nodes online · 3 agents connected · last incident 14d ago
Speak MCP natively — or any HTTP/SOCKS5 client works.
{
"mcpServers": {
"freeproxy": {
"command": "freeproxy",
"args": ["mcp", "--policy=sticky-by-domain"],
"env": {
"FP_KEY": "fp_live_••••••••••••"
}
}
}
}
// exposes tools: fetch, crawl, choose_node,
// authed_session, list_nodes
# http proxy on localhost:7777 curl -x http://127.0.0.1:7777 \ -H "X-FP-Policy: round-robin" \ https://example.com
from freeproxy import Rota rota = Rota(policy="sticky-by-domain") with rota.session(tags=["home", "mobile"]) as s: r = s.get("https://arxiv.org") assert r.status_code == 200 print(rota.last_node) # 'home-fiber'
One config. Five tools. Zero lock-in.
Drop the snippet into Claude Desktop, Cursor, Cline, or any MCP-aware client. Your agent gains a verb-level model of your network — not just a proxy URL.
- ✓fetch — single request with rota policyauto retry, auto rotate on 429/403
- ✓crawl — multi-page, multi-noderespects robots.txt, rate-limits per-domain
- ✓authed_session — sticky cookie jarpinned to one node for login flows
- ✓choose_node — explicit selectionby tag, geo, latency, or name
- ✓list_nodes — introspect the rotaso the agent knows what's available