SolveGate/solvegate-mcp

An MCP server that lets an agent deal with Cloudflare Turnstile: check whether a
page has one, and clear it when it does.
Three tools. One of them needs no account.
| Tool | What it does | Needs a key |
|---|---|---|
| inspect_page | Fetch a URL and report whether Cloudflare Turnstile is on it, its sitekey, how it renders, its data-* configuration, and whether the page is a full-page WAF challenge instead of a widget | **No** |
| solve_turnstile | Clear a Turnstile or Turnstile WAF challenge and return a token | Yes |
| get_solve | Fetch a solve by id — free, never re-bills | Yes |
Install
Claude Desktop / any MCP client, in your config:
Leave SOLVEGATE_API_KEY out and inspect_page still works. That is deliberate:
you should be able to see what the server does before deciding whether to sign
up for anything.
Get a key at solvegate.io. A free sk_test_ sandbox key
needs no card and returns a deterministic token instantly — right for wiring this
up, and it never clears a real gate.
Why inspect_page exists
The commonest wrong turn with a solver is calling it when you should have looked
first. Three cases account for most of it:
- **The page carries reCAPTCHA or hCaptcha, not Turnstile.** Those are different
products from different vendors. This server does not solve them, and neither
does SolveGate — inspect_page says so by name instead of letting you find out
from a 422.
- **It is a WAF challenge, not a widget.** A full-page Cloudflare interstitial
has no data-sitekey, because the challenge belongs to a zone rule rather than
to a widget you embed. There is nothing to read off the page, and the gate is
waf rather than turnstile.
- **The sitekey is rendered from script after load.** Then it is not in the
served HTML at all, and the tool says that rather than guessing.
Inspecting is free, takes about a second, and is quite often the whole answer.
What it will not tell you
**The widget mode.** Managed, non-interactive and invisible are stored on the
widget inside the Cloudflare account that owns the sitekey. The page carries only
the key, so no tool can read the mode off the source — including this one, and
including anything that claims otherwise.
It does not matter for solving: all three modes resolve to the same request. A
sitekey, a page URL, and a token back.
The one exception is Cloudflare's five documented dummy sitekeys, whose widget
type Cloudflare publishes itself. inspect_page reports those, and finding one
on a page tells you something useful — you are looking at a staging build rather
than production.
Configuration
| Variable | Default | What it does |
|---|---|---|
| SOLVEGATE_API_KEY | — | Your key. sk_test_ for the sandbox, sk_live_ for real gates. |
| SOLVEGATE_BASE_URL | https://api.solvegate.io | API base. |
| SOLVEGATE_SITE_URL | https://solvegate.io | Where inspect_page runs. |
| SOLVEGATE_TIMEOUT_MS | 30000 | Per-request timeout. |
| SOLVEGATE_MAX_WAIT_MS | 60000 | How long solve_turnstile waits for a pending solve. |
The key is read from the environment and is never a tool argument — a tool