Slack MCP (jtalk22/slack-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 21 tools. No publisher has claimed this listing.

B
Emerging
89/100
9 days ago

Slack MCP

Unlock full Slack access for your AI—DMs, private channels, threads, and search history. No OAuth apps or admin approval required. Session mirroring gives your AI the same access you already have.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Sandbox Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

jtalk22

Source: Smithery · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: CLOUDFLARE_API_TOKEN, SLACK_MCP_AUTH_TEST_URL. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: SLACK_API_KEY, SLACK_MCP_HTTP_AUTH_TOKEN, SLACK_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSLACK_API_KEY
configSLACK_COOKIE1. SLACK_TOKEN +
configSLACK_MCP_CHROME_PROFILEEach profile gets its own token file, Keychain entries, metadata, and lock. Add when the workspaces live in different Chrome profiles.
configSLACK_MCP_CHROME_USER_DATA_DIR
configSLACK_MCP_EXTRACTION_MODE
configSLACK_MCP_HTTP_ALLOWED_ORIGINS
🔐 secretSLACK_MCP_HTTP_AUTH_TOKEN
configSLACK_MCP_HTTP_INSECURE
configSLACK_MCP_KEYCHAIN_TIMEOUT_MS
configSLACK_MCP_NO_UPSELL
configSLACK_MCP_PROFILE
configSLACK_MCP_TOKEN_STORAGE
🔐 secretSLACK_TOKEN1. + SLACK_COOKIE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

All four hints declared on every tool

4/21 tools missing one or more hints — slack_smart_search (missing: destructiveHint); slack_catch_me_up (missing: destructiveHint); slack_triage (missing: destructiveHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

9/21 tools referenced in tests (43%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/jtalk22/slack-mcp-server)](https://m8ven.ai/mcp/jtalk22/slack-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 203bf37982037780e36687d5915eaa7d37f8f7c5
code hash: f25760afd5547d374f65536f5102ab74eb6bc8a4e9ad82735b37728d10b83bbb
verified: 9/1/2026, 8:47:53 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client