slack_reply_to_thread

2 registry entries were observed exposing a tool named slack_reply_to_thread — 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. @sigmacomputing/slack-mcp-serverMCPattestedtrust 85/100 · A
    v0.1.1
    ↓ 6k/wk

    MCP server for interacting with Slack

    ClaudeCursorCopilotGemini
    Sigma ComputingMIT7mo agonpmGitHubobserved · static extraction
  2. slack-workspace-mcp-serverMCPcommunitytrust 60/100 · B
    v0.0.7
    ↓ 237/wk

    MCP server for Slack workspace integration

    ClaudeCursorCopilotGemini
    PulseMCPMIT4mo agonpmGitHubobserved · static extraction
    mcpslackmodel-context-protocol

All indexed toolsSearch the registry for slack_reply_to_thread