SkillTotal

Is Slack MCP server safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js network egress
  • npm prepare hook
  • MCP tool surface detected

@modelcontextprotocol/server-slack is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 3 risky constructs are reported for review. It can: install time execution, mcp tools detected and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

@modelcontextprotocol/server-slack 2025.4.25

npm_package · npm:@modelcontextprotocol/server-slack
LOW
0
/ 100 risk score
Snapshot · scanned Sep 24, 2026 · @modelcontextprotocol/server-slack@2025.4.25 · engine 0.53.0 / ruleset 60

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Slack MCP server's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
install time executionmcp tools detectednetwork egress

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Tool surface
Tool Usage
Network egress
Interaction & Communication / Direct Communication
Supply-chain provenance risk
General Protections / Supply Chain

Findings (3)

MEDIUMnpm prepare hookST-INSTALL-NPM-PREPARE

package.json has a 'prepare' script (runs on git/local installs and before publishing).

"prepare": "npm run build",

Why it matters: Usually a build step, but confirm it doesn't fetch or run remote code.

Fix: Usually a legitimate build step; confirm it only builds and does not fetch or execute remote code.

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

const response = await fetch(`https://slack.com/api/conversations.list?${params}`, { headers: this.botHeaders });
const response = await fetch(`https://slack.com/api/conversations.info?${params}`, { headers: this.botHeaders });
const response = await fetch("https://slack.com/api/chat.postMessage", {
const response = await fetch("https://slack.com/api/chat.postMessage", {
const response = await fetch("https://slack.com/api/reactions.add", {
const response = await fetch(`https://slack.com/api/conversations.history?${params}`, { headers: this.botHeaders });
const response = await fetch(`https://slack.com/api/conversations.replies?${params}`, { headers: this.botHeaders });
const response = await fetch(`https://slack.com/api/users.list?${params}`, {
const response = await fetch(`https://slack.com/api/users.profile.get?${params}`, { headers: this.botHeaders });

Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.

Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.

LOWMCP tool surface detectedST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

const server = new Server({

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →