Skip to main content
Glama

Related Servers

Alternatives to CapSolver MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      An 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.
      15
      332 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Official 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Official Thordata MCP server. Gives AI assistants real-time web scraping, SERP extraction, and global residential proxy capabilities to access live web data seamlessly.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      8
      MIT

    TDQS

    B3.1/5.0

    Scored across 15 tools

    Disambiguation2/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues