capskip-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Solve Capy Puzzle

capskip_solve_capy

Solve Capy Puzzle slide captchas and retrieve the captchakey, challengekey, and answer fields needed to submit the form successfully.

Instructions

Solve a Capy Puzzle captcha — a slide puzzle where a piece is dragged into a hole cut out of a photograph. IMPORTANT: unlike every other captcha tool here, the answer is NOT a single token. It is three values — captchakey, challengekey and answer — which all go into the target form, in fields named 'capy_captchakey', 'capy_challengekey' and 'capy_answer'. Submit the answer verbatim: it is the drag path the widget would have recorded, so trimming or re-encoding it invalidates the solve. The challenge key is single-use and short-lived, so submit promptly rather than caching the three values. A solve takes about two seconds — Capy refuses answers that arrive faster than a human could have produced them, so CapSkip holds the result back deliberately.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Full URL of the page the captcha appears on, including scheme.
`proxy`	No	Draw the puzzle image through this proxy. That fetch is the only request a Capy solve makes.
`sitekey`	Yes	The site's public Capy key, conventionally prefixed 'PUZZLE_'. Read it from 'capy_captchakey' in the page source, or from the widget script URL: <script src='https://jp.api.capy.me/puzzle/get_js/?k=PUZZLE_XXXX'>.
`timeout`	No	Seconds to wait before giving up. Maximum 600.
`api_server`	No	The root of the Capy API the key lives behind, taken from the widget script URL. Defaults to 'https://jp.api.capy.me'. Note that 'api.capy.me' no longer resolves, although several solver services still document it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes
`answer`	No
`respKey`	No
`captchaId`	Yes
`captchakey`	No
`challengekey`	No
`solveSeconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.0Sep 24, 2026

TDQS

A4.5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes well beyond the annotations, disclosing that the answer must be submitted verbatim, that trimming or re-encoding invalidates it, that the challenge key is single-use and short-lived, and that CapSkip deliberately holds the result for about two seconds to avoid fast-solve rejection. This is rich behavioral context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized for an unusually complex captcha solver. It front-loads the core purpose, then explains the non-standard answer formatituation, verbatim requirement, and timing behavior in compact sentences. Each sentence carries necessary information without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 100% schema coverage, existing output schema, and detailed annotations, the description covers all the unique behavioral requirements an agent must know to invoke and consume the result correctly. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The tool description does not add parameter-level meaning beyond the schema, but it does not need to because every parameter already has a detailed schema description. No contradiction or missing compensation is present.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: 'Solve a Capy Puzzle captcha' and explains what kind of puzzle it is. It also distinguishes the tool from siblings by explicitly stating that, unlike every other captcha tool here, the answer is not a single token.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use this tool: when dealing with a Capy Puzzle captcha, and contrasts it with 'every other captcha tool here' by explaining the three-value answer. It does not explicitly list when not to use it or mention sibling tools by name, but the unique answer format and field names provide strong usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server