CapSolver MCP Server
OfficialRelated Servers
Alternatives to CapSolver MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceAn MCP server that lets AI agents solve reCAPTCHA, Cloudflare Turnstile, GeeTest, and image captchas via the local CapSkip solver. It enables autonomous captcha handling without per-solve fees or human intervention.15332 npm10MIT
@curviate/mcpofficial
AlicenseNot gradedqualityCmaintenanceOfficial MCP server for the Curviate API, enabling AI agents to perform LinkedIn actions like profile management, messaging, posting, and advanced search, with Sales Navigator and Recruiter support.MIT- AlicenseNot gradedqualityCmaintenanceA mock-first MCP server for CAPTCHA solving with CapSolver, featuring scoped tools, redacted responses, and bounded polling to detect and solve challenges without leaking credentials.MIT

Thordata MCPofficial
AlicenseNot gradedqualityBmaintenanceOfficial Thordata MCP server. Gives AI assistants real-time web scraping, SERP extraction, and global residential proxy capabilities to access live web data seamlessly.MIT- AlicenseAqualityBmaintenanceEnables MCP clients like Claude and Cursor to solve CAPTCHA and anti-bot challenges — Turnstile, DataDome, Akamai, PerimeterX, Imperva, AWS WAF, FunCaptcha and image OCR — through a single API. Returns tokens, clearance cookies or recognized text, with task creation, polling, cancellation, balance and price lookups.8MIT
- AlicenseAqualityDmaintenanceOfficial MCP server for FormaCV, enabling AI-powered CV formatting, anonymization, tailoring, and ATS push-back from AI agents like Claude Desktop and Cursor.836 npm18MIT
TDQS
Scored across 15 tools
Several tool pairs are functionally indistinguishable: get_account_balance vs get_balance have identical descriptions, wait_for_result vs get_task_result_wait both wait on a task ID, and list_task_types / get_supported_tasks / get_task_parameters / get_task_schema all overlap around task-type discovery. create_task vs get_token also blur together since both launch paid solves, leaving an agent to guess which variant to call.
All names are snake_case and nearly all follow verb_noun (get_*, list_*, create_*, refresh_*), which is highly predictable. Minor deviations like wait_for_result and the awkward get_task_result_wait break the pattern slightly but remain readable.
15 tools is at the upper edge of a well-scoped set for a CAPTCHA-solving service. The problem is that several of those slots are consumed by duplicate aliases (balance, wait, task listing) rather than distinct capabilities, so the count feels inflated relative to actual function.
The lifecycle is largely covered: discovery, schema lookup, docs, solve, poll, wait, request-ID recovery, balance, and user-agent extraction. Gaps remain around task cancellation, listing/history of prior tasks, and explicit feedback/error reporting, but these are workaroundable.