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 分