click_at

5 registry entries were observed exposing a tool named click_at — 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,470 of 26,658 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. @async23/chrome-devtools-mcpverified
   trust 85/100 · AMCP serverobserved 2026-08-17 · static extraction
   MCP server for Chrome DevTools
2. brave-mcpverified
   trust 85/100 · AMCP serverobserved 2026-08-19 · static extraction
   MCP server and CLI for Brave DevTools
3. ChromeDevTools/chrome-devtools-mcp
   trust 60/100 · BMCP serverobserved 2026-08-28 · static extraction
   Chrome DevTools for coding agents
4. @thinkrun/mcp
   trust 60/100 · BMCP serverobserved 2026-08-09 · static extraction
   Let your AI coding agent test its own frontend work. Connects Claude Code, Cursor, and any MCP client to your real Chrome browser — real ses
5. io.github.HayoDev/safari-devtools-mcp
   trust 60/100 · BMCP serverobserved 2026-06-13 · static extraction
   MCP server for Safari DevTools — browser debugging and automation for AI coding agents

All indexed toolsSearch the registry for click_at