Solvegate Mcp

io.github.SolveGate由 GitHub 账号 SolveGate 发布v0.1.1更新于 Oct 24, 2026

Inspect a page for Cloudflare Turnstile free, and clear Turnstile and WAF challenges.

已验证STDIO仅桌面浏览器自动化安全与监控

概览

AI 生成的概览

一个本地 MCP 服务器,让助手检查页面是否带有 Cloudflare Turnstile,并在配置 API 密钥后清除 Turnstile 与 WAF 挑战以获取令牌。

可以做什么
检查指定网址,报告是否存在 Cloudflare Turnstile、其 sitekey、渲染方式、data-* 配置,或该页面是否为整页 WAF 挑战而非组件,无需账号或密钥。使用 API 密钥清除 Turnstile 或 Turnstile WAF 挑战并返回令牌。按 id 获取求解结果,免费且不会重复计费。求解在后台异步执行并轮询,因此即使超时也会留下可稍后查询的求解 id。
适用场景
适用于端到端测试、针对自有预发布环境的 CI,或对自有生产环境做合成监控时,Turnstile 挑战反复阻断自动化流程的情况。先做检查往往就能判断页面用的是 Turnstile,还是本服务器无法处理的 reCAPTCHA、hCaptcha 或 WAF 拦截页。
运行要求
通过 npx 在本地运行(需要 Node.js)。SOLVEGATE_API_KEY 可选:inspect_page 无需密钥即可使用,而 solve_turnstile 和 get_solve 需要密钥,例如无需绑卡的免费 sk_test_ 沙箱密钥。可选配置包括 SOLVEGATE_BASE_URL、SOLVEGATE_SITE_URL、SOLVEGATE_TIMEOUT_MS 和 SOLVEGATE_MAX_WAIT_MS。需要能访问 SolveGate API 的网络。
安装前请注意
求解需要 SOLVEGATE_API_KEY,真实关卡需要付费的 sk_live_ 密钥,因此求解会消耗账户余额,余额为空时返回 balance_empty。令牌一次性使用且有效期很短,应在提交时再申请。沙箱密钥返回 mode 为 sandbox,无法通过真实关卡。只对自有或获授权测试的站点求解,黑名单目标会被拒绝。密钥从环境变量读取,不作为工具参数传入。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Solvegate Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

solvegate-mcp

[CI] [npm] [Glama score]

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.

ToolWhat it doesNeeds a key
inspect_pageFetch 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 widgetNo
solve_turnstileClear a Turnstile or Turnstile WAF challenge and return a tokenYes
get_solveFetch a solve by id — free, never re-billsYes

Install

bash
npx solvegate-mcp

Claude Desktop / any MCP client, in your config:

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

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

VariableDefaultWhat it does
SOLVEGATE_API_KEY—Your key. sk_test_ for the sandbox, sk_live_ for real gates.
SOLVEGATE_BASE_URLhttps://api.solvegate.ioAPI base.
SOLVEGATE_SITE_URLhttps://solvegate.ioWhere inspect_page runs.
SOLVEGATE_TIMEOUT_MS30000Per-request timeout.
SOLVEGATE_MAX_WAIT_MS60000How long solve_turnstile waits for a pending solve.

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

bash
npm installnpm run buildnpm test          # spawns the built server and speaks MCP to itOFFLINE=1 npm test  # skips the two tests that reach the network

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

MIT.

来源:README.md,提交 9f471b6

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分