# Solvecha (remote · api.solvecha.com)

Solve reCAPTCHA image grids, text captchas, GeeTest and FunCAPTCHA for AI agents. Free tier.

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

## Components

- remote · `api.solvecha.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-solvecha-solvecha/api.md), [page](https://verifymcp.io/servers/com-solvecha-solvecha/api)

## Channel facts

- Endpoint: `https://api.solvecha.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 965 tokens (~160/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Solvecha MCP server?

Solvecha is a hosted endpoint at https://api.solvecha.com/mcp, so there is nothing to install locally. 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 --transport http com-solvecha-solvecha 'https://api.solvecha.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-solvecha-solvecha": {
      "url": "https://api.solvecha.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-solvecha-solvecha": {
      "type": "http",
      "url": "https://api.solvecha.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-solvecha-solvecha]
url = "https://api.solvecha.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-solvecha-solvecha": {
      "type": "remote",
      "url": "https://api.solvecha.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-solvecha-solvecha --url 'https://api.solvecha.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-solvecha-solvecha:
    url: "https://api.solvecha.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-solvecha-solvecha": {
      "Transport": "http",
      "Url": "https://api.solvecha.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-solvecha-solvecha -t streamable-http -u 'https://api.solvecha.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-solvecha-solvecha": {
      "type": "http",
      "url": "https://api.solvecha.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-04 (score 80, +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-11-02 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `get_account_status` (~32 tokens)

Show credit and plan

Shows the plan, the solves left today, the balance and the time until the daily reset. Free to call.

Output parameters:

- `balance_usd` (string)
- `daily_quota` (integer)
- `plan` (string): Plan name: a monthly plan, 'Free', 'Pay per use' or 'No plan'.
- `seconds_until_daily_reset` (integer): The daily quota resets at 00:00 UTC.
- `solves_left_today` (integer): How many more successful solves can be paid today (daily quota left plus balance).
- `status` (string)

### `report_result` (~133 tokens)

Report whether the site accepted the answer

Tells Solvecha whether a reCAPTCHA answer was accepted or rejected. Free, optional, and it improves accuracy.

Input parameters:

- `grid` (string, required): The grid you sent: '3x3', '4x4' or '1x1'.
- `job_id` (string, required): The job_id returned by solve_recaptcha_grid.
- `round_index` (null|integer): Optional: which challenge round this was, starting at 0.
- `verdict` (string, required): 'accepted' if the site accepted the answer (the challenge was passed or the next step appeared), 'rejected' if it did not.

Output parameters:

- `message` (string)
- `recorded` (boolean)

### `solve_funcaptcha` (~171 tokens)

Solve a FunCAPTCHA (Arkose Labs) puzzle

Solves a FunCAPTCHA tile-selection puzzle (mode 'tile') or a game-style match puzzle (mode 'match') and returns which tiles to pick. Costs one credit per successful solve.

Input parameters:

- `image` (string, required): One picture: the grid of tiles (mode tile) or the whole game image (mode match). Base64 or https URL.
- `mode` (string): 'tile' picks tiles in a 3x2 grid (default). 'match' solves game puzzles where a picture must match a reference.
- `task` (string, required): The instruction text, for example 'Pick the sheep' or 'Match the number of rocks with the number on the left'.
- `timeout_seconds` (integer): How long to wait for the answer, 5 to 90. Default 45.

Output parameters:

- `answer` (null|array)
- `job_id` (string)
- `mode` (string)
- `selected_tiles` (null|array): Tiles to pick, counted from 1 (left to right, top to bottom for tile mode; in the order of the answer options for match mode).

### `solve_geetest_slider` (~124 tokens)

Solve a GeeTest slider

Solves a GeeTest slider puzzle and returns how far to drag the handle, as a percentage of the background width. Costs one credit per successful solve.

Input parameters:

- `images` (null|array, required): Either one screenshot of the whole challenge, or two pictures in this order: the background, then the transparent puzzle piece. Each is base64 or an https URL.
- `task` (string): The instruction text of the challenge. Default 'slide'.
- `timeout_seconds` (integer): How long to wait for the answer, 5 to 90. Default 45.

Output parameters:

- `how_to_use` (string)
- `job_id` (string)
- `offset_percent` (number): How far to drag the slider handle, as a percentage of the width of the background picture as shown on the page.

### `solve_recaptcha_grid` (~255 tokens)

Solve a reCAPTCHA v2 image challenge

Solves a Google reCAPTCHA v2 image challenge from a screenshot and returns which tiles to click. Send the instruction text (task), the layout (grid) and the picture(s). Waits for the answer (usually 2 to 6 seconds). Costs one credit per successful solve. After you click and submit, call report_result with Google's verdict.

Input parameters:

- `grid` (string, required): Challenge layout: '3x3' or '4x4' (one picture of the whole grid) or '1x1' (single tile pictures, 1 to 9).
- `images` (null|array, required): For 3x3 and 4x4: exactly one picture of the whole grid. For 1x1: one to nine tile pictures. Each is base64 (PNG, JPEG, GIF or WebP; a data: URL is fine) or an https URL.
- `task` (string, required): The instruction text shown to the user, copied in full, for example 'Select all images with buses'.
- `timeout_seconds` (integer): How long to wait for the answer, 5 to 90. Default 45. Solves usually take 2 to 6 seconds.

Output parameters:

- `answer` (null|array): One boolean per tile: true means click it.
- `grid` (string)
- `job_id` (string): Pass this to report_result after you submit the answer.
- `positions` (null|array): The same tiles as 'row R, column C' (3x3 and 4x4 only).
- `selected_tiles` (null|array): Tiles to click, counted from 1. 3x3 and 4x4: left to right, top to bottom. 1x1: the number of the picture you sent. Empty means: click none (then press Verify or Skip).
- `summary` (string)

### `solve_text_captcha` (~83 tokens)

Solve a text captcha

Reads a picture with distorted letters and digits and returns the text (case-sensitive). Costs one credit per successful solve.

Input parameters:

- `image` (string, required): The captcha picture: base64 (a data: URL is fine) or an https URL.
- `timeout_seconds` (integer): How long to wait for the answer, 5 to 90. Default 45.

Output parameters:

- `job_id` (string)
- `text` (string): The recognised text. It is case-sensitive.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-solvecha-solvecha/api#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 75
- 2026-10-25: 75
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73

## Common questions

### What is the Solvecha MCP server?

Solvecha is an MCP server listed in the public MCP registry as com.solvecha/solvecha. Solve reCAPTCHA image grids, text captchas, GeeTest and FunCAPTCHA for AI agents. Free tier. This page covers its hosted endpoint (https://api.solvecha.com/mcp).

### Is the Solvecha MCP server safe to use?

Solvecha scores 80 out of 100 on VerifyMCP. 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 Solvecha MCP server expose?

Solvecha exposes 6 tools: get_account_status, report_result, solve_funcaptcha, solve_geetest_slider, solve_recaptcha_grid, solve_text_captcha. Their descriptions and schemas cost roughly 798 tokens of context every time the server is loaded.

### Does the Solvecha MCP server require authentication?

No. We connected to Solvecha without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Solvecha MCP server still maintained?

Solvecha is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.solvecha.com/mcp
- Authorisation metadata: https://api.solvecha.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/Solvecha/solvecha-skills
- Website: https://solvecha.com/ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-solvecha-solvecha/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-solvecha-solvecha/api.json
- HTML version of this page: https://verifymcp.io/servers/com-solvecha-solvecha/api