Skip to main content
Glama

Related Servers

Alternatives to rea-captcha

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      A universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.
      63
      15 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets agents drive your real Chrome browser with existing logins and sessions via an outbound-only WebSocket extension. It exposes Playwright-compatible browser tools for navigation, clicking, typing, and snapshots.
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that drives your real Chrome/Edge/Opera browser through a Chrome extension and DevTools Protocol, preserving logins and session state, and can also perform OS-level mouse and keyboard input behind approval.
      51
      34 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to drive a Playwright-compatible browser (with humanized mouse, keyboard, and scroll behavior, persistent profiles, extensions, and GeoIP-aware proxies) to research the web, automate daily tasks, and run tests, with unchanged upstream @playwright/mcp tools plus two local introspection tools. It installs via npm or Docker and speaks stdio or Streamable HTTP.
      332 npm
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      A local stdio MCP server that drives your Chrome browser through the Asklear extension, offering six browser tools for navigation, observation, clicking, filling, scrolling, and extraction — all operations remain on your machine.
      6
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools map to distinct captcha-handling lifecycle steps (inspect, complete, wait, handoff, resume, analyze), and descriptions clarify their different outcomes. There is minor overlap between inspect, wait, and resume, since all examine the existing browser session's challenge state, but the intended actions differ enough for an agent to choose correctly.

    Naming Consistency5/5

    All tool names follow the same predictable pattern: the captcha_ prefix plus a concise snake_case verb. The convention is applied uniformly with no mixing of styles or casing.

    Tool Count5/5

    Six tools is well-scoped for a captcha-handling server, with each tool covering a meaningful operation in the lifecycle. There are no redundant or trivial tools that would bloat the surface.

    Completeness5/5

    The surface covers the full practical lifecycle: detection via inspect, authorized completion, bounded waiting, human handoff, resumption, and read-only offline analysis. No obvious agent workflow or lifecycle stage appears to be missing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues