reply_all

2 registry entries were observed exposing a tool named reply_all — 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,336 of 40,577 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. @artymclabin/gmail-mcpMCPcommunitytrust 60/100 · B

   v1.2.3

   ↓ 603/wk

   Lean Gmail MCP server with auto authentication support (maintained fork of GongRzhe/Gmail-MCP-Server)

   ClaudeCursorCopilotGemini

   Arty McLabinMIT3mo agonpmGitHub+compareobserved 2026-07-15 · static extraction

   gmailmcpcursoraioauthmodel-context-protocol
2. io.github.mkpoli/gmail-mcpMCPcommunitytrust 60/100 · B

   v0.2.1

   Multi-account Gmail on a Cloudflare Worker you deploy yourself: read, send, reply, labels, threads

   io.github.mkpoliUnknown2mo agoGitHub+compareobserved 2026-08-18 · static extraction

   mcp

All indexed toolsSearch the registry for reply_all