Mithwire MCP

browser_solve_cloudflare

Detect and solve Cloudflare Turnstile challenges by clicking the verification checkbox. Requires a session ID to target the correct browser session.

Instructions

Detect and solve a Cloudflare Turnstile challenge by clicking the verification checkbox.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "browser_solve_cloudflare"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes
`max_retries`	No
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the mechanism (clicking the verification checkbox) but says nothing about failure behavior, what happens after retries are exhausted, or how it interacts with the max_retries/timeout parameters — significant gaps for a tool with an output schema and retry logic.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words. It is efficient, though its brevity contributes to the other gaps rather than being purely a virtue.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but the description omits parameter semantics and any behavioral detail on failure/retry handling. For a challenge-solving tool with retry and timeout knobs, this leaves the agent under-informed.

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

Parameters1/5

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

Schema description coverage is 0% and all three parameters (session_id, max_retries, timeout_seconds) are undocumented in the schema. The description adds no meaning for any of them, so it fails to compensate for the coverage gap.

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?

States a specific verb+resource: 'Detect and solve a Cloudflare Turnstile challenge by clicking the verification checkbox.' This is unambiguous and clearly distinguishable from generic siblings like browser_click or browser_wait_for_selector, since it names a specific anti-bot challenge type.

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

Usage Guidelines3/5

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

The trigger scenario (a Cloudflare Turnstile challenge being present) is implied by the description, but there is no explicit when-to-use/when-not guidance or pointer to alternatives such as browser_click or browser_wait_for_selector. Usage must be inferred.

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

Deploy Server