MCP server · trust report

io.github.mindstone/mcp-server-slack

Passes 3 checks with a soft flag on supply chain and version behavior — worth a look, not a dealbreaker.

Publisher
io.github.mindstone
Repository
github.com/mindstone/mcp-servers
Install
npm:@mindstone/mcp-server-slack, npm:@mindstone/mcp-server-slack, npm:@mindstone/mcp-server-slack, npm:@mindstone/mcp-server-slack, npm:@mindstone/mcp-server-slack, npm:@mindstone/mcp-server-slack
Versions
6
Inspected
5 of 6 checks · 90%
Scored
2026-09-03 · rubric 1.0.0

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

6 checks3 clean2 flagged1 not inspected
  • Injection surface

    pass25% of grade

    Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

    Scanned 245 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

  • Supply chain

    warn25% of grade

    Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

    install hook "prepare" present and not a recognized benign build command

  • Credential hygiene

    pass15% of grade

    How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

    No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    pass15% of grade

    Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

    No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

  • Version behavior

    warn10% of grade

    Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

    vs prior 0.2.0 (minor bump): new tool "authenticate_slack_workspace" appeared; new tool "list_slack_workspaces" appeared; new tool "search_slack_messages" touches a sensitive surface (email/exec/net/fs); new tool "get_slack_saved_messages" touches a sensitive surface (email/exec/net/fs); new tool "get_slack_message_by_link" touches a sensitive surface (email/exec/net/fs); new tool "send_myself_a_note" touches a sensitive surface (email/exec/net/fs); new tool "compose_slack_message" touches a sensitive surface (email/exec/net/fs); new tool "post_slack_message" touches a sensitive surface (email/exec/net/fs); new tool "reply_to_slack_thread" appeared; new tool "schedule_slack_message" appeared; new tool "list_scheduled_slack_messages" touches a sensitive surface (email/exec/net/fs); new tool "delete_scheduled_slack_message" touches a sensitive surface (email/exec/net/fs); new tool "update_slack_message" appeared; new tool "delete_slack_message" touches a sensitive surface (email/exec/net/fs); new tool "list_slack_channels" appeared; new tool "get_slack_channel_history" touches a sensitive surface (email/exec/net/fs); new tool "create_slack_channel" appeared; new tool "mark_slack_channel_as_read" touches a sensitive surface (email/exec/net/fs); new tool "get_slack_unread_messages" touches a sensitive surface (email/exec/net/fs); new tool "invite_user_to_channel" touches a sensitive surface (email/exec/net/fs); new tool "get_slack_thread_replies" touches a sensitive surface (email/exec/net/fs); new tool "add_slack_reaction" appeared; new tool "remove_slack_reaction" appeared; new tool "list_slack_emoji" touches a sensitive surface (email/exec/net/fs); new tool "list_slack_users" touches a sensitive surface (email/exec/net/fs); new tool "get_slack_user_profile" appeared; new tool "lookup_user_by_email" touches a sensitive surface (email/exec/net/fs); new tool "open_slack_dm" touches a sensitive surface (email/exec/net/fs); new tool "download_slack_file" touches a sensitive surface (email/exec/net/fs); new tool "upload_slack_file" touches a sensitive surface (email/exec/net/fs); new tool "list_slack_pins" appeared; new tool "pin_slack_message" appeared; new tool "unpin_slack_message" appeared; new tool "add_slack_bookmark" appeared; new tool "add_slack_reminder" appeared; new tool "list_slack_reminders" touches a sensitive surface (email/exec/net/fs); new tool "complete_slack_reminder" appeared; new tool "delete_slack_reminder" touches a sensitive surface (email/exec/net/fs); new tool "list_slack_bookmarks" appeared.

  • Transport config

    unscannable10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v0.3.0 · current2026-08-06 B82.55/6 · 90%±0
v0.2.02026-07-30 B87.53/6 · 55%±0
v0.1.62026-06-12 B87.53/6 · 55%±0
v0.1.42026-06-10 B87.53/6 · 55%