NoneCap
Related Servers
Alternatives to NoneCap
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes the full 2Captcha API surface to Claude Code, enabling solving of 31 captcha types, management tools, and webhook integration for asynchronous solves.5MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates with 2Captcha to solve various CAPTCHA types (image, reCAPTCHA, hCaptcha, etc.) for AI agents via MCP.121 npm-
- FlicenseNot gradedqualityCmaintenanceEnables solving CAPTCHAs in MCP workflows with authorization, bounded attempts, and structured result validation.-
- AlicenseAqualityCmaintenanceEnables AI agents to solve reCAPTCHA v2/v3/Enterprise, Cloudflare Turnstile, DataDome and image captchas during browser or HTTP automation, returning the token, cookie or text the page needs. Failed solves are never billed, and a configurable per-process spend cap limits autonomous spending.464 npmMIT
- AlicenseAqualityAmaintenanceCapMonster Cloud Official MCP server CAPTCHA Solver & bypass reCAPTCHA, Turnstile, DataDome, and other CAPTCHAs.84MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action in the solve lifecycle: start (solve_hcaptcha), poll by id (get_solve), cancel (cancel_solve), list (list_solves), outcome reporting (report_solve_outcome), and account lookup (get_account). The descriptions explicitly resolve the one potential overlap between solve_hcaptcha and get_solve (both can wait) by instructing callers to poll with get_solve rather than re-solving.
Names follow a verb_noun shape (solve_hcaptcha, cancel_solve, list_solves, get_account, report_solve_outcome, get_solve). The only wrinkle is that 'solve' is a verb in solve_hcaptcha but a noun object in cancel_solve/get_solve/report_solve_outcome, a minor inconsistency that remains readable.
Six tools is well-scoped for a captcha-solving service: one per lifecycle operation plus account info. No tool feels redundant or missing from the set.
The surface covers the full solve lifecycle: initiate, poll/retrieve token, cancel, list history, report acceptance, and check credits/quota. There are no obvious dead ends for an agent driving a solve end-to-end.