
Solvegate Mcp
io.github.SolveGatePublished by GitHub account SolveGatev0.1.1Updated Oct 24, 2026
Inspect a page for Cloudflare Turnstile free, and clear Turnstile and WAF challenges.
Overview
A local MCP server that lets an assistant inspect pages for Cloudflare Turnstile and, with an API key, clear Turnstile and WAF challenges to obtain a token.
- What you can do
- Inspect a URL and report whether Cloudflare Turnstile is present, its sitekey, rendering, data-* configuration, or whether it is a full-page WAF challenge instead of a widget, without needing an account or key. Clear a Turnstile or Turnstile WAF challenge and return a token, using an API key. Fetch a solve by id, which is free and never re-bills. Solving runs asynchronously and polls, so a timeout still leaves a solve id that can be retrieved later.
- When to use it
- Useful for end-to-end tests, CI against your own staging, or synthetic monitoring of your own production when a Turnstile challenge keeps blocking automation. Inspecting first is often enough to tell whether a page uses Turnstile at all, or reCAPTCHA, hCaptcha, or a WAF interstitial that this server cannot solve.
- Requirements
- Runs locally via npx (Node.js). SOLVEGATE_API_KEY is optional: inspect_page works without it, while solve_turnstile and get_solve need a key, such as a free sk_test_ sandbox key that needs no card. Optional settings include SOLVEGATE_BASE_URL, SOLVEGATE_SITE_URL, SOLVEGATE_TIMEOUT_MS and SOLVEGATE_MAX_WAIT_MS. Network access to the SolveGate API is required.
Installation
In SourceWeft
- Open Solvegate Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
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_pagesays so by name instead of letting you find out from a422. - 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 iswafrather thanturnstile. - 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
The key is read from the environment and is never a tool argument — a tool argument is model-visible and ends up in transcripts.
Notes on behaviour
Solving is async underneath. solve_turnstile creates the solve with
async: true and polls it, rather than holding a connection open for the whole
attempt. An agent's tool call has a timeout it does not control, and a
synchronous solve makes a slow gate look like a dead tool. It also means a
timeout here leaves you a solve id: the error names it, and get_solve will pick
it up rather than losing a solve that was already billed.
Errors are results, not exceptions. Every failure comes back as an isError
result carrying SolveGate's own error.code — balance_empty, unknown_sitekey,
rate_limited, forbidden_target. A model can act on those. It can do nothing
useful with a stack trace.
Tokens are single-use and short-lived. expiresAt is Unix seconds; past it,
Cloudflare stops accepting the token and the solve record is just a record.
Request a token at the moment you submit it.
Check mode before trusting a token. An sk_test_ key returns
mode: "sandbox", and a sandbox token will not clear a real gate. The field
exists so a test key in a production config fails loudly rather than quietly.
Acceptable use
Solve only against properties you own or are authorised to test. This exists for
end-to-end tests that keep failing on a challenge, CI against your own staging,
and synthetic monitoring of your own production. The
acceptable use policy is the binding version, and
targets on the denylist return 403 forbidden_target regardless of what any
agent asks for.
Development
The tests drive a real stdio transport rather than calling the tool callbacks directly. That is on purpose: a schema the SDK rejects at registration, or a stray write to stdout — which corrupts the transport, since stdout is the transport — only shows up when something actually speaks the protocol to it.
Links
- SolveGate API reference
- OpenAPI spec
- Turnstile checker — the same inspection this server exposes, in a browser
- Turnstile error index
MIT.
Source: README.md at commit 9f471b6
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts