CaptchaNo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPTCHANO_WAIT | No | Optional number of seconds the API blocks on each solve request before polling. Default is 45, max 120. | |
| CAPTCHANO_API_KEY | Yes | Your CaptchaNo API key (starts with cn-). Required to authenticate and bill solves. | |
| CAPTCHANO_API_BASE | No | Optional API base URL. Default is https://api.captchano.com. | |
| CAPTCHANO_LOG_LEVEL | No | Optional log level: debug, info, warn, error, or silent. Default is info. | |
| CAPTCHANO_TOOL_TIMEOUT | No | Optional max seconds one solve_captcha call takes before returning a resumable solving result. Default is 50. | |
| CAPTCHANO_MAX_SPEND_USD | No | Optional spend ceiling for this server process, in USD. Default is unlimited. | |
| CAPTCHANO_MCP_HTTP_TOKEN | No | Optional bearer token required on /mcp in --http mode. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| solve_captchaA | Solve a captcha on a web page and return the token / cookie / text needed to pass it. Use when an authorised browser or HTTP automation is blocked by reCAPTCHA (v2, v3, Enterprise), Cloudflare Turnstile, DataDome or an image captcha. Before calling: identify the type and read the sitekey from the page (call list_captcha_types for where to find it and which fields each type needs). Required: recaptcha_* and turnstile → url + sitekey; datadome → url + challengeUrl + proxy; image → body (base64). Waits for the result (up to ~50 s by default, polling automatically). If it is still solving at the end, it returns the task id: call get_task with it instead of solving again. Each successful solve is billed to the CaptchaNo balance (cost is returned); failed solves are free. Do not call repeatedly for the same captcha: one token is valid for one submission and expires in about 2 minutes, so use it right away. |
| get_taskA | Fetch the current status and solution of a task created by solve_captcha. Use when solve_captcha returned status "solving" (call again every ~5 s), or to re-read a solution you already received. Results are kept for 10 minutes. Free and read-only. |
| get_balanceA | Return the CaptchaNo account balance (USD) and how much this MCP server has spent in the current session against its optional CAPTCHANO_MAX_SPEND_USD limit. Use before a large batch of solves, or after an insufficient_balance error. Free and read-only. |
| list_captcha_typesA | List every captcha type solve_captcha supports, with its required and optional fields, which solution field it returns, and how to find the sitekey (or other inputs) on the page. Use when you are unsure which type a page uses or which arguments to pass. Static, free, no network call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: solve_captcha performs solving, get_task polls task status, get_balance reads account funds, and list_captcha_types enumerates supported types. The descriptions explicitly delineate when to use each and how they chain together, leaving no room for misselection.
All four names follow a strict verb_noun snake_case pattern (solve_captcha, get_task, get_balance, list_captcha_types). The convention is uniform and predictable throughout.
Four tools is a tight, well-scoped set for a focused captcha-solving service, and each earns its place in the solve/poll/balance/discover workflow. It is slightly lean, with no dedicated cancel or error-report tool, but nothing is redundant.
The surface covers the full lifecycle: discovering supported types and required fields, solving, polling asynchronous tasks, and checking balance/spend limits. Minor gaps exist (no explicit task cancellation or failure-report operation), but these are handled by expiry and free-failed-solve semantics.