browser_handle_dialog

4 registry entries were observed exposing a tool named browser_handle_dialog — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 8,491 of 26,663 scannable entries (32%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

1. @agent360/browser-mcp
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   Browser MCP — control your real Chrome from Claude Code. 34 tools, CAPTCHA solving, date pickers, autocomplete combobox, overlay dismissal,
2. @yawlabs/vew-mcp
   trust 60/100 · BMCP serverobserved 2026-08-10 · static extraction
   Browser MCP: drive a real Chromium via Playwright with compact ref-addressable page snapshots
3. io.github.JustasMonkev/mcp-accessibility-scanner
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server for automated web accessibility scanning with Playwright and Axe-core.
4. io.github.ofershap/real-browser
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server + Chrome extension for AI browser control with real sessions.

All indexed toolsSearch the registry for browser_handle_dialog