CaptchaNo MCP Server
Related Servers
Alternatives to CaptchaNo MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables PraisonAI agents to solve authorized CAPTCHA challenges with a bounded one-attempt budget, structured result validation, and a human-review stop for denied, unsupported, exhausted, or malformed requests.-
- AlicenseNot gradedqualityCmaintenanceEnables solving reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstile, and image captchas through MCP tools. Users pay per solve with prepaid credit and can retrieve results asynchronously.MIT
- FlicenseNot gradedqualityBmaintenanceEnables solving captchas through the createTask/getTaskResult protocol, supporting 19 task types with real browser rendering and anti-bot handling.-
- AlicenseAqualityAmaintenanceEnables AI agents to drive your real, logged-in Chrome browser with existing sessions and cookies, bypassing CAPTCHA and anti-bot measures, with support for multi-session and human-in-the-loop workflows.4058MIT
- FlicenseNot gradedqualityCmaintenanceEnables solving CAPTCHAs in MCP workflows with authorization, bounded attempts, and structured result validation.-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform stealth browser automation and anti-detection web interaction, including session management, humanized interactions, and bypassing anti-bot/WAF protections.MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: solve_captcha performs solving, get_task polls task status, get_balance reads account funds, and list_captcha_types enumerates supported types. The descriptions explicitly delineate when to use each and how they chain together, leaving no room for misselection.
All four names follow a strict verb_noun snake_case pattern (solve_captcha, get_task, get_balance, list_captcha_types). The convention is uniform and predictable throughout.
Four tools is a tight, well-scoped set for a focused captcha-solving service, and each earns its place in the solve/poll/balance/discover workflow. It is slightly lean, with no dedicated cancel or error-report tool, but nothing is redundant.
The surface covers the full lifecycle: discovering supported types and required fields, solving, polling asynchronous tasks, and checking balance/spend limits. Minor gaps exist (no explicit task cancellation or failure-report operation), but these are handled by expiry and free-failed-solve semantics.