FourA
Web scraping for AI agents. One smart tool fetches any public page and picks the method automatically (direct request, rotating proxy, or full headless browser), getting past anti-bot challenges. Four tools + six prompts, one API key.
https://foura-mcp.run.tools
How to connect
-
Smithery (hosted)
1. Open https://smithery.ai/servers/foura/mcp 2. Click Connect and complete OAuth in your MCP client (Claude, Cursor, VS Code, etc.) 3. MCP endpoint: https://foura-mcp.run.tools
Tools (4)
-
foura_singleSend one HTTP request and return the response. Fastest of the four tools (typically 200ms-2s). Use for static pages, JSON APIs, server-rendered HTML. Set unblocker:true if the target has wire-level anti-bot protection. Switch to foura_proxy if you get blocked - status 403, status 429, captcha page, OR response carries `x-vercel-mitigated: challenge` / `cf-mitigated: challenge` headers, OR body title matches `Vercel Security Checkpoint` / `Just a moment` / `Attention Required` / `We're verifying
-
foura_proxyRoute an HTTP request through FourA's proxy pool with automatic retry across multiple proxies. Per-host proxy rating picks proxies most likely to succeed for the target. Use when foura_single returns 403, captcha, or geo-blocked content. Typical latency 1-5s. The response includes the encoded proxy ID that succeeded ('proxy' field) - reuse it in foura_single.proxy or foura_browser.proxy to pin follow-up requests to the same exit IP, or pass it in ignoreProxies to skip this exit on the next rotat
-
foura_browserLoad a URL in a real browser session. JS runs, DOM renders, cookies come back. 2-10s. Use for SPAs, lazy-loaded content, or JS anti-bot challenges (Cloudflare Turnstile etc.). Prefer foura_single for static HTML; foura_proxy for static pages where your IP is blocked. To rotate the browser's exit IP: call foura_proxy first, pass its returned `proxy` ID into this tool's `proxy` field - the browser exits through that pool IP. Default (no `proxy`) is one fixed container egress. If the target is behi
-
foura_autoGive a URL, get the content back. The default first choice for any page when you just want the data and don't want to decide how to fetch it. Internally it walks a cost-aware ladder - a fast direct request first, then a rotating proxy, then a full browser session - escalating only as far as the target forces it, solving common bot challenges (Cloudflare, and similar) on the way, and cheaply replaying a warm session on repeat calls to the same host. It learns the right settings per host on its ow