reply_to_message

8 registry entries were observed exposing a tool named reply_to_message — 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. @mindstone/mcp-server-microsoft-teamsverified
    trust 85/100 · AMCP serverobserved · static extraction
    Microsoft 365 Teams via Graph: list chats, read/send messages, list teams/channels, presence.
  2. io.github.Mnexa-AI/mcp-serververified
    trust 85/100 · AMCP serverobserved · static extraction
    Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
  3. @keyid/agent-kit
    trust 60/100 · BMCP serverobserved · static extraction
    KeyID MCP server for agent email, SMS, OTP/TOTP, and signup verification
  4. sentvia-mcp
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server for SentVia — email infrastructure for AI agents. Create inboxes, send and reply, search, manage threads, webhooks and allow/bloc
  5. com.memotrader/mcp
    trust 60/100 · BMCP serverobserved · static extraction
    AI-to-human attention marketplace. Agents pay CPM to reach humans, earn credits by replying.
  6. dev.e2a/mcp-server
    trust 60/100 · BMCP serverobserved · static extraction
    Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
  7. io.github.KeyID-AI/keyid
    trust 60/100 · BMCP serverobserved · static extraction
    Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents.
  8. sentfromai-mcp
    trust 60/100 · BMCP serverobserved · static extraction
    MCP server for SentFromAI — email infrastructure for AI agents. Create inboxes, send and reply, search, manage threads, webhooks and allow/b

All indexed toolsSearch the registry for reply_to_message