Slack_connect
NPM · @PIPEWORX/MCP-SLACK_CONNECT · 2 COMPONENTS
Slack MCP Pack
Available components
Last scanned (20 hours ago)
Scores higher than 77% of npm servers
Category Communication
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-slack_connect). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 414 tokens (~82/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "slack_send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 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
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.
- 4 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-slack_connect@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-slack_connect |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-slack_connect/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692352923 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:08d589b1fc44735b2804a36400aaf10f76f58713d36ec114362a2e797e92277ea8acf0e208d0d2707f62dc753bcf5742e9a83b499d81434ae19377fe2 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
slack_channel_history ~106
Get message history from a Slack channel. Bot auto-joins the channel if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel ID (e.g., "C01234ABCDE") |
| cursor | string | – | Pagination cursor for next page of results |
| latest | string | – | Only messages before this Unix timestamp |
| limit | number | – | Max number of messages to return (default 20, max 1000) |
| oldest | string | – | Only messages after this Unix timestamp |
No output schema declared.
No examples provided.
slack_join_channel ~35
Join a public Slack channel so the bot can read history and post messages.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel ID to join |
No output schema declared.
No examples provided.
slack_list_channels ~89
List channels in the Slack workspace. Returns channel names, IDs, and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor for next page of results |
| limit | number | – | Max number of channels to return (default 100, max 1000) |
| types | string | – | Comma-separated channel types: public_channel, private_channel, mpim, im (default "public_channel") |
No output schema declared.
No examples provided.
slack_list_users ~61
List users in the Slack workspace. Returns user profiles, IDs, and status.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor for next page of results |
| limit | number | – | Max number of users to return (default 100, max 1000) |
No output schema declared.
No examples provided.
slack_send_message ~70
Send a message to a Slack channel. Bot auto-joins the channel if needed.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | Channel ID to send the message to |
| text | string | yes | Message text (supports Slack markdown) |
| thread_ts | string | – | Thread timestamp to reply in a thread (optional) |
No output schema declared.
No examples provided.
How do I install the Slack_connect MCP server?
Slack_connect runs locally as an npm package, launched with npx -y @pipeworx/mcp-slack_connect. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-slack_connect
claude mcp add pipeworx-io-slack-connect -- npx -y @pipeworx/mcp-slack_connect
What is the Slack_connect MCP server?
Slack_connect is an MCP server listed in the public MCP registry as io.github.pipeworx-io/slack_connect. Slack MCP Pack. This page covers its npm package (@pipeworx/mcp-slack_connect).
Is the Slack_connect MCP server safe to use?
Slack_connect scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Slack_connect MCP server expose?
Slack_connect exposes 5 tools: slack_list_channels, slack_channel_history, slack_send_message, slack_list_users, slack_join_channel. Their descriptions and schemas cost roughly 361 tokens of context every time the server is loaded.
Is the Slack_connect MCP server still maintained?
Slack_connect is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Slack_connect MCP server under?
Slack_connect declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.