ai.foura/mcp

Route 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 rotation. Escalate to foura_browser if all proxies fail or the page needs JavaScript rendering. When the trigger is a tier-1 WAF challenge (Vercel Security Checkpoint, Cloudflare 'Just a moment', Akamai Bot Manager), set maxTries to 25-30 - the default 5 will usually be too low for these targets. Distinguish from country / ASN allowlist denials (country-licensed bookmakers, government sites): there rotation never helps regardless of maxTries - after ~30 failed attempts on the same block, stop climbing and pivot strategy instead.

Send 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 your browser`. For these tier-1 WAF challenges call foura_proxy with maxTries:25-30 (the default 5 is sized for lightly-blocked sites). On success, chain the returned proxy ID into foura_browser.proxy if the page also needs JavaScript to render.

Load 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 behind a tier-1 WAF challenge (Vercel / Cloudflare / Akamai), calling this tool directly will usually still capture the challenge page rather than the post-challenge content - the snapshot fires before the challenge's deferred reload completes. Correct chain: call foura_proxy first with maxTries:25-30 against the same URL → take the returned proxy base36 ID → pass it into this tool's `proxy` field. The browser then exits through the IP that already cleared the challenge for this target. By default the browser actively solves an anti-bot / captcha challenge it meets along the way (the `unblocker` flag, default true); set `unblocker:false` to skip solving and return the page exactly as it loads, challenge page included.

Give 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 own, so there are no maxTries / pool / retry knobs to tune. Pass `validate` (a substring the real page must contain) on protected targets so it can tell a real page from a challenge page. The response includes a `meta` trace (which rung delivered, credits spent) and, by default, the winning `session` ({proxy, cookies, userAgent}) so you can replay it through foura_single / foura_proxy afterwards. Use one of the lower-level tools instead only when you need explicit control: foura_single for a specific raw HTTP request, foura_proxy to drive the rotation/exit yourself, foura_browser for a scripted browser session.