LeashIndex Get the report

Index / messaging

Slack

io-github-mindstone-mcp-server-slack declares 39 capabilities across 39 tools, with 2 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

99/100 exposureHigh exposure

Manifest recorded 2026-11-02 from tools/list answered by the npm package @mindstone/mcp-server-slack@0.3.5 (published to npm as @mindstone/mcp-server-slack, listed in the official MCP registry as io.github.mindstone/mcp-server-slack 0.3.5), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · irreversible-uncapped · 22 of 39 tools

22 tools are classified as irreversible or destructive and declare no limit. 19 of them are counted only because the server annotated them destructiveHint. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

critical · no-revocation · All 39 tools

39 of 39 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

high · no-expiry · All 39 tools

39 of 39 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 39 tools

39 of 39 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

low · uncapped-read · 17 of 39 tools

17 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
authenticate_slack_workspacesend inferred
list_slack_workspacesread declared
search_slack_messagesread declared
get_slack_saved_messagesread declared
get_slack_message_by_linkread declared
send_myself_a_notesend inferred
compose_slack_messagesend inferred
post_slack_messagedestructive declared
reply_to_slack_threaddestructive declared
schedule_slack_messagedestructive declared
list_scheduled_slack_messagesread declared
delete_scheduled_slack_messagedestructive declared
update_slack_messagedestructive declared
delete_slack_messagedestructive declared
list_slack_channelsread declared
get_slack_channel_historyread declared
create_slack_channeldestructive declared
mark_slack_channel_as_readdestructive declared
get_slack_unread_messagesread declared
invite_user_to_channeldestructive declared
get_slack_thread_repliesread declared
add_slack_reactiondestructive declared
remove_slack_reactiondestructive declared
list_slack_emojiread declared
list_slack_usersread declared
get_slack_user_profileread declared
lookup_user_by_emailread declared
open_slack_dmdestructive declared
download_slack_fileread declared
upload_slack_filedestructive declared
list_slack_pinsread declared
pin_slack_messagedestructive declared
unpin_slack_messagedestructive declared
add_slack_bookmarkdestructive declared
add_slack_reminderdestructive declared
list_slack_remindersread declared
complete_slack_reminderdestructive declared
delete_slack_reminderdestructive declared
list_slack_bookmarksread declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-2999 tools/list answered by the npm package @mindstone/mcp-server-slack@0.3.1 (published to npm as @mindstone/mcp-server-slack, listed in the official MCP registry as io.github.mindstone/mcp-server-slack 0.3.1), run in an isolated container with no network access and placeholder credentials
2026-10-2799 tools/list answered by the npm package @mindstone/mcp-server-slack@0.3.0 (published to npm as @mindstone/mcp-server-slack, listed in the official MCP registry as io.github.mindstone/mcp-server-slack 0.3.0), run in an isolated container with no network access and placeholder credentials
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.