io.github.SolveGate/solvegate-mcp
NPM · SOLVEGATE-MCP · SCANNED SEP 20
Inspect a page for Cloudflare Turnstile free, and clear Turnstile and WAF challenges.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 539 tokens (~179/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.SolveGate/solvegate-mcp server?
io.github.SolveGate/solvegate-mcp runs locally as an npm package, launched with npx -y solvegate-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · solvegate-mcp
claude mcp add solvegate-solvegate-mcp -- npx -y solvegate-mcp
{
"mcpServers": {
"solvegate-solvegate-mcp": {
"command": "npx",
"args": [
"-y",
"solvegate-mcp"
]
}
}
} {
"servers": {
"solvegate-solvegate-mcp": {
"command": "npx",
"args": [
"-y",
"solvegate-mcp"
]
}
}
} codex mcp add solvegate-solvegate-mcp -- npx -y solvegate-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"solvegate-solvegate-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"solvegate-mcp"
],
"enabled": true
}
}
} openclaw mcp add solvegate-solvegate-mcp --command npx --arg -y --arg solvegate-mcp
mcp_servers:
solvegate-solvegate-mcp:
command: "npx"
args: ["-y", "solvegate-mcp"] {
"McpServers": {
"solvegate-solvegate-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"solvegate-mcp"
]
}
}
} assistant mcp add solvegate-solvegate-mcp -t stdio -c npx -a -y solvegate-mcp
{
"mcpServers": {
"solvegate-solvegate-mcp": {
"command": "npx",
"args": [
"-y",
"solvegate-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/solvegate-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_solve Retrieve a solve by id ~93
Fetch a solve created earlier. Free — reading never re-bills. Use this when solve_turnstile timed out while still pending: the solve may have finished after the tool gave up, and the id is in that error message. A 404 means no such solve for this API key's workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The solve id, e.g. slv_8Kd2aF9 |
| Name | Type | Req | Description |
|---|---|---|---|
| billed | boolean | yes | – |
| errorCode | string|null | yes | – |
| expiresAt | number|null | yes | – |
| id | string | yes | – |
| mode | string | yes | – |
| status | string | yes | – |
| summary | string | yes | – |
| token | string|null | yes | – |
No examples provided.
inspect_page Inspect a page for Cloudflare Turnstile ~161
Fetch a URL and report what its HTML says about Cloudflare Turnstile: whether a widget is present, its sitekey, whether it renders implicitly or via turnstile.render(), the widget's data-* configuration, whether the sitekey is one of Cloudflare's documented test keys, and whether the page is a full-page WAF challenge rather than a widget. Free, no API key required. Use this before solving when the sitekey is unknown. It CANNOT determine the widget's mode (managed / non-interactive / invisible) — that is stored in the Cloudflare account that owns the sitekey and is not in the page at all.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page URL to inspect, e.g. https://example.com/login |
| Name | Type | Req | Description |
|---|---|---|---|
| finalUrl | string | yes | – |
| httpStatus | number | yes | – |
| otherCaptcha | array | yes | Other CAPTCHA products on the page — we do not solve these |
| present | boolean | yes | Turnstile was found on the page |
| rendering | – | yes | – |
| responseFieldPresent | boolean | yes | – |
| sitekeys | array | yes | Sitekeys found, in document order |
| summary | string | yes | One line a human can read |
| wafChallenge | boolean | yes | The response is a Cloudflare WAF challenge interstitial |
No examples provided.
solve_turnstile Solve a Cloudflare Turnstile or WAF challenge ~208
Clear a Cloudflare challenge and return a token. `gate` is "turnstile" for an embedded widget (there is a data-sitekey in the page) or "waf" for a full-page Cloudflare interstitial. `sitekey` and `url` are both required; the url must be the page the challenge actually renders on, because a sitekey is bound to its configured hostnames. Tokens are single-use and expire in minutes — request one at the moment you submit. Failed solves are never billed. Requires SOLVEGATE_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Optional Turnstile action label, if the widget sets one |
| gate | string | yes | Which challenge type to clear |
| proxy | string | – | Optional egress proxy URL to solve through |
| sitekey | string | yes | The target's sitekey, e.g. 0x4AAAAAAA… |
| url | string | yes | The page URL the challenge renders on |
| Name | Type | Req | Description |
|---|---|---|---|
| billed | boolean | yes | – |
| errorCode | string|null | yes | – |
| expiresAt | number|null | yes | Unix seconds after which the token is worthless |
| id | string | yes | – |
| mode | string | yes | sandbox tokens NEVER clear a real gate |
| solveMs | number|null | yes | – |
| status | string | yes | – |
| summary | string | yes | – |
| token | string|null | yes | Submit this as the cf-turnstile-response field |
No examples provided.
What is the io.github.SolveGate/solvegate-mcp server?
io.github.SolveGate/solvegate-mcp is listed in the public MCP registry as io.github.SolveGate/solvegate-mcp. Inspect a page for Cloudflare Turnstile free, and clear Turnstile and WAF challenges. This page covers its npm package (solvegate-mcp).
Is the io.github.SolveGate/solvegate-mcp server safe to use?
io.github.SolveGate/solvegate-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.SolveGate/solvegate-mcp server expose?
io.github.SolveGate/solvegate-mcp exposes 3 tools: inspect_page, solve_turnstile, get_solve. Their descriptions and schemas cost roughly 462 tokens of context every time the server is loaded.
Is the io.github.SolveGate/solvegate-mcp server still maintained?
io.github.SolveGate/solvegate-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.SolveGate/solvegate-mcp server under?
io.github.SolveGate/solvegate-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.