io.github.CloudCorpRecords/channelchat
NPM · @RENETURCIOS/CHANNELCHAT · 2 COMPONENTS
Slack channels, messages, threads, reactions and users via the Slack Web API.
Available components
Last scanned (1 hour ago)
Scores higher than 34% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 470 tokens (~58/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 64
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/@reneturcios/channelchat@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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_add_reaction ~75
Add a reaction emoji to a message in a Slack channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | ID of the Slack channel containing the message to react to. |
| reaction | string | yes | Name of the emoji reaction to add, without colons. |
| timestamp | string | yes | Timestamp of the message to add the reaction to. |
No output schema declared.
No examples provided.
slack_get_channel_history ~49
Get recent messages from a Slack channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | ID of the Slack channel to get message history from. |
| limit | number | – | Maximum number of messages to return. |
No output schema declared.
No examples provided.
slack_get_thread_replies ~57
Get all replies in a message thread in a Slack channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | ID of the Slack channel containing the thread. |
| thread_ts | string | yes | Timestamp of the parent message whose thread replies are returned. |
No output schema declared.
No examples provided.
slack_get_user_profile ~36
Get the profile of a specific Slack user.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | ID of the Slack user whose profile is returned. |
No output schema declared.
No examples provided.
slack_get_users ~57
Get a list of all users in a Slack workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous response, used to fetch the next page of users. |
| limit | number | – | Maximum number of users to return per page. |
No output schema declared.
No examples provided.
slack_list_channels ~71
List public or private channels in a Slack workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_archived | boolean | – | Whether to exclude archived channels from the results. |
| limit | number | – | Maximum number of channels to return. |
| types | string | – | Comma-separated channel types to list, such as public_channel or private_channel. |
No output schema declared.
No examples provided.
slack_post_message ~49
Post a new message to a Slack channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | ID of the Slack channel to post the message to. |
| text | string | yes | Text of the message to post. |
No output schema declared.
No examples provided.
slack_reply_to_thread ~76
Reply to a specific message thread in a Slack channel.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | ID of the Slack channel containing the thread to reply to. |
| text | string | yes | Text of the reply message to post in the thread. |
| thread_ts | string | yes | Timestamp of the parent message whose thread the reply belongs to. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/channelchat MCP server?
io.github.CloudCorpRecords/channelchat runs locally as an npm package, launched with npx -y @reneturcios/channelchat. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/channelchat
claude mcp add cloudcorprecords-channelchat -- npx -y @reneturcios/channelchat
What is the io.github.CloudCorpRecords/channelchat MCP server?
io.github.CloudCorpRecords/channelchat is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/channelchat. Slack channels, messages, threads, reactions and users via the Slack Web API. This page covers its npm package (@reneturcios/channelchat).
Is the io.github.CloudCorpRecords/channelchat MCP server safe to use?
io.github.CloudCorpRecords/channelchat scores 66 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/channelchat MCP server expose?
io.github.CloudCorpRecords/channelchat exposes 8 tools: slack_list_channels, slack_post_message, slack_reply_to_thread, slack_add_reaction, slack_get_channel_history, and 3 more. Their descriptions and schemas cost roughly 470 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/channelchat MCP server still maintained?
io.github.CloudCorpRecords/channelchat is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.CloudCorpRecords/channelchat MCP server under?
io.github.CloudCorpRecords/channelchat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.