What are the risks of connecting to npm:@jtalk22/slack-mcp?

References sensitive file paths / environment secrets. Overall trust grade C- (72/100).

When was npm:@jtalk22/slack-mcp last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

C-

npm:@jtalk22/slack-mcp

Item: npm:@jtalk22/slack-mcp
Rating: 72
Author: wmcp.sh

https://www.npmjs.com/package/@jtalk22/slack-mcp

72/100 · MCP Trust Grade · checked 1mo ago · MCP 4.3.0

Is the npm:@jtalk22/slack-mcp MCP server safe to use?

Independent trust grade C- (72/100). References sensitive file paths / environment secrets. wmcp.sh continuously watches npm:@jtalk22/slack-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 29 tools · Productivity

slack_token_status

slack_health_check

slack_refresh_tokens

slack_list_conversations

slack_conversations_history

slack_get_full_conversation

slack_search_messages

slack_users_info

slack_send_message

slack_get_thread

slack_list_users

slack_add_reaction

slack_remove_reaction

slack_conversations_mark

slack_conversations_unreads

slack_users_search

slack_workflow_save

slack_workflows

+11 more tools

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 29 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
uses eval/exec/child_process (review for unsanitized input)
scanned 6 source files

Maintenance / popularity20%100

published within 90 days
35 published versions

Tool hygiene15%70

no TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package @jtalk22/slack-mcp@4.3.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@jtalk22/slack-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@jtalk22/slack-mcp grade C-

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40jtalk22%2Fslack-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C-](https://wmcp.sh/mcp/grade/npm%3A%40jtalk22%2Fslack-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40jtalk22%2Fslack-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40jtalk22%2Fslack-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3A%40jtalk22%2Fslack-mcp/badge.svg" alt="MCP Trust Grade C- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.