Skip to main content

MCP ReCaptcha Server

A Model Context Protocol (MCP) server for AceDataCloud's reCAPTCHA captcha-solving APIs.

Features

  • Solve reCAPTCHA image challenges and obtain reCAPTCHA v2/v3 tokens.
  • Bearer-token authentication through AceDataCloud

Connect locally

Use the local stdio package and an AceDataCloud API token. The public hosted HTTPS endpoint could not be verified, so this README does not offer it as a connection option. The local MCP process still calls AceDataCloud's API; it does not run the underlying service offline.

  1. Open Ace Data Cloud → Applications. Sign in, or register an account first.
  2. Find General application. If it has not been created, choose Initialize General Application. A general key can use the services available to your account; a dedicated application's key is limited to its service. Check the required service/model access and current pricing.
  3. Copy the API Key from the application card, or open Keys / Manage Keys → Create to create a separate key for this integration. Give it a recognizable name so you can revoke or rotate it independently.
  4. When creating a key, review Expiration Time, Set Usage Limitation, and Allowed APIs. Enable only the restrictions you need, allow the operations you will call, then click Create and copy the token from the key list. Task lookup does not grant permission to submit a generation. Confirm the application's balance can cover your first request; any trial allowance is whatever your account currently displays.
  5. Copy only the token value, without quotation marks, spaces, or Bearer . An API Key / API Token field expects this raw value; only a manually configured HTTP Authorization header needs the Bearer prefix. A platform-... account-management token cannot replace a generation API key.

Copy an application API key or open Manage Keys

Create a separately named key with optional restrictions

Save the key in the client's credential store or the environment variable shown below. Never put it in a prompt, shared workflow, screenshot, or Git commit. If authentication fails, check the full copied value, application/service access, expiration, usage limit, and balance before creating another key.

Local stdio

Install the package and give the local process an API token:

python -m pip install mcp-recaptcha
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
mcp-recaptcha

For Claude Desktop local MCP, merge this entry into the file opened by its developer settings (~/Library/Application Support/Claude/claude_desktop_config.json on macOS). uvx requires uv on PATH:

{
  "mcpServers": {
    "recaptcha": {
      "command": "uvx",
      "args": ["mcp-recaptcha"],
      "env": {"ACEDATACLOUD_API_TOKEN": "YOUR_API_TOKEN"}
    }
  }
}

Keep this user-level file private. Self-hosted HTTP uses mcp-recaptcha --transport http --port 8000; expose it only with suitable network and TLS controls. Local execution still calls the AceDataCloud API.

Check the connection

Confirm that the MCP client loads its tools. recaptcha_get_usage_guide returns reference information; it does not prove downstream API access or balance. A real service request can be billed. If it returns 401, check the API token; if it returns 403 or an account/balance error, read that response before retrying.

Tools

  • recaptcha_get_task — Retrieve an asynchronous result or terminal error
  • recaptcha2_recognize — Recognize a reCAPTCHA v2 image challenge
  • recaptcha2_get_token — Get a reCAPTCHA v2 token
  • recaptcha3_get_token — Get a reCAPTCHA v3 token
  • recaptcha_get_usage_guide — Get reCAPTCHA usage guide
  • recaptcha_get_api_info — Get reCAPTCHA API information

Service details

Service details

Asynchronous results

Set async: true to submit without waiting. If the response includes task_id, use recaptcha_get_task with that ID every 3–5 seconds until it returns status: ready or a terminal error. A task ID is an acceptance receipt, not a completed result. The query preserves terminal timeout details; do not create a replacement task while the original is processing. Some recognition requests return a ready result inline.

Metadata

Release files for mcp-recaptcha 2026.11.15.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-recaptcha 2026.11.15.0
File Size Uploaded Provenance Actions
mcp_recaptcha-2026.11.15.0.tar.gz 19.3 kB Without provenance Details for mcp_recaptcha-2026.11.15.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-recaptcha 2026.11.15.0
File Interpreter ABI Platform Actions
mcp_recaptcha-2026.11.15.0-py3-none-any.whl Python 3 none any Details for mcp_recaptcha-2026.11.15.0-py3-none-any.whl

Total release size: 39.9 kB

Release files / mcp_recaptcha-2026.11.15.0.tar.gz

Download URL mcp_recaptcha-2026.11.15.0.tar.gz
Size 19.3 kB
Tags Source
SHA-256 checksum
How to use checksums
43601fd65510bebdaa98bb9d655c65dac4961742ce1ad823fa0079b205ac39d8
BLAKE2b-256 checksum
How to use checksums
be75328029ddeade9093c0e72989d26b948a7cb0c452049b44c6384eb794f73d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release files / mcp_recaptcha-2026.11.15.0-py3-none-any.whl

Download URL mcp_recaptcha-2026.11.15.0-py3-none-any.whl
Size 20.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
06cbb3c55e48bc88253dd0dd354e9ca3151aa84eeaa604f315c8795d460e7891
BLAKE2b-256 checksum
How to use checksums
6d17e35234e28815590c9746384e3cd4939fcdc27ec2cd5cee73a194351d335a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Security for mcp-recaptcha 2026.11.15.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page