com.mcparmory/slack
OCI · GHCR.IO/MCPARMORY/SLACK:1.0.1 · 2 COMPONENTS · SCANNED SEP 20
Manage channels, conversations, users, and workspace apps programmatically
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 7167 tokens (~99/item across 72 items; 72 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety95
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 11 of 14 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_me_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 72 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/slack MCP server?
com.mcparmory/slack runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/slack:1.0.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/slack:1.0.1
claude mcp add com-mcparmory-slack -- docker run --rm -i ghcr.io/mcparmory/slack:1.0.1
{
"mcpServers": {
"com-mcparmory-slack": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/slack:1.0.1"
]
}
}
} {
"servers": {
"com-mcparmory-slack": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/slack:1.0.1"
]
}
}
} codex mcp add com-mcparmory-slack -- docker run --rm -i ghcr.io/mcparmory/slack:1.0.1
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-slack": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/slack:1.0.1"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-slack:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/slack:1.0.1"] {
"McpServers": {
"com-mcparmory-slack": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/slack:1.0.1"
]
}
}
} {
"mcpServers": {
"com-mcparmory-slack": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/slack:1.0.1"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/slack:1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
open_direct_message Open Direct Message ~142
Opens or resumes a direct message conversation, either a 1:1 DM with a single user or a multi-person DM with multiple users. The conversation is created if it doesn't exist, or resumed if it already does.
| Name | Type | Req | Description |
|---|---|---|---|
| return_im | boolean | – | When true, returns the complete direct message channel definition in the response, including all channel metadata and settings. |
| users | string | – | Comma-separated list of user identifiers to include in the direct message. Provide a single user for a 1:1 DM, or multiple users for a group DM. The order of users is preserved in the returned conver… |
No output schema declared.
No examples provided.
remove_pin_from_channel Remove Pin from Channel ~79
Removes a pinned message from a channel. Specify the channel and optionally the message timestamp to un-pin.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | The channel ID or name where the pinned item is located. |
| timestamp | string | – | The timestamp of the specific message to un-pin. If omitted, the most recently pinned message in the channel will be removed. |
No output schema declared.
No examples provided.
remove_reaction Remove Reaction ~162
Removes an emoji reaction from a message or file comment. Specify either a message timestamp or file comment ID to identify the target item.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel where the message to remove reaction from was posted. |
| file | string | – | File to remove reaction from. |
| file_comment | string | – | The file comment ID from which to remove the reaction. Use this when removing a reaction from a file comment instead of a message. |
| name | string | yes | The emoji name of the reaction to remove (e.g., 'thumbsup', 'heart'). Must match the exact reaction name. |
| timestamp | string | – | The message timestamp identifying which message to remove the reaction from. Use this when removing a reaction from a message instead of a file comment. |
No output schema declared.
No examples provided.
remove_star Remove Star ~112
Removes a star from a specific item, such as a file comment or message. Requires authentication with stars:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel to remove star from, or channel where the message to remove star from was posted (used with `timestamp`). |
| file_comment | string | – | The file comment to remove the star from. Either this or timestamp must be provided. |
| timestamp | string | – | The timestamp of the message to remove the star from. Either this or file_comment must be provided. |
No output schema declared.
No examples provided.
remove_user_from_conversation Remove User From Conversation ~61
Removes a specified user from a conversation, effectively ending their participation in that conversation thread.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | ID of conversation to remove user from. |
| user | string | – | The unique identifier of the user to be removed from the conversation. |
No output schema declared.
No examples provided.
revoke_file_public_url Revoke File Public URL ~38
Revokes public and external sharing access for a file, preventing further access via public URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | File to revoke |
No output schema declared.
No examples provided.
schedule_message Schedule Message ~330
Schedules a message to be delivered to a channel at a specified future time. The message content and formatting can be customized with optional parameters for parsing, unfurling, and threading.
| Name | Type | Req | Description |
|---|---|---|---|
| as_user | boolean | – | When true, posts the message as the authenticated user instead of as a bot. Defaults to false. |
| channel | string | – | Channel, private group, or DM channel to send message to. Can be an encoded ID, or a name. See [below](#channels) for more details. |
| parse | string | – | Controls how the message text is processed. Defaults to 'none'. Options include 'full' for markdown-style formatting and 'mrkdwn' for Slack's markup syntax. |
| post_at | string | – | Unix EPOCH timestamp indicating when the message should be sent. Must be a future time. |
| reply_broadcast | boolean | – | When true, makes a threaded reply visible to all channel members. Only applies when thread_ts is provided. Defaults to false. |
| text | string | – | The message content to send. Required unless using blocks or other content structures. See formatting documentation for supported syntax options. |
| thread_ts | number | – | The timestamp of a parent message to make this message a threaded reply. Use the parent message's timestamp, not a reply's timestamp. |
| unfurl_links | boolean | – | When true, enables automatic expansion of text-based links (URLs, articles, etc.) into rich previews. |
| unfurl_media | boolean | – | When false, prevents automatic expansion of media content (images, videos, etc.) in the message. |
No output schema declared.
No examples provided.
search_messages Search Messages ~132
Searches for messages matching a query string, with optional result highlighting and sorting capabilities. Returns matching messages from the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| highlight | boolean | – | Enable query highlight markers in results to visually distinguish matched terms within message content. |
| query | string | yes | Search query string to match against message content. Supports the platform's standard search syntax. |
| sort | string | – | Sort results by relevance score or message timestamp. Defaults to score-based sorting if not specified. |
| sort_dir | string | – | Sort direction for results: ascending (`asc`) for oldest/lowest first, or descending (`desc`) for newest/highest first. |
No output schema declared.
No examples provided.
send_ephemeral_message Send Ephemeral Message ~264
Sends an ephemeral message visible only to a specific user in a channel. Ephemeral messages disappear after the user refreshes and are useful for temporary notifications or interactive responses.
| Name | Type | Req | Description |
|---|---|---|---|
| as_user | boolean | – | When true, posts the message as the authenticated user; when false, posts as the bot. Defaults based on available scopes. |
| channel | string | yes | Target channel, private group, or direct message channel. Accepts encoded channel ID or channel name. |
| parse | string | – | Controls message formatting interpretation. Set to `none` by default to treat text literally, or use other values to enable special formatting. |
| text | string | – | Message content. Required unless using block-based formatting. Supports text, mentions, and links depending on the `parse` setting. |
| thread_ts | string | – | Parent message timestamp to post this message as a reply in a thread. Use the parent message's `ts` value, not a reply's timestamp. Only visible if the thread is already active. |
| user | string | yes | User ID of the recipient. The user must be a member of the specified channel to receive the ephemeral message. |
| username | string | – | Custom display name for the bot. Only applies when `as_user` is false; ignored otherwise. |
No output schema declared.
No examples provided.
send_me_message Send Me Message ~90
Send a me message (action message) to a channel. Me messages are typically used to share actions or emotes in a conversational context.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel to send message to. Can be a public channel, private group or IM channel. Can be an encoded ID, or a name. |
| text | string | – | The text content of the me message to send to the channel. |
No output schema declared.
No examples provided.
send_message_to_channel Send Message to Channel ~313
Sends a message to a Slack channel, private group, or direct message. Supports threaded replies, formatting options, and customizable authorship.
| Name | Type | Req | Description |
|---|---|---|---|
| as_user | string | – | When true, posts the message as the authenticated user instead of as a bot. Defaults to false. |
| channel | string | yes | Target destination for the message: a channel name, private group name, or encoded channel/user ID. |
| mrkdwn | boolean | – | When false, disables Slack markup parsing. Enabled by default to allow formatting. |
| parse | string | – | Controls message formatting behavior. Defaults to `none`; see API documentation for available options. |
| reply_broadcast | boolean | – | When true and used with `thread_ts`, makes the threaded reply visible to all channel members instead of just the thread participants. |
| text | string | – | Message content. Required unless using blocks or other content fields. Supports text and Slack markup when `mrkdwn` is enabled. |
| thread_ts | string | – | Timestamp of the parent message to create a threaded reply. Use the parent message's timestamp, not a reply's timestamp. |
| unfurl_links | boolean | – | When true, enables automatic unfurling of text-based content links in the message. |
| unfurl_media | boolean | – | When false, prevents automatic unfurling of media content (images, videos, etc.) in the message. |
| username | string | – | Custom display name for the bot. Only used when `as_user` is false; ignored otherwise. |
No output schema declared.
No examples provided.
unarchive_conversation Unarchive Conversation ~42
Restores an archived conversation to active status, reversing the archival action and making it accessible again.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | ID of conversation to unarchive |
No output schema declared.
No examples provided.
update_call Update Call ~127
Updates the join URLs and other metadata for an existing Call, allowing you to modify how clients access the call.
| Name | Type | Req | Description |
|---|---|---|---|
| desktop_app_join_url | string | – | A direct launch URL for the 3rd-party Call application on desktop clients. When provided, Slack clients will attempt to open the call directly using this URL instead of the standard join_url. |
| id | string | yes | The unique identifier of the Call to update, as returned by the calls.add method. |
| join_url | string | – | The URL that clients use to join the Call. This is the primary join link for the call. |
No output schema declared.
No examples provided.
update_conversation Rename Conversation ~55
Updates the name of an existing conversation. This operation allows you to rename a conversation to better organize or identify it.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | ID of conversation to rename |
| name | string | – | New name for conversation. |
No output schema declared.
No examples provided.
update_conversation_purpose Update Conversation Purpose ~75
Updates the purpose or topic description for a conversation. This helps organize and clarify the conversation's intent.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation to set the purpose of |
| purpose | string | – | The new purpose or topic description for the conversation. Provide a clear, concise statement that describes the conversation's intent or focus. |
No output schema declared.
No examples provided.
update_conversation_topic Update Conversation Topic ~74
Updates the topic for a conversation. The topic is a plain text string used to label or describe the conversation's subject matter.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Conversation to set the topic of |
| topic | string | – | The new topic string for the conversation. Plain text only; formatting and linkification are not supported. |
No output schema declared.
No examples provided.
update_message Update Message ~198
Updates the text and formatting of an existing message in a channel. Requires the message timestamp and channel ID to identify which message to update.
| Name | Type | Req | Description |
|---|---|---|---|
| as_user | string | – | Set to `true` to update the message as the authenticated user (applies to bot users as well). Defaults to `false` if not specified. |
| channel | string | yes | The channel ID containing the message to be updated. |
| parse | string | – | Controls how the message content is parsed. Use `none` to disable formatting or `full` to enable all formatting rules. Defaults to `client` if not specified; omitting this parameter will reset to the… |
| text | string | – | The new message text using standard formatting rules. Not required if `blocks` or `attachments` are being provided instead. |
| ts | string | yes | The timestamp (ts) of the message to be updated, used to uniquely identify the message within the channel. |
No output schema declared.
No examples provided.
update_user_presence Update User Presence ~64
Manually set a user's presence status to either active (auto) or away. Requires authentication with users:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| presence | string | yes | Presence status to set for the user. Must be either 'auto' for active presence or 'away' for away status. |
No output schema declared.
No examples provided.
update_usergroup Update Usergroup ~158
Update an existing User Group's properties such as handle, description, and associated channels. Requires usergroups:write scope.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | string | – | A comma-separated list of encoded channel IDs to set as defaults for this User Group. |
| description | string | – | A brief description of the User Group's purpose or membership. |
| handle | string | – | A unique mention handle for the User Group. Must be distinct across all channels, users, and other User Groups in the workspace. |
| include_count | boolean | – | When enabled, the response will include the total count of users currently in the User Group. |
| usergroup | string | yes | The encoded ID of the User Group to update. This identifier is required to target the correct group. |
No output schema declared.
No examples provided.
update_usergroup_users Update Usergroup Users ~119
Update the complete membership of a User Group by replacing all users with a new list of user IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| include_count | boolean | – | When true, the response will include a count of the total number of users in the User Group. |
| usergroup | string | yes | The encoded ID of the User Group to update. This identifies which group's membership will be replaced. |
| users | string | yes | A comma-separated list of encoded user IDs that defines the complete new membership for the User Group. All previous members not in this list will be removed. |
No output schema declared.
No examples provided.
users_set_photo Set User Photo ~89
Set the user profile photo
| Name | Type | Req | Description |
|---|---|---|---|
| crop_w | string | – | Width/height of crop box (always square) |
| crop_x | string | – | X coordinate of top-left corner of crop box |
| crop_y | string | – | Y coordinate of top-left corner of crop box |
| image | string | – | Base64-encoded file content for upload. File contents via `multipart/form-data`. |
No output schema declared.
No examples provided.
verify_authentication Verify Authentication ~28
Verifies that the provided authentication token is valid and returns information about the authenticated user or application.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.mcparmory/slack MCP server?
com.mcparmory/slack is an MCP server listed in the public MCP registry as com.mcparmory/slack. Manage channels, conversations, users, and workspace apps programmatically. This page covers its container image (ghcr.io/mcparmory/slack:1.0.1).
Is the com.mcparmory/slack MCP server safe to use?
com.mcparmory/slack scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/slack MCP server expose?
com.mcparmory/slack exposes 72 tools: verify_authentication, get_bot_info, update_call, delete_message, delete_scheduled_message, and 67 more. Their descriptions and schemas cost roughly 7,167 tokens of context every time the server is loaded.
Is the com.mcparmory/slack MCP server still maintained?
com.mcparmory/slack is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.