Is Slack · korotovsky safe and trustworthy?

tashan scores Slack · korotovsky on public evidence — tashan score 62.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Slack · korotovsky?

In Claude Code: run `claude mcp add slack-mcp-server -- npx -y slack-mcp-server`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Slack · korotovsky?

source: korotovsky/slack-mcp-server.

‹ The Index

Slack · korotovsky

npm

Model Context Protocol (MCP) server for Slack Workspaces. This integration supports both Stdio and SSE transports, proxy settings and does not require any permissions or bots being created or approved by Workspace admins

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Messaging and email · Prompt engineering

Who it is for: Operations · AI engineer

Install (Claude Code):

claude mcp add slack-mcp-server -- npx -y slack-mcp-server

tashan score: 62.0
Adoption: 22k/wk
Upkeep: 61.0
Freshness: 64.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 1.3.0 — and the 7 packages it installs

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Slack · korotovsky scores 62 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-slack-mcp-server.svg)](https://tashan.sh/capability/pkg-slack-mcp-server.html)

npm ↗ · source ↗ · pkg:slack-mcp-server

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?