Twocaptcha

@twocaptcha I need to solve a reCAPTCHA v2 for https://example.com/login with site key 6Le-wvkSAAAAAPBMRTvw0Q4Muexq9bi0DJwx_mJ-

Task created successfully with ID 72457362895. The reCAPTCHA v2 challenge has been queued for solving by Twocaptcha's worker network. Typical solve time is 10-30 seconds depending on current queue load. Once solved, you'll receive a response token that can be submitted with your login form. Check task status using the returned task ID to retrieve the solution token.

This example shows the primary workflow: submitting a CAPTCHA challenge and receiving a task ID. You'll need to poll separately for the solution (not shown here). Requires valid API credits in your Twocaptcha account. Response times vary with service load—budget 30-60 seconds for complex CAPTCHAs during peak hours.

@twocaptcha Create a task to solve this hCaptcha with site key a5f74b19-9e45-40e0-b45d-47ff91b7a6c2 on https://discord.com/register

hCaptcha task initiated with ID 72457363012. The challenge parameters have been forwarded to available solvers in the Twocaptcha network. hCaptcha typically requires 15-45 seconds to solve. You'll receive a token string upon completion that must be included in your registration request's h-captcha-response field within 2 minutes before it expires.

Demonstrates hCaptcha support, a common alternative to reCAPTCHA. The MCP handles task creation but doesn't automatically poll for completion—you'll need follow-up logic to retrieve the solved token. Be aware that solved tokens have short expiration windows (typically 120 seconds), so coordinate your form submission timing accordingly.

@twocaptcha I'm hitting rate limits on an API protected by Cloudflare Turnstile. Can you solve the challenge for https://api.example.com with site key 0x4AAAAAAADnPIDROzbs0Wjw?

Cloudflare Turnstile task created with ID 72457363089. This challenge type typically solves in 20-40 seconds. Turnstile tokens are single-use and domain-locked, so the returned solution will only work for api.example.com requests. Once you receive the solved token, include it in your API request's cf-turnstile-response header or form field as specified by the API's documentation.

Shows support for Cloudflare's newer Turnstile system, increasingly common on developer APIs. Important limitation: Turnstile tokens are bound to the specific domain and often the IP address that requested them. If your automation runs from multiple IPs or the API enforces strict fingerprinting, you may need to solve a fresh challenge per request. Costs 1-2 credits per solve.

When this MCP saves QA cycles on protected staging environments

A 6-person engineering team runs nightly Playwright tests against a staging environment that sits behind Cloudflare's Turnstile CAPTCHA. Without automated solving, QA engineers manually complete CAPTCHAs each morning before tests can proceed, burning 20-30 minutes daily. The Twocaptcha MCP solves this by letting your test suite programmatically request CAPTCHA solutions via a single API key—no per-user credentials, no browser automation hacks. The trade-off: each solve costs $0.50-$2.99 depending on CAPTCHA type, so a 50-test suite hitting 10 CAPTCHAs nightly runs $150-$900/month. This math works when your QA team's hourly rate exceeds the solve cost, typically at 4+ engineers. If your staging environment can whitelist CI IPs instead, do that first—it's free and faster.

When this MCP unblocks price monitoring at small scale

A 3-person e-commerce ops team monitors competitor pricing across 40 retailer sites twice daily to adjust their own catalog. Half those sites deploy reCAPTCHA v2 or hCaptcha after the first few requests, killing their Python scraper. The Twocaptcha MCP handles this by offloading CAPTCHA solving to human workers—your scraper pauses, submits the challenge via the MCP's single tool, waits 10-30 seconds for a solution, then continues. At 80 CAPTCHAs daily and $1.50 average cost, that's $3,600/year versus hiring a part-time analyst at $25k. The boundary: if you're scraping 500+ pages daily, solve costs balloon past $20k/year and you need a residential proxy network instead. For sub-100-page monitoring, this MCP is the pragmatic unlock.

When this MCP doesn't fit internal support tooling

A 10-person SaaS support team fields 30 account recovery requests daily, each requiring a CAPTCHA verification before password reset. The team considers automating this via the Twocaptcha MCP to speed up ticket resolution. This is the wrong call. The MCP's single tool creates tasks for external CAPTCHA solving—it's built for scenarios where your system encounters third-party CAPTCHAs, not for solving CAPTCHAs you control. If you own the CAPTCHA (via Google reCAPTCHA Enterprise or similar), you already have server-side verification APIs that skip the visual challenge entirely for trusted contexts. Use those. The Twocaptcha MCP only makes sense when you're interacting with someone else's CAPTCHA and have no backend access. For internal workflows, it adds cost and latency with no benefit.