Slack

The materials explicitly state that no keys or environment variables are required, and they do not show any need for user-supplied API keys or local sensitive credentials; based on the provided facts, there is no clear credential-abuse red flag.

Its stated functions—sending/receiving messages, managing channels, and interacting with a workspace—necessarily imply sending messages or actions to Slack-side services. Although no specific remote host is listed, it does present a normal data-egress surface typical of a networked collaboration tool.

The system flags executes-code, indicating that this MCP tool runs as a local process. That is a normal execution model for MCP tools, and the materials do not show any request for system privileges beyond its stated purpose, so this warrants caution rather than a high-risk rating.

By description, it can access and operate on collaboration data within a Slack workspace, such as messages and channels. The materials do not claim arbitrary local file access or unrelated resource access, but its ability to read/write workspace content means permissions should still be scoped carefully.

The source is a curated awesome list entry and an open-source repository is provided, with about 1,665 stars, giving it reasonable auditability and positive trust signals. Although the license is unspecified and maintenance status is unknown, those factors alone do not constitute a high-risk supply-chain red flag.