EverySolve — Authorized captcha workflows with discovered challenge schemas

简体中文 · Setup · Workflow · Prompts · Capability reference · API documentation

EverySolve is a standalone EveryInfra agent skill for authorized captcha integration through MCP. It discovers the supported challenge schema and solution shape, preserves required session context and separates a solver response from acceptance by the target application.

Captcha integrations fail when an application assumes that every challenge produces the same kind of answer. EverySolve first discovers the supported challenge schema and expected solution form, then keeps target authorization and any required browser or session context explicit.

Use this skill only for a target and workflow you are authorized to access or test. It describes how to integrate a supported solution; it is not permission to evade access restrictions or automate abuse.

What you can do

• Inspect supported challenge types before building an authorized integration.
• Confirm whether the expected result is a token, cookie, text, number or geometric answer.
• Diagnose a session or solution-shape mismatch without blindly retrying paid requests.

Quick start

This is a standalone, one-skill MCP workflow package, not a new API service. It requires a compatible agent host and the configured access described in setup. Local package validation does not establish live API availability.

Install the source repository in Codex after reviewing its contents. These commands add a GitHub-backed repository catalog, not an official marketplace endorsement:

codex plugin marketplace add everyinfra/everysolve-plugin
codex plugin add everysolve@everysolve-plugin

For a local checkout, replace the first command's source with .. Setup also covers Claude Code and the separate service connection.

Configure access once, then ask:

For this site that I administer, inspect the supported challenge types and list required inputs. Do not solve anything yet.

This initial prompt is scoped to inspection or preparation. Review any paid operation or external side effect before proceeding. Claude Code instructions and Cursor packaging boundaries are in setup.

How the workflow works

1. Confirm authorization for the exact target and requested operation.
2. Use everyinfra_list_captcha_types to discover type, parameters, availability and solution form.
3. Collect only required challenge inputs; preserve proxy or session identity where the live contract requires it.
4. Call everyinfra_solve_captcha only for the approved target and supported challenge.
5. Interpret the returned solution shape and apply it only within the matching authorized workflow.

What a useful result contains

A supported solution or an explicit failure state, with the application step matched to its actual shape. A returned token is not proof that the target site accepted it.

When to use this skill

EverySolve handles an authorized challenge step. It does not supply general browsing, data extraction or permission to access a target. Those prerequisites remain separate.

Limits and safety

• No guaranteed solution rate or universal support for challenge types.
• No token reuse across unrelated targets or sessions.
• No unsupported-type fallback guesses, unauthorized access or account-abuse workflows.

The package contains one skill and does not grant permissions or register a duplicate MCP connection. Never put credentials in prompts, checked-in files, screenshots or shared logs. Discovery, API execution, billing and a final external result are separate states. See security.

Frequently asked questions

Does every challenge return a token?

No. The catalog can describe different solution forms. The caller must inspect the live schema and the actual response.

Does solving mean the browser flow succeeded?

No. The target may reject an expired or context-mismatched solution. Report solver output separately from target acceptance.

Can it be used on any site?

Only within a workflow the user is authorized to access or test. This repository does not grant permission or remove a site’s access restrictions.

Validate and contribute

python3 scripts/validate.py

This offline check validates packaging, local documentation links, the single-skill boundary, metadata and fixtures. It does not send messages, allocate resources or verify a production account. Contribution guidance and the release checklist describe the remaining checks.

Source publication, tagged releases, official marketplace acceptance and live service verification are separate milestones. Maintained by EveryInfra. Licensed under Apache-2.0.