Slack MCP Server

The material explicitly states it uses Slack session tokens and claims full access without OAuth, admin approval, or app registration; session tokens are typically highly sensitive, and theft or reuse could directly impersonate a user's session, creating a serious credential abuse risk.

The description indicates it accesses Slack, so prompt content or operational data will likely be sent to Slack-related services; the material does not list concrete remote endpoints, and there is no direct evidence of exfiltration to unrelated or unknown third parties, but the egress details are opaque.

System checks indicate this tool executes code or starts processes; this is a common MCP capability and does not by itself justify a high-risk rating, but it does mean the tool has local execution surface and should run in a constrained environment.

The phrase 'full Slack access' implies broad reach into messages, channels, or workspace data under the user's Slack session, while the material also emphasizes bypassing standard authorization flows; this suggests an unusually broad access scope with unclear permission boundaries, which is a red flag for overbroad data access.

While the project is open source and MIT-licensed, which provides some auditability, it comes from a third-party registry, has no README, zero stars, unknown maintenance status, and its stated behavior appears to bypass official authorization mechanisms; overall, supply-chain trust is insufficient.