# @mindstone/mcp-server-slack

Slack MCP server: channels, messages, threads, reactions, users, files, and scheduled messages

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.3.0
- **Author:** io.github.mindstone
- **License:** Unknown
- **npm:** @mindstone/mcp-server-slack
- **Source:** https://github.com/mindstone/mcp-servers
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 48 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-18T11:37:36.263Z
- **Version scanned:** 0.3.0
- **CVEs:** none found by OSV at scan time

## Tools

39 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `authenticate_slack_workspace`
- `list_slack_workspaces`
- `list_slack_channels`
- `get_slack_channel_history`
- `create_slack_channel`
- `mark_slack_channel_as_read`
- `get_slack_unread_messages`
- `invite_user_to_channel`
- `download_slack_file`
- `upload_slack_file`
- `search_slack_messages`
- `get_slack_saved_messages`
- `get_slack_message_by_link`
- `send_myself_a_note`
- `compose_slack_message`
- `post_slack_message`
- `reply_to_slack_thread`
- `schedule_slack_message`
- `list_scheduled_slack_messages`
- `delete_scheduled_slack_message`
- `update_slack_message`
- `delete_slack_message`
- `list_slack_pins`
- `pin_slack_message`
- `unpin_slack_message`
- `add_slack_reaction`
- `remove_slack_reaction`
- `list_slack_emoji`
- `get_slack_thread_replies`
- `list_slack_users`
- `get_slack_user_profile`
- `lookup_user_by_email`
- `open_slack_dm`
- `add_slack_bookmark`
- `add_slack_reminder`
- `list_slack_reminders`
- `complete_slack_reminder`
- `delete_slack_reminder`
- `list_slack_bookmarks`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server-slack\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@mindstone/mcp-server-slack\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 40, ceiling 64 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40mindstone%2Fmcp-server-slack
- Install plan: https://forgeregistry.com/api/v1/packages/%40mindstone%2Fmcp-server-slack/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40mindstone%2Fmcp-server-slack
- HTML page: https://forgeregistry.com/registry/%40mindstone%2Fmcp-server-slack
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.