mcp-browser-verify

Activation

• UI bug, layout mismatch, flow verification, auth journey, “sprawdź w przeglądarce”.
• Prefer mcp-browserclaw when BrowserClaw is connected (logged-in agent browser + cockpit).
• Do not use when the user needs CAPTCHA/2FA intervention or anti-bot in the BrowserOS human session — use mcp-browseros instead.

Procedure

1. Define scenario: URL, credentials (if any), steps, expected result.
2. Run scripted navigation.
3. Capture evidence: screenshots + console/network errors.
4. Report deltas + actionable fix hints.

Output

• Scenario + evidence + pass/fail + next fix step.