io.github.capsolver-ai/capsolver-mcp
PYPI · CAPSOLVER-MCP
MCP Server for CapSolver - captcha-solving capabilities for AI agents
Available components
Last scanned (16 hours ago)
Scores higher than 84% of PyPI servers
Category Security
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- 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 47 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 878 tokens (~175/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +14
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 25 Oct 26 +1
- Stability: 0.97 → pass security
- 24 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
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 4 Nov 2026 · Analysed pypi/capsolver-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
detect_captchas ~126
Detect which captcha types are present on a given page URL. Opens the page in a headless browser and inspects the DOM to identify captcha widgets (reCAPTCHA, Cloudflare Turnstile). Requires playwright to be installed. Args: page_url: The full URL of the page to inspect. Returns: {"success": True, "url": "...", "detected_captchas": ["reCaptchaV2", ...]} on success. {"success": False, "error": "..."} on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| page_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_balance ~65
Get the current CapSolver account balance. Returns: {"success": True, "balance": 5.67, "packages": [...]} on success. {"success": False, "error": "...", "error_id": ..., "error_code": "..."} on failure.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_supported_captchas ~38
List all captcha types supported by this CapSolver instance. Returns the registered handler names and all available captcha type values. No parameters required.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solve_captcha ~436
Solve a captcha in token mode — no browser required. CapSolver will create a task on its server, solve the captcha challenge, and return the solution token. Use this when you only need the token to submit to a target website (e.g. via form POST or API call). Args: captcha_type: One of "reCaptchaV2", "reCaptchaV3", "cloudflare". website_url: The full URL of the page where the captcha appears. website_key: The site key / public key / data-sitekey of the captcha widget. version: reCAPTCHA version hint ("v2" or "v3"). Usually auto-detected. page_action: reCAPTCHA v3 action name (e.g. "login", "submit"). min_score: reCAPTCHA v3 minimum score threshold (0.0–1.0). invisible: Whether the reCAPTCHA widget uses invisible mode. enterprise: Whether to use the Enterprise API variant. s_token: Enterprise s_token for stoken-based verification. cdata: Cloudflare Turnstile custom data parameter. proxy: Proxy in "user:pass@host:port" or "host:port" format. user_agent: Custom User-Agent string to use during solving. timeout: Maximum seconds to wait for a solution (default: 120). polling_interval: Seconds between status polls (default: 5). Returns: {"success": True, "solution": {...}} on success. {"success": False, "error": "...", "error_id": ..., "error_code": "...", "http_status": ...} on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| captcha_type | string | yes | – |
| cdata | – | – | – |
| enterprise | – | – | – |
| invisible | – | – | – |
| min_score | – | – | – |
| page_action | – | – | – |
| polling_interval | – | – | – |
| proxy | – | – | – |
| s_token | – | – | – |
| timeout | – | – | – |
| user_agent | – | – | – |
| version | – | – | – |
| website_key | string | yes | – |
| website_url | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
solve_on_page ~213
Detect, solve, and optionally autofill all captchas on a page. One-shot operation: opens the page in a headless browser, detects captcha widgets, solves them via the CapSolver API, and injects the solution tokens back into the page DOM. Requires playwright to be installed. Args: page_url: The full URL of the page containing captchas. autofill: If True, inject solved tokens into the page (default: True). timeout: Maximum seconds to wait per captcha (default: 120). polling_interval: Seconds between status polls (default: 5). Returns: {"success": True, "url": "...", "results": [{"captcha_type": "...", "solved": true, "token": "...", "filled": true}, ...]} {"success": False, "error": "..."} on failure.
| Name | Type | Req | Description |
|---|---|---|---|
| autofill | boolean | – | – |
| page_url | string | yes | – |
| polling_interval | – | – | – |
| timeout | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.capsolver-ai/capsolver-mcp server?
io.github.capsolver-ai/capsolver-mcp runs locally as a PyPI package, launched with uvx capsolver-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · capsolver-mcp
claude mcp add capsolver-ai-capsolver-mcp -- uvx capsolver-mcp
What is the io.github.capsolver-ai/capsolver-mcp server?
io.github.capsolver-ai/capsolver-mcp is listed in the public MCP registry as io.github.capsolver-ai/capsolver-mcp. MCP Server for CapSolver - captcha-solving capabilities for AI agents. This page covers its PyPI package (capsolver-mcp).
Is the io.github.capsolver-ai/capsolver-mcp server safe to use?
io.github.capsolver-ai/capsolver-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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.capsolver-ai/capsolver-mcp server expose?
io.github.capsolver-ai/capsolver-mcp exposes 5 tools: solve_captcha, detect_captchas, solve_on_page, get_balance, get_supported_captchas. Their descriptions and schemas cost roughly 878 tokens of context every time the server is loaded.
Is the io.github.capsolver-ai/capsolver-mcp server still maintained?
io.github.capsolver-ai/capsolver-mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 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.capsolver-ai/capsolver-mcp server under?
io.github.capsolver-ai/capsolver-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.