Slack (Sigma Computing) (sigmacomputing) MCP Server

@sigmacomputing/slack-mcp-server npm v0.1.1 Source verified

Published by sigmacomputing — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for interacting with Slack.

Trust grade
C
78/100
Last scanned
Trust
C · 78/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
C Why this grade 100 − 22 = 78/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−22 Hardcoded Slack token in server code MTC-SRC-008 exfiltration

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind the deduction.

Findings 2

high Hardcoded Slack token in server code (dist/tests/slack-mcp-server.test.js)MTC-SRC-008

A live-looking Slack token is hardcoded in `dist/tests/slack-mcp-server.test.js:40`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: Slack token: xoxb…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/tests/slack-mcp-server.test.js

medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003

In the server's implementation (`dist/index.js:32`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`https://slack.com/api/conversations.list?${params}`

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/index.js

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest C 78/100 2 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: C · 78/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sigmacomputing-slack-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/sigmacomputing-slack-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/sigmacomputing-slack-mcp-server"><img src="https://mcptrustchecker.com/registry/sigmacomputing-slack-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sigmacomputing-slack-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @sigmacomputing/slack-mcp-server --online

Use the free API → How scoring works

Other implementations of Slack (Sigma Computing) 25

Independent packages implementing the same tool, scanned with the same engine. Compare all 26 side by side →

More in Productivity & Workflow