Skip to main content
Glama
Sign In

EveryInfra

by io.github.xiaoxihexiaoyu
OverviewDiscussionsAdmin

Solve a CAPTCHA

everyinfra_solve_captcha
Destructive

Solve a CAPTCHA or bot challenge and get a ready-to-use solution. USD 0.000139/call–0.004583/call, charged per successful solve (castle: per token, × count); failed or empty attempts leave no final charge (anything reserved is restored). Use it when a target site is blocked by Turnstile / reCAPTCHA / hCaptcha / a Cloudflare challenge page / GeeTest and the like. Params differ per type — check them with everyinfra_list_captcha_types first.

Input Schema

NameRequiredDescriptionDefault
typeYesCAPTCHA type, e.g. turnstile / recaptcha_v2 / image
paramsNoParams for that type, e.g. {"website_url":"https://…","website_key":"0x…"}. ⚠ A few types need your own proxy: they deliver a cookie bound to the IP the challenge was solved from, so a solution from our exit IP would not work for you

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / params / description
      Previous value: -"该类型的参数,如 {\"website_url\":\"https://…\",\"website_key\":\"0x…\"}。⚠ 有几类要你自带代理(proxy):它们交付的是 Cookie 而 Cookie 绑定求解时的出口 IP —— 用我们的出口解出来,你拿去用是无效的"New value: +"Params for that type, e.g. {\"website_url\":\"https://…\",\"website_key\":\"0x…\"}. ⚠ A few types need your own proxy: they deliver a cookie bound to the IP the challenge was solved from, so a solution from our exit IP would not work for you"
    • changedInput schema / properties / type / description
      Previous value: -"验证码类型,如 turnstile / recaptcha_v2 / image"New value: +"CAPTCHA type, e.g. turnstile / recaptcha_v2 / image"
  2. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "akamai_bmp",
-  "akamai_sec_cpt",
-  "akamai_web",
-  "alibaba",
-  "altcha",
-  "anubis",
-  "atb_captcha",
-  "audio",
-  "aws_waf",
-  "aws_waf_classify",
-  "basilisk",
-  "binance",
-  "botdeflector",
-  "bounding_box",
-  "captchafox",
-  "capy",
-  "castle",
-  "cloudflare_challenge",
-  "coordinates",
-  "cutcaptcha",
-  "cybersiara",
-  "datadome",
-  "datadome_interstitial",
-  "f5_shape",
-  "f5_tspd",
-  "friendly_captcha",
-  "funcaptcha",
-  "geetest",
-  "hcaptcha",
-  "hunt",
-  "image",
-  "imperva",
-  "kasada",
-  "kasada_cd",
-  "keycaptcha",
-  "lemin",
-  "mtcaptcha",
-  "perimeterx",
-  "prosopo",
-  "recaptcha_grid",
-  "recaptcha_v2",
-  "recaptcha_v2_enterprise",
-  "recaptcha_v3",
-  "recaptcha_v3_enterprise",
-  "rotate",
-  "shein",
-  "slider",
-  "temu",
-  "tencent_tendi",
-  "text_captcha",
-  "turnstile",
-  "yandex_smartcaptcha",
-  "yidun"
-]New value: +[
+  "akamai_bmp",
+  "akamai_sec_cpt",
+  "akamai_web",
+  "alibaba",
+  "altcha",
+  "anubis",
+  "atb_captcha",
+  "audio",
+  "aws_waf",
+  "aws_waf_classify",
+  "basilisk",
+  "binance",
+  "botdeflector",
+  "bounding_box",
+  "captchafox",
+  "capy",
+  "castle",
+  "cloudflare_challenge",
+  "coordinates",
+  "cutcaptcha",
+  "cybersiara",
+  "datadome",
+  "datadome_interstitial",
+  "f5_shape",
+  "f5_tspd",
+  "friendly_captcha",
+  "funcaptcha",
+  "geetest",
+  "hcaptcha",
+  "hunt",
+  "image",
+  "imperva",
+  "kasada",
+  "kasada_cd",
+  "lemin",
+  "mtcaptcha",
+  "perimeterx",
+  "prosopo",
+  "recaptcha_grid",
+  "recaptcha_v2",
+  "recaptcha_v2_enterprise",
+  "recaptcha_v3",
+  "recaptcha_v3_enterprise",
+  "rotate",
+  "shein",
+  "slider",
+  "temu",
+  "tencent_tendi",
+  "text_captcha",
+  "turnstile",
+  "yandex_smartcaptcha",
+  "yidun"
+]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a cost range, billing semantics ('charged per successful solve', per-token for castle, no final charge on failure with reservation restored), and a proxy/IP-binding caveat for certain types. It stops short of describing latency, polling, or what the returned solution looks like, so it is not fully complete.

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?

Front-loaded with the core action, then pricing, then usage conditions and prerequisite. The pricing range is a bit dense but each clause carries operational information; no filler sentences.

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

Completeness4/5

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

Covers cost model, failure billing, per-type param discovery, and the proxy caveat for a tool with nested params and no output schema. Only gap is that it does not hint at whether solving is synchronous or job-based (a sibling everyinfra_get_job exists), which an agent might need.

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

Parameters4/5

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

Schema coverage is 100% (baseline 3), and the description goes further by warning that params vary per type and pointing to everyinfra_list_captcha_types. The IP-bound proxy caveat in the schema is reinforced, adding real meaning beyond field names.

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 and resource ('Solve a CAPTCHA or bot challenge and get a ready-to-use solution') and enumerates the challenge families (Turnstile / reCAPTCHA / hCaptcha / Cloudflare / GeeTest). This clearly separates it from administrative siblings like everyinfra_account or everyinfra_usage.

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

Usage Guidelines5/5

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

Gives an explicit trigger condition ('Use it when a target site is blocked by ...') and a prerequisite/alternative action: check per-type params with everyinfra_list_captcha_types first. Both when-to-use and the routing to a sibling are spelled out.

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

All EveryInfra toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources