CaptchaLa MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAPTCHALA_APP_KEY | No | Your CaptchaLa App Key (sent as X-App-Key). Required for validate_captcha_token and issue_server_token tools. | |
| CAPTCHALA_APP_SECRET | No | Your CaptchaLa App Secret (sent as X-App-Secret). Required for validate_captcha_token and issue_server_token tools. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_captchala_docsB | Search the CaptchaLa documentation. Returns the most relevant doc sections for a query. |
| get_captchala_docB | Fetch a specific CaptchaLa documentation page by path. |
| validate_captcha_tokenA | Validate a CaptchaLa pass token against the CaptchaLa API. Requires App Key/Secret (per-call or env). |
| issue_server_tokenB | Issue a server-side CaptchaLa challenge token for an action. Requires App Key/Secret (per-call or env). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct and clear purpose: documentation retrieval (get vs search) is separated, and token issuance and validation are distinct operations. No ambiguity between tools.
Tools follow a consistent verb_noun snake_case pattern. Minor inconsistency: one uses singular 'doc' and another plural 'docs', but overall pattern is clear.
4 tools is well-scoped for a captcha service server. It covers essential operations (token issue, validate) and documentation support without unnecessary bloat.
The tool set covers the entire captcha workflow: issuing server-side challenges and validating client tokens, plus documentation retrieval. No obvious missing operations for the given purpose.