Skip to main content
Glama

CapSkip MCP Server — Unlimited Captcha Solver for AI Agents

Node.js 18+ License: MIT Tests npm

A captcha solver MCP server that lets AI agents solve reCAPTCHA, Cloudflare Turnstile, GeeTest, ALTCHA, Capy Puzzle, CaptchaFox, Friendly Captcha, AWS WAF, DataDome, hCaptcha, MTCaptcha, Yandex SmartCaptcha and image captchas instead of stalling on them.

Works with Claude Desktop, Claude Code, Cursor, VS Code, and any Model Context Protocol client. Powered by CapSkip — a local captcha solver that runs on your own machine, licensed once rather than billed per solve.

npx -y capskip-mcp

What this solves

An AI agent driving a browser hits a captcha and stops. This server gives it fifteen tools so it can read the sitekey, solve the challenge, and carry on — without a human stepping in and without a per-solve API bill.

CapSkip runs as a desktop app exposing a captcha-solving HTTP API on 127.0.0.1:8080. capskip-mcp is a thin translation layer over that API: the fifth official CapSkip client, alongside the Python, Node.js, PHP and .NET SDKs.

Related MCP server: ma-browser

Supported captcha types

Captcha

Tool

Notes

reCAPTCHA v2 solver (checkbox)

capskip_solve_recaptcha

Returns a g-recaptcha-response token

reCAPTCHA v2 invisible solver

capskip_solve_recaptcha

Pass invisible: true

reCAPTCHA Enterprise solver

capskip_solve_recaptcha

Pass enterprise: true, works with v2 and v3

reCAPTCHA v3 solver

capskip_solve_recaptcha

Pass version: "v3" and the page's action

Cloudflare Turnstile solver

capskip_solve_turnstile

Widget and interstitial challenge pages

GeeTest v3 solver

capskip_solve_geetest

Slide puzzle; returns challenge/validate/seccode

GeeTest v4 solver

capskip_solve_geetest_v4

Every v4 challenge type; needs only the captcha_id, returns the five values the site verifies

ALTCHA solver

capskip_solve_altcha

Proof-of-work; returns the token for the altcha field

Capy Puzzle solver

capskip_solve_capy

Slide puzzle; returns three form values, not a token

CaptchaFox solver

capskip_solve_captchafox

Returns the token for the cf-captcha-response field

Friendly Captcha solver

capskip_solve_friendly_captcha

Proof-of-work; say which version (v1 or v2)

AWS WAF CAPTCHA solver (Amazon WAF)

capskip_solve_amazon_waf

Challenge page or widget; returns the voucher pair, not the cookie

DataDome solver (slider and device check)

capskip_solve_datadome

Returns the datadome cookie, tied to one IP and one User-Agent

hCaptcha solver (checkbox, invisible and Enterprise)

capskip_solve_hcaptcha

Returns the token for h-captcha-response; pass invisible: true or the Enterprise data when the page needs them

MTCaptcha solver (text captcha)

capskip_solve_mtcaptcha

Returns the token for mtcaptcha-verifiedtoken; the sitekey starts with MTPublic-

Yandex SmartCaptcha solver

capskip_solve_yandex_smart

Returns the token for smart-token; the sitekey usually starts with ysc1_

Image captcha solver (text/OCR)

capskip_solve_image_captcha

File path, URL, data URI, or base64

Not supported: FunCaptcha/Arkose. There is no tool for it. hCaptcha and reCAPTCHA both carry a data-sitekey, so check the widget before choosing a tool: class="h-captcha" or a js.hcaptcha.com script takes capskip_solve_hcaptcha, class="g-recaptcha" takes capskip_solve_recaptcha.

Try them against live widgets on the captcha demo pages.


Quick start (5 minutes)

1. Install the CapSkip captcha solver

Download and run the CapSkip desktop app from the download page. Leave it running in the background.

In CapSkip settings, note the API port (default 8080) and API key (optional — if key validation is disabled, any string works).

2. Add capskip-mcp to your MCP client

No install step — npx fetches and runs it on demand.

{
  "mcpServers": {
    "capskip": {
      "command": "npx",
      "args": ["-y", "capskip-mcp"],
      "env": {
        "CAPSKIP_HOST": "127.0.0.1",
        "CAPSKIP_PORT": "8080",
        "CAPSKIP_API_KEY": "capskip"
      }
    }
  }
}

MCP client

Config file

Example

Claude Desktop

claude_desktop_config.json

examples/claude-desktop.json

Claude Code

claude mcp add (CLI)

examples/claude-code.md

Cursor

.cursor/mcp.json

examples/cursor.json

VS Code

.vscode/mcp.json

examples/vscode.json

3. Restart your client

It should list fifteen tools, all prefixed capskip_.

4. Ask your agent to solve a captcha

"Call capskip_status to confirm CapSkip is running, then solve the reCAPTCHA on this page and submit the form."

The agent reads the sitekey off the page, calls capskip_solve_recaptcha, and places the returned token in the page's g-recaptcha-response field.


Why a local captcha solver

Cloud captcha APIs bill per solve, so an agent that retries is an agent that costs money, and every page URL and sitekey you solve leaves your network.

CapSkip runs on your machine:

  • Unlimited captcha solving — licensed once, no per-solve fees, no credit balance to top up

  • Local by default — the solver talks to 127.0.0.1; nothing is proxied through a third-party queue

  • No rate limit per key — throughput is bounded by your machine, not a vendor's plan tier

  • Fast — image captchas return in well under a second; typical reCAPTCHA v2 solves land in 30–45s

Using an existing 2captcha or Anti-Captcha integration?

CapSkip exposes the familiar in.php / res.php endpoints, so it works as a 2captcha API alternative — point your existing client at 127.0.0.1:8080 and keep your code. See the migration notes. This MCP server is the equivalent for AI agents rather than scripts.


Tools

Tool

Purpose

Required arguments

capskip_status

Check whether the CapSkip desktop app is running and reachable

none

capskip_solve_image_captcha

Read the text out of a distorted-text captcha image

image

capskip_solve_recaptcha

Solve reCAPTCHA v2 or v3, including invisible and Enterprise

sitekey, url

capskip_solve_turnstile

Solve a Cloudflare Turnstile widget or challenge page

sitekey, url

capskip_solve_geetest

Solve a GeeTest v3 slide-puzzle captcha

gt, challenge, url

capskip_solve_altcha

Solve an ALTCHA proof-of-work challenge

url, and one of challenge_url / challenge_json

capskip_solve_capy

Solve a Capy Puzzle captcha

sitekey, url

capskip_solve_captchafox

Solve a CaptchaFox challenge

sitekey, url

capskip_solve_friendly_captcha

Solve a Friendly Captcha proof-of-work challenge

sitekey, url

capskip_solve_amazon_waf

Solve an AWS WAF (Amazon WAF) CAPTCHA

sitekey, url

capskip_solve_datadome

Pass a DataDome challenge and get its cookie

captcha_url, url

capskip_solve_hcaptcha

Solve an hCaptcha widget (checkbox, invisible, Enterprise)

sitekey, url

capskip_solve_mtcaptcha

Solve an MTCaptcha text captcha

sitekey, url

capskip_solve_geetest_v4

Solve a GeeTest v4 captcha

captcha_id, url

capskip_solve_yandex_smart

Solve a Yandex SmartCaptcha

sitekey, url

There is no min_score parameter on capskip_solve_recaptcha. reCAPTCHA v3 scores are assigned by Google from signals no solver has access to — local or cloud, none can raise a score after the fact. A min_score option would promise control that does not exist, so it is deliberately left out. Passing it anyway is rejected as an unrecognized key, not silently ignored.

Full parameter tables and worked examples: API Reference.

Guide

Description

Tutorial

Every captcha type — how to recognize it, what to read off the page, what call to make, where the answer goes

Getting Started

Full setup: CapSkip app, client config, first solve

API Reference

Every tool, parameter, and return shape

Troubleshooting

Connection errors, timeouts, rejected tokens


Browser automation: Playwright, Puppeteer and Selenium

This server solves the captcha and hands back a token; your agent's existing browser tooling does the driving. The pattern is the same whichever you use:

  1. Read the sitekey from the page (data-sitekey, or the widget's config object).

  2. Call the matching capskip_solve_* tool with that sitekey and the page URL.

  3. Write the token into the response field and submit.

// The agent does this via its browser tool after capskip_solve_recaptcha returns
document.querySelector('#g-recaptcha-response').value = TOKEN;

For non-agent scripts, use the language SDKs directly — see the Playwright, Puppeteer and Selenium guides.


Configuration

Variable

Default

Meaning

CAPSKIP_API_KEY

capskip

Any string when key validation is off

CAPSKIP_HOST

127.0.0.1

CapSkip host

CAPSKIP_PORT

8080

API port from CapSkip settings

CAPSKIP_TIMEOUT

120

Default timeout for the image / ALTCHA / Capy / MTCaptcha tools, seconds

CAPSKIP_RECAPTCHA_TIMEOUT

300

Default timeout for the reCAPTCHA / Turnstile / GeeTest / CaptchaFox / Friendly Captcha / AWS WAF / DataDome / hCaptcha / GeeTest v4 / Yandex SmartCaptcha tools, seconds

ALTCHA and Capy use CAPSKIP_TIMEOUT, not the reCAPTCHA one — neither is a browser solve. ALTCHA is CPU proof-of-work measured in milliseconds; a Capy solve is one HTTP fetch plus pixel math, held back to roughly two seconds because Capy refuses answers that arrive faster than a human could have produced them.

Friendly Captcha is proof-of-work too but takes the longer timeout: the service sets the difficulty per request, and v2 always solves in a browser.

| CAPSKIP_POLLING_INTERVAL | 5 | Max seconds between polls |

CLI flags override environment variables, which override the defaults:

capskip-mcp --api-key <key> --host <host> --port <port> --timeout <seconds> \
            --recaptcha-timeout <seconds> --polling-interval <seconds>

An invalid value (non-numeric port, port outside 1–65535, a negative or out-of-range timeout, an unknown flag) fails at startup naming the offending flag or variable, rather than surfacing later as a confusing solve failure.


What you get back

Every solve tool returns a human-readable text block and structuredContent matching its declared output schema:

{
  "captchaId": "12345",
  "code": "03AGdBq26f...",
  "solveSeconds": 11.8
}
  • capskip_solve_turnstile adds userAgent. Submit the token with this exact User-Agent — Cloudflare rejects a token replayed under a different one.

  • capskip_solve_geetest adds challenge, validate and seccode, to post back exactly as the site's own front-end would; code keeps the raw JSON string CapSkip returns.

  • capskip_solve_altcha adds token, the base64 payload to submit verbatim in the site's form field named altcha, and number, the counter that solved the challenge; code holds the same string as token.

  • capskip_solve_capy adds captchakey, challengekey and answer — not a token. All three go into the target form, in fields named capy_captchakey, capy_challengekey and capy_answer; code keeps the raw answer as JSON. The answer is the drag path the widget would have recorded, so submit it verbatim, and promptly: the challenge key is single-use and short-lived.

  • capskip_solve_captchafox adds token, for the form field named cf-captcha-response, and userAgent when the solve reported one — the UA the browser minted the token under, not any you sent. Submit under that one.

  • capskip_solve_friendly_captcha adds token. The field it goes into differs by version: frc-captcha-solution on v1, frc-captcha-response on v2. The text reply names the right one for the version that was solved.

  • capskip_solve_amazon_waf adds captcha_voucher and existing_token — not the cookie. The two only work as a pair: POST them as JSON to the voucher endpoint in the same folder as the page's challenge.js, and the response's token is the aws-waf-token cookie. The text reply spells out that step, with the exact URL when you passed challenge_script. Exchange the pair promptly rather than storing it.

  • capskip_solve_datadome adds cookie (the datadome=... pair for a Cookie header; code keeps the full Set-Cookie value), userAgent (the one the cookie was earned with) and, only when you passed no proxy and CapSkip solved through its own DataDome proxy list, proxy as host:port. The cookie belongs to one IP and one User-Agent: repeat the request with that User-Agent, from the same address — through the proxy you passed, through the reported proxy, or from this machine when neither applies. The text reply spells out which.

  • capskip_solve_hcaptcha adds token, for the hidden h-captcha-response field (and g-recaptcha-response, if the form has one), respKey (the second value hCaptcha hands the widget; most sites never read it, and it can be empty) and userAgent, the one the token was earned with. Submit the form with that User-Agent, promptly: tokens are single use and expire about two minutes after they are issued.

  • capskip_solve_mtcaptcha adds token, v1(...), for the hidden mtcaptcha-verifiedtoken field.

  • capskip_solve_geetest_v4 adds captcha_id, lot_number, pass_token, gen_time and captcha_output, the five values the site verifies, to send under those same names; code keeps them as the raw JSON string. isOffline: true appears only when GeeTest could not be reached and passed the widget offline.

  • capskip_solve_yandex_smart adds token, for the hidden smart-token field. It is valid for five minutes and can be checked once.

Long solves emit MCP progress notifications, so a 45-second reCAPTCHA does not trip your client's tool-call timeout.


Errors

Every tool call returns isError: true with readable text on failure — never a stack trace or a bare protocol error — so the model can read the message and correct course.

Cause

Message

CapSkip unreachable

CapSkip is not reachable at <host>:<port>. Confirm the CapSkip desktop app is running and that its API port matches this setting (override with CAPSKIP_HOST / CAPSKIP_PORT).

Another process holds the port

Something is listening on <host>:<port> but it did not answer as CapSkip (HTTP <code>). Check the API port in CapSkip settings, and that nothing else has taken that port — override with CAPSKIP_HOST / CAPSKIP_PORT.

Wrong API key

CapSkip rejected the API key. Set CAPSKIP_API_KEY to the key shown in CapSkip settings, or disable key validation there.

ERROR_CAPTCHA_UNSOLVABLE

CapSkip could not solve this captcha. Fetch a fresh sitekey or challenge from the page and try again.

ERROR_GOOGLEKEY

CapSkip rejected the sitekey. Re-read data-sitekey from the page and retry.

ERROR_PAGEURL

CapSkip rejected the url. Pass the full page URL, including its scheme.

ERROR_INVALID_IMAGE

CapSkip could not read that image. Check the file is a valid, uncorrupted PNG or JPEG.

ERROR_BAD_PARAMETERS

CapSkip rejected the parameters for this captcha type. Re-check the values supplied.

Solve exceeded timeout

The solve did not finish within <elapsed>s. Raise the timeout parameter, or check CapSkip's own queue. — plus the captcha id when one was assigned

Unknown or misspelled parameter

Rejected before the call reaches CapSkip, naming the key, e.g. Unrecognized key: "min_score"

See Troubleshooting for fixes.


FAQ

Can AI agents solve captchas?

Not on their own — a model cannot produce a valid reCAPTCHA or Turnstile token. It needs a solver. This MCP server connects your agent to CapSkip so it can request a real token and continue the task.

Does this work with Claude, Cursor and VS Code?

Yes. It is a standard MCP stdio server, so it works with any Model Context Protocol client, including Claude Desktop, Claude Code, Cursor and VS Code. Config examples for each are in examples/.

Is there a free captcha solver here?

The MCP server is MIT-licensed and free. It requires the CapSkip desktop app, which is licensed once and then solves without per-solve charges — unlike cloud APIs that bill per captcha.

Which captchas can it solve?

reCAPTCHA v2 (checkbox and invisible), reCAPTCHA v3, reCAPTCHA Enterprise, Cloudflare Turnstile, GeeTest v3 and v4, ALTCHA, Capy Puzzle, CaptchaFox, Friendly Captcha, AWS WAF (Amazon WAF), DataDome, hCaptcha (including invisible and Enterprise), MTCaptcha, Yandex SmartCaptcha, and image/text captchas. FunCaptcha/Arkose is not supported.

Why does my reCAPTCHA v3 token get a low score?

Google assigns v3 scores from signals such as IP reputation and browsing history. A solver returns a valid token, but cannot raise the score. If a site enforces a high threshold, solve from a cleaner IP — a proxy is supported on every solve tool except the image one (for ALTCHA it applies only to the challenge fetch, and for Capy only to the puzzle-image fetch).

Does it need my captcha to be on a public page?

Yes for widget captchas — CapSkip loads the page URL you pass. Image captchas need only the image, which can be a local file.

Can I use it with Playwright or Puppeteer?

Yes. The agent drives the browser; this server supplies the token. See the browser automation section.


Requirements

  • Node.js 18 or newer

  • The CapSkip desktop app installed and running (download)

License

MIT — see LICENSE.

Available Tools

15 tools
capskip_solve_altchaSolve ALTCHAA

Solve an ALTCHA proof-of-work challenge. ALTCHA is not a recognition captcha — there is nothing to read; the client brute-forces a number that satisfies a challenge, so a solve is deterministic and takes milliseconds. Give it either challenge_url (the endpoint the fetches from, which CapSkip will fetch) or challenge_json (the challenge document itself). Returns a token to put in the page's form field named altcha, verbatim. IMPORTANT: challenges expire quickly — some sites inside two minutes — so read the challenge immediately before calling and submit the token promptly. An expired challenge is rejected with a bare "verification failed" that looks exactly like a wrong answer.

Inputs: url (required), proxy, timeout, challenge_url, +1 more. Returns: code, token, number, captchaId, +1 more

capskip_solve_amazon_wafSolve AWS WAF CAPTCHAA

Solve an AWS WAF (Amazon WAF) CAPTCHA — the image-grid or toy-car puzzle Amazon's firewall shows on a 405 challenge page (window.gokuProps plus challenge.js/captcha.js from an awswaf.com host) or in a JS-API widget (jsapi.js plus AwsWafCaptcha.renderCaptcha). Only sitekey and url are required. IMPORTANT: the answer is NOT the cookie. It is a pair, captcha_voucher and existing_token, which only work together: POST them as JSON {"captcha_voucher":…,"existing_token":…} to the voucher endpoint in the same folder as the page's challenge.js (replace 'challenge.js' with 'voucher'), and the response's token field is the aws-waf-token. Send that as the aws-waf-token cookie on the protected domain (some widget pages use an x-aws-waf-token header instead) and repeat the request. Exchange the pair immediately rather than storing it.

Inputs: url (required), sitekey (required), iv, proxy, +5 more. Returns: code, captchaId, solveSeconds, existing_token, +1 more

capskip_solve_captchafoxSolve CaptchaFoxA

Solve a CaptchaFox challenge. CaptchaFox scores the browser itself rather than asking the visitor to read anything, so most solves draw no puzzle at all. Returns a token to put in the form field named 'cf-captcha-response', verbatim — it is verified server side against the session that produced it, so any edit invalidates it. IMPORTANT: the url must be the page the widget actually runs on. CaptchaFox checks it against the domains the key is registered for and refuses a mismatch permanently, not intermittently — so a sitekey that fails immediately and consistently usually means the wrong page URL, not a bad key. The result also carries the User-Agent the token was minted under; submit under that one, not your own.

Inputs: url (required), sitekey (required), proxy, timeout, +1 more. Returns: code, token, captchaId, userAgent, +1 more

capskip_solve_capySolve Capy PuzzleA

Solve a Capy Puzzle captcha — a slide puzzle where a piece is dragged into a hole cut out of a photograph. IMPORTANT: unlike every other captcha tool here, the answer is NOT a single token. It is three values — captchakey, challengekey and answer — which all go into the target form, in fields named 'capy_captchakey', 'capy_challengekey' and 'capy_answer'. Submit the answer verbatim: it is the drag path the widget would have recorded, so trimming or re-encoding it invalidates the solve. The challenge key is single-use and short-lived, so submit promptly rather than caching the three values. A solve takes about two seconds — Capy refuses answers that arrive faster than a human could have produced them, so CapSkip holds the result back deliberately.

Inputs: url (required), sitekey (required), proxy, timeout, +1 more. Returns: code, answer, respKey, captchaId, +3 more

capskip_solve_datadomeSolve DataDomeA

Pass a DataDome challenge — the block page (HTTP 403, sometimes 401) a DataDome-protected site returns instead of its content, with a slider (/captcha/) or a device check (/interstitial/) loaded from geo.captcha-delivery.com — and get the datadome cookie. Requires captcha_url and url. IMPORTANT: the cookie belongs to ONE IP address and ONE User-Agent. Repeat the request with the returned cookie as the Cookie header, the returned userAgent as the User-Agent, and from the same IP: through the proxy you passed, or — when the result carries proxy — through that proxy, which CapSkip picked from its own DataDome proxy list because you passed none. Any other address or User-Agent gets the block page again.

Inputs: url (required), captcha_url (required), proxy, timeout, +1 more. Returns: code, proxy, cookie, captchaId, +2 more

capskip_solve_friendly_captchaSolve Friendly CaptchaA

Solve a Friendly Captcha proof-of-work challenge. Nothing is shown on screen — the widget does arithmetic instead of asking the visitor to do anything. IMPORTANT: two entirely different protocols ship under this one name, sharing a brand and a sitekey namespace and nothing else, and a sitekey does not tell you which a site uses. Send version (v1 or v2), or send module_script and let CapSkip read the version off the build the site loads. Solving the wrong one returns a well-formed token the site rejects, with nothing to indicate the version was the problem. The form field also differs by version: v1 uses 'frc-captcha-solution', v2 uses 'frc-captcha-response'. Solve time is not a constant — the service sets the difficulty per request — so budget for that rather than assuming a fixed duration.

Inputs: url (required), sitekey (required), proxy, timeout, +4 more. Returns: code, token, captchaId, solveSeconds

capskip_solve_geetestSolve GeeTest v3A

Solve a GeeTest v3 slide-puzzle captcha. Returns geetest_challenge, geetest_validate, and geetest_seccode to post back exactly as the site's own front-end would. IMPORTANT: the challenge value is single-use and expires in roughly a minute, so fetch gt and challenge from the page immediately before calling. A stale challenge is the most common failure.

Inputs: gt (required), url (required), challenge (required), proxy, +2 more. Returns: code, seccode, validate, captchaId, +2 more

capskip_solve_geetest_v4Solve GeeTest v4A

Solve a GeeTest v4 captcha (a page loading static.geetest.com/v4/gt4.js and calling initGeetest4) and get the five values the site verifies: captcha_id, lot_number, pass_token, gen_time and captcha_output. Requires captcha_id and url only; unlike GeeTest v3 there is no challenge to fetch first. Every v4 challenge type is answered (slide, icon, nine-grid, match and the rest). Send the five values under those same names in the request the page's own submit makes. For GeeTest v3 (gt + challenge) use capskip_solve_geetest instead.

Inputs: url (required), captcha_id (required), proxy, timeout, +1 more. Returns: code, gen_time, captchaId, isOffline, +5 more

capskip_solve_hcaptchaSolve hCaptchaA

Solve an hCaptcha widget — or a js.hcaptcha.com script on the page — and get its token. Checkbox, invisible and hCaptcha Enterprise widgets all use this tool. Requires sitekey and url. Put the returned token in the form's hidden h-captcha-response field and in g-recaptcha-response if the form has one, or call the widget's data-callback with it, then submit with the returned User-Agent. Tokens are single use and expire about two minutes after they are issued, so submit promptly. Do not use capskip_solve_recaptcha for hCaptcha: both carry a data-sitekey, but they are different widgets.

Inputs: url (required), sitekey (required), data, proxy, +3 more. Returns: code, token, respKey, captchaId, +2 more

capskip_solve_image_captchaSolve an image captchaA

Read the text out of a distorted-text captcha image. Returns the recognized text, which you type into the page's captcha field. Proxies are not supported for image captchas.

Inputs: image (required), timeout. Returns: code, captchaId, solveSeconds

capskip_solve_mtcaptchaSolve MTCaptchaA

Solve an MTCaptcha text captcha — a widget configured by a mtcaptchaConfig object, or an iframe from service.mtcaptcha.com — and get its token. Requires sitekey (starts with 'MTPublic-') and url; pass action too when mtcaptchaConfig sets one. You do not need to read or type the characters in the picture. Put the returned token, which starts with v1(, in the form's hidden mtcaptcha-verifiedtoken field, then submit the form.

Inputs: url (required), sitekey (required), proxy, action, +2 more. Returns: code, token, captchaId, solveSeconds

capskip_solve_recaptchaSolve reCAPTCHAA

Solve a Google reCAPTCHA v2 or v3 widget, including invisible and Enterprise variants. Returns a token to place in the page's "g-recaptcha-response" field before submitting the form. Read the sitekey from the page first — a guessed sitekey fails. Note that reCAPTCHA v3 returns a score assigned by Google; no solver can raise it.

Inputs: url (required), sitekey (required), proxy, action, +5 more. Returns: code, captchaId, solveSeconds

capskip_solve_turnstileSolve Cloudflare TurnstileA

Solve a Cloudflare Turnstile widget or interstitial challenge page. Returns a token for the page's "cf-turnstile-response" field. IMPORTANT: submit the token using the returned userAgent — Cloudflare rejects a token replayed under a different User-Agent. For an interstitial challenge page, also pass cdata and pagedata read from the page.

Inputs: url (required), sitekey (required), cdata, proxy, +3 more. Returns: code, captchaId, userAgent, solveSeconds

capskip_solve_yandex_smartSolve Yandex SmartCaptchaA

Solve a Yandex SmartCaptcha (a widget loaded from smartcaptcha.yandexcloud.net, usually a ) and get its token. Requires sitekey and url. You do not need to tick the checkbox or answer the challenges it shows; CapSkip returns only the finished token. Put the token in the form's hidden smart-token field, then submit the form. A token is valid for five minutes and can be checked once.

Inputs: url (required), sitekey (required), proxy, timeout, +1 more. Returns: code, token, captchaId, solveSeconds

capskip_statusCheck CapSkip statusA
Read-only

Check whether the CapSkip desktop app is running and reachable. Call this first when a solve fails unexpectedly, to tell "CapSkip is not running" apart from "the sitekey was wrong". Takes no arguments.

Inputs: no named parameters. Returns: host, port, detail, latencyMs, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Each tool maps cleanly to one captcha vendor, so purposes are largely distinct. The only close pairs are geetest vs geetest_v4 and recaptcha vs hcaptcha, and the descriptions explicitly disambiguate both (naming the script host, the field names, and 'do not use recaptcha for hCaptcha'), though friendly_captcha hides two protocols behind one name.

    Naming Consistency5/5

    Every tool is snake_case under a shared capskip_ prefix, with the dominant pattern capskip_solve_<vendor> (plus a suffix only where a vendor has multiple versions: geetest/geetest_v4). The single exception, capskip_status, is a genuinely different kind of operation and still follows the prefix convention.

    Tool Count5/5

    15 tools for a captcha-solving service is well-scoped: each tool corresponds to a distinct vendor/protocol that an agent might genuinely encounter, and none appear redundant or padded. The one non-solve tool (status) earns its place as a diagnostic for the common 'app not running' failure mode.

    Completeness4/5

    Coverage is broad across the major vendors (reCAPTCHA, hCaptcha, Turnstile, DataDome, GeeTest v3/v4, Capy, ALTCHA, Friendly, AWS WAF, MTCaptcha, Yandex, CaptchaFox, image) plus a health check. Minor gaps remain: no Lemin/Prosopo or legacy Cloudflare challenge solver, and no account/balance or solve-history tool, but these are workaroundable or out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      A local MCP server that lets AI agents bypass bot detection, geo-restrictions, and JavaScript rendering challenges when scraping the web, backed by ScraperAPI's services
      28
      5
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that lets AI agents use your real browser as an API, accessing any website with your login state, no keys or scrapers needed.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides an undetectable Playwright browser to bypass Cloudflare and other bot detection systems, enabling AI agents to navigate and scrape web pages without being blocked.
      11 npm
      MIT