@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.
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:
| Points | What was found | Category |
|---|---|---|
| −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.
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
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
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.1 latest |
C 78/100 | 2 | 1.5.0 | 2026-07-22 |
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.
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
Independent packages implementing the same tool, scanned with the same engine. Compare all 26 side by side →
Session-based, local-first Slack MCP server with 21 tools that works without OAuth.
Slack workspace MCP server covering channels, messages, threads, reactions, users, files, bookmarks, and message scheduling via the Slack Web API.
Security scan results for the Slack (avidian) MCP server.
Security scan results for the Slack (axivo) MCP server.
Security scan results for the Slack (korotovsky) MCP server.
Security scan results for the Slack (mintmcp) MCP server.
Security scan results for the 0nmcp MCP server.
Security scan results for the 126 Email MCP server.
Security scan results for the 5dive MCP server.
Security scan results for the 7pace MCP server.
Security scan results for the Adaptive Cards MCP server.
Security scan results for the Adb Mcp Tool MCP server.