NoneCap
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NONECAP_API_KEY | Yes | Your NoneCap API key. | |
| NONECAP_BASE_URL | No | Set this to point the server at a different API host. |
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 |
|---|---|
| solve_hcaptchaA | Solve an hCaptcha and return the token. Waits up to wait_seconds; if the solve is still running then, returns its id and status: call get_solve with the id rather than solving again. Only successful solves are charged. |
| get_solveA | Get a solve by id: its status, and the token once it is solved. Set wait_seconds to wait for it to finish. |
| cancel_solveA | Cancel a pending or running solve. Cancelled solves are not charged. |
| list_solvesA | List your recent solves, newest first. |
| get_accountA | Get your NoneCap account: credit balance, and your plan's solves left today. |
| report_solve_outcomeA | Tell NoneCap whether the site accepted a solve's token. Free; reporting the same solve again corrects it. |
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 6 tools
Each tool maps to a distinct action in the solve lifecycle: start (solve_hcaptcha), poll by id (get_solve), cancel (cancel_solve), list (list_solves), outcome reporting (report_solve_outcome), and account lookup (get_account). The descriptions explicitly resolve the one potential overlap between solve_hcaptcha and get_solve (both can wait) by instructing callers to poll with get_solve rather than re-solving.
Names follow a verb_noun shape (solve_hcaptcha, cancel_solve, list_solves, get_account, report_solve_outcome, get_solve). The only wrinkle is that 'solve' is a verb in solve_hcaptcha but a noun object in cancel_solve/get_solve/report_solve_outcome, a minor inconsistency that remains readable.
Six tools is well-scoped for a captcha-solving service: one per lifecycle operation plus account info. No tool feels redundant or missing from the set.
The surface covers the full solve lifecycle: initiate, poll/retrieve token, cancel, list history, report acceptance, and check credits/quota. There are no obvious dead ends for an agent driving a solve end-to-end.