Secure read-only MCP server for Slack workspaces
Secure read-only MCP server for Slack workspaces. Provides Claude Code (and other MCP clients) with access to your Slack channels, messages, users, and files without any write permissions. Read-only: 15 tools, all read-only. Never posts, edits, or deletes anything. Secure: 6-layer security model (input validation, token handling, client hardening, output sanitization, runtime protection, supply…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Secure read-only MCP server for Slack workspaces. Provides Claude Code (and other MCP clients) with access to your Slack channels, messages, users, and files without any write permissions. Read-only: 15 tools, all read-only. Never posts, edits, or deletes anything. Secure: 6-layer security model (input validation, token handling, client hardening, output sanitization, runtime protection, supply chain security). User OAuth Token: Uses tokens for user-scoped access to your workspace. No SDK…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.