browser_extract

3 registry entries were observed exposing a tool named browser_extract — 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 12,342 of 40,590 scannable entries (30%) — 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. @thinkrun/mcpMCPcommunitytrust 60/100 · B
    v0.3.8
    ↓ 165/wk

    Let your AI coding agent test its own frontend work. Connects Claude Code, Cursor, and any MCP client to your real Chrome browser — real sessions, real cookies, no headless conflicts.

    ClaudeCursorCopilotGemini
    ThinkRunMIT3mo agonpmGitHubobserved · static extraction
    mcpbrowserautomationplaywrightthinkrunai-agent
  2. @ainative/browser-mcpMCPcommunitytrust 60/100 · B
    v1.1.2

    AI-powered browser automation MCP — 6 tools for web interaction, extraction, and validation.

    ClaudeCursorCopilotGemini
    io.github.AINative-StudioUnknown2mo agonpmGitHubobserved · static extraction
    mcp
  3. weboperator-mcpMCPcommunitytrust 60/100 · B
    v1.5.1

    Hands your live Chrome tab to any MCP client — snapshot, navigate, click, type, extract.

    ClaudeCursorCopilotGemini
    Artem KKMIT1mo agonpmGitHubobserved · static extraction
    mcpmodelcontextprotocolbrowserchromebrowser-automationweb-agent

All indexed toolsSearch the registry for browser_extract