Slack (mindstone) MCP Server

@mindstone/mcp-server-slack npm v0.3.0 Source verified

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

Slack workspace MCP server covering channels, messages, threads, reactions, users, files, bookmarks, and message scheduling via the Slack Web API.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. 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.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

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 a deduction.

Findings 3

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

In the server's implementation (`dist/tokenProvider.js:363`): 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: onse = await globalThis.fetch('https://slack.com/api/oauth.v2.access', { method: 'POST',

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/tokenProvider.js

medium Unconstrained URL/host parameter "file_url" on "download_slack_file"MTC-CAP-007

Tool "download_slack_file" takes a URL/host parameter "file_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool download_slack_file · inputSchema.properties.file_url

medium Unconstrained URL/host parameter "url" on "get_slack_message_by_link"MTC-CAP-007

Tool "get_slack_message_by_link" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool get_slack_message_by_link · inputSchema.properties.url

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • download_slack_fileingests untrusted input
  • get_slack_channel_historyingests untrusted input
  • get_slack_message_by_linkingests untrusted input
  • get_slack_thread_repliesingests untrusted input
  • get_slack_unread_messagesingests untrusted input
  • lookup_user_by_emailingests untrusted input
  • add_slack_bookmarkno sensitive capability
  • add_slack_reactionno sensitive capability
  • add_slack_reminderno sensitive capability
  • authenticate_slack_workspaceno sensitive capability
Show 29 more tools ↓
  • complete_slack_reminderno sensitive capability
  • compose_slack_messageno sensitive capability
  • create_slack_channelno sensitive capability
  • delete_scheduled_slack_messageno sensitive capability
  • delete_slack_messageno sensitive capability
  • delete_slack_reminderno sensitive capability
  • get_slack_saved_messagesno sensitive capability
  • get_slack_user_profileno sensitive capability
  • invite_user_to_channelno sensitive capability
  • list_scheduled_slack_messagesno sensitive capability
  • list_slack_bookmarksno sensitive capability
  • list_slack_channelsno sensitive capability
  • list_slack_emojino sensitive capability
  • list_slack_pinsno sensitive capability
  • list_slack_remindersno sensitive capability
  • list_slack_usersno sensitive capability
  • list_slack_workspacesno sensitive capability
  • mark_slack_channel_as_readno sensitive capability
  • open_slack_dmno sensitive capability
  • pin_slack_messageno sensitive capability
  • post_slack_messageno sensitive capability
  • remove_slack_reactionno sensitive capability
  • reply_to_slack_threadno sensitive capability
  • schedule_slack_messageno sensitive capability
  • search_slack_messagesno sensitive capability
  • send_myself_a_noteno sensitive capability
  • unpin_slack_messageno sensitive capability
  • update_slack_messageno sensitive capability
  • upload_slack_fileno sensitive capability

What this scan could not see

Versions 3

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.3.0 latest A 97/100 3 1.13.0 2026-08-25
v0.2.0 A 97/100 3 1.12.1 2026-07-31
v0.1.6 A 97/100 3 1.12.1 2026-07-27

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: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mindstone-mcp-server-slack/badge.svg)](https://mcptrustchecker.com/registry/mindstone-mcp-server-slack)
HTML
<a href="https://mcptrustchecker.com/registry/mindstone-mcp-server-slack"><img src="https://mcptrustchecker.com/registry/mindstone-mcp-server-slack/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mindstone-mcp-server-slack/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 @mindstone/mcp-server-slack --online

Use the free API → How scoring works

Other implementations of Slack 29

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

More in Productivity & Workflow