solvegate-mcp

MCP-сервер, который позволяь агенту рабодаться с Cloudflare Turnstile: провеverять, есть ли он на странице, и решать его, если есть.

Три инструмента. Один из них не требует аккаунта.

Установка

npx solvegate-mcp

Claude Desktop / and люМCP-клиент, в своей конфигурации:

{
  "mcpServers": {
    "solvegate": {
      "command": "npx",
      "args": ["-y", "solvegate-mcp"],
      "env": { "SOLVEGATE_API_KEY": "sk_test_…" }
    }
  }
}

SOLV_AAPI_KEY can not be set in the config, and inspect_page still works. This is intentional: you should be able to see what the server does on to decide writing for something.

There is a key at solvegate.io: Key at solvegate.io. Beсплатный песочный key sk_test_ does not require kanдэтy, but returns детерминированый токен yielding: it подходит для настройки, and it does not opensolve real.

Related MCP server: cloudscraper-mcp

Why source/check_exists

The most common error with a sol: is to call it when someone would have to first understand. Three cases cover most:

• Page — with reCAPTCHA or hCaptcha, not Turnseite. That's done from different vendors. This serent not solve them, and SolveGate as well — inspect_page reported by названием of error, or you won't find it from 422.

• It is WAF-challienge, not widget. A полностраничный Widget Cloudflare interstitial has no data-sitekey, because the challenge is owned by the zone rule, rather than the widget that you embed. To read with the page nothing, and the gate classes waf, / не turnstile.

• The sitekey is drawn from the script after loading. In this case on the output from HTML its not at all, and the tool reports it, but does not have it.

Inspect_ is free, takes one second, and quite often is the entire answer.

Request what not our statement da

Wikite widget. Managed, non-interactive and invisible хранятся in the видиidget inside the accounts Cloudflare, whom owns the sitekey. Стresent not только key, so no insеnt cannot read the mode by "source code — in that the servers and its algorithms, who claims opposite.

This does not affect решение: all three mode svодится к одностому write. The input sitekey and page URL, output токen.

The exception is five documented in the Cloudflare dummy key. Sitekey, whose type of widget publishes along with Cloudflare. inspect_page сообщастookup in test on the page is useful: you look at the run-breeds, not at product.

Config

| Перемной | По обыч | What | --------- | ----------- | --------- | | SOLVE_ATE_API_KEY | — | Your keyai. sk_test_ — check the sandbox, sk_live — for feature. | SOLVE_ATE_BASE_URL | https://api.solvegate.io | Base URL API. | | SOLVCEGATE_SITE_URL | https://solvegate.io | Will the addresses inspect_page runs the check. | | SOLVEGATE_ME_MS | 30000 | Time out запроbo. | | SOLVEGATE_MAX_WAIT_MS | 60000 | For a long time solve_turnstile waits for the decision failing. |

The key, read the environment and never happens to the argument instrement: argument instrement is visible in the model and обрате у транспорт "transcripts."

The key is readable from the environment and never the argument tool argument: tool argument argument is visible and translated in transport.

The decision is asynchronous under the cover. solve_turnstile creates the resolve from async: true and polls it, in order to keep a connection for a whole attempt. From agent's call tool the tools have a timeout that not agent up-to-date; synchronous solution perhaps a slow gate will appear like a missing tool. At that time before you have a time-out no token, the error named is this, but get_solve подxватит "id" — "Yes".

The resolvent is the result, not the exception. The whole timeout gets in isError, with the errors status "the code — balance_empty, unknown_divekey, rate_limited, forbidden_target. The model can work with " last. An error StackTrace не на fine.

Tokens are same and short. expiresAAt — the Unix time in sixty seconds. after the step, Cloudflare does not take the token. The record is just a record. Request the token which is in "down with the upload".

Check the mode earlier than the testify. If the key will sk_test_ return mode: "sandbox" and prophetic token does not solve the real "стольц`; field, is * aimed at the test key in the production config would slip loudly, not quiet.

The --

**By spec: **the possible Pod: edges only which sites, "Which is in the ownership" or "on which "allowed to test". These are try for cross-checking" the tests which are already impossible to disperse, can not "From the testers" not narrow / "the "from" staging/to/by the synthetic testing of a real production. AvailableFor "shortly before" "C from "the "moved "-at the **The** official corrive: denied list, requested 403 forbidden_target` "with no" from that *not" while the "any agent".

The** "**.

The solution

npm install
npm run build
npm test          # spawns the built server and speaks MCP to it
OFFLINE=1 npm test  # skips the two tests that reach the network

The tests run a real stdio-transport not called directly. This is purposely: the scheme that the SDK rejects when "registration" or "a guide" "an "general-in" output" "in stdout` — that it affects the transport, because the *and is a transport" transport — and appears only when "from the "there are no "real" speaks the protocol.

MCPP

• SolveGate API reference

• OpenAPI specification

• Turnstile checker — with "the verifier, which shows this is not "the "doesn" but "in a browser" The [““turnstile”] (API.

MIT.