# io.github.SolveGate/solvegate-mcp (npm · solvegate-mcp)

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

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `solvegate-mcp`: 82/100 (this document), [markdown](https://verifymcp.io/servers/solvegate-solvegate-mcp/solvegate-mcp.md), [page](https://verifymcp.io/servers/solvegate-solvegate-mcp/solvegate-mcp)

## Channel facts

- Registry: `npm`
- Package: `solvegate-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add solvegate-solvegate-mcp -- npx -y solvegate-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "solvegate-solvegate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "solvegate-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "solvegate-solvegate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "solvegate-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add solvegate-solvegate-mcp -- npx -y solvegate-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "solvegate-solvegate-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "solvegate-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add solvegate-solvegate-mcp --command npx --arg -y --arg solvegate-mcp
```

### Hermes

```yaml
mcp_servers:
  solvegate-solvegate-mcp:
    command: "npx"
    args: ["-y", "solvegate-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "solvegate-solvegate-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "solvegate-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add solvegate-solvegate-mcp -t stdio -c npx -a -y solvegate-mcp
```

### Other

```json
{
  "mcpServers": {
    "solvegate-solvegate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "solvegate-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 82, +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.

### 2026-09-17 (score 81, +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.

### 2026-09-15 (score 80, +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.

### 2026-09-13 (score 79, +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.

### 2026-09-11 (score 78, +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.

### 2026-09-09 (score 77, +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.

### 2026-09-06 (score 76, +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.

### 2026-09-04 (score 75, +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.

## MCP tools (3)

### `inspect_page` (~161 tokens)

Inspect a page for Cloudflare Turnstile

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.

Input parameters:

- `url` (string, required): The page URL to inspect, e.g. https://example.com/login

Output parameters:

- `finalUrl` (string)
- `httpStatus` (number)
- `otherCaptcha` (array): Other CAPTCHA products on the page — we do not solve these
- `present` (boolean): Turnstile was found on the page
- `rendering`
- `responseFieldPresent` (boolean)
- `sitekeys` (array): Sitekeys found, in document order
- `summary` (string): One line a human can read
- `wafChallenge` (boolean): The response is a Cloudflare WAF challenge interstitial

### `solve_turnstile` (~208 tokens)

Solve a Cloudflare Turnstile or WAF challenge

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.

Input parameters:

- `action` (string): Optional Turnstile action label, if the widget sets one
- `gate` (string, required): Which challenge type to clear
- `proxy` (string): Optional egress proxy URL to solve through
- `sitekey` (string, required): The target's sitekey, e.g. 0x4AAAAAAA…
- `url` (string, required): The page URL the challenge renders on

Output parameters:

- `billed` (boolean)
- `errorCode` (string|null)
- `expiresAt` (number|null): Unix seconds after which the token is worthless
- `id` (string)
- `mode` (string): sandbox tokens NEVER clear a real gate
- `solveMs` (number|null)
- `status` (string)
- `summary` (string)
- `token` (string|null): Submit this as the cf-turnstile-response field

### `get_solve` (~93 tokens)

Retrieve a solve by id

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.

Input parameters:

- `id` (string, required): The solve id, e.g. slv_8Kd2aF9

Output parameters:

- `billed` (boolean)
- `errorCode` (string|null)
- `expiresAt` (number|null)
- `id` (string)
- `mode` (string)
- `status` (string)
- `summary` (string)
- `token` (string|null)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/solvegate-solvegate-mcp/solvegate-mcp#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 76
- 2026-09-05: 75
- 2026-09-04: 75
- 2026-09-03: 74
- 2026-09-02: 74
- 2026-09-01: 70
- 2026-08-31: 70
- 2026-08-30: 70
- 2026-08-29: 70
- 2026-08-28: 70
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 68

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/solvegate-mcp
- Socket report: https://socket.dev/npm/package/solvegate-mcp
- Repository: https://github.com/SolveGate/solvegate-mcp
- Changelog RSS feed: https://verifymcp.io/servers/solvegate-solvegate-mcp/solvegate-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/solvegate-solvegate-mcp/solvegate-mcp.json
- HTML version of this page: https://verifymcp.io/servers/solvegate-solvegate-mcp/solvegate-mcp