rea-captcha
Related Servers
Alternatives to rea-captcha
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA universal browser automation MCP server using Playwright, enabling programmatic control of Chrome with 63 tools for navigation, interaction, media control, and CDP-based diagnostics.6315 npm3MIT
- AlicenseNot gradedqualityBmaintenanceMCP 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.1Apache 2.0
- AlicenseAqualityAmaintenanceMCP 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.5134 PyPI2MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides structured control of a Playwright browser for QA, scraping, diagnostics, and reproducible browser workflows.7,015 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT

Asklear Browser MCPofficial
AlicenseCqualityBmaintenanceA 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.6Apache 2.0
TDQS
Scored across 6 tools
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.
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.
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.
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.