Slack Crunchtools MCP Server
mcp-slack-crunchtools
PyPI
v0.1.3
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Secure read-only MCP server for Slack workspaces
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Hardcoded Slack token in test/example/packaging MTC-SRC-008 | exfiltration |
2. Client adoption risk — 99 − 5 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Hardcoded Slack token in test/example/packaging (tests/test_tools.py)MTC-SRC-008
A hardcoded Slack token (a live-looking credential hardcoded in shipped code) appears in `tests/test_tools.py:68`. Verify whether this is a real credential; if so, remove and rotate it.
Evidence: Slack token: xoxp…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server tests/test_tools.py
Tools 15
Each tool and what it can reach — statically extracted from the published source.
slack_list_filesreads sensitive dataslack_auth_testno sensitive capabilityslack_get_channel_historyno sensitive capabilityslack_get_channel_infono sensitive capabilityslack_get_file_infono sensitive capabilityslack_get_reactionsno sensitive capabilityslack_get_thread_repliesno sensitive capabilityslack_get_user_infono sensitive capabilityslack_get_user_profileno sensitive capabilityslack_list_channel_membersno sensitive capability
Show 5 more tools ↓
slack_list_channelsno sensitive capabilityslack_list_reactionsno sensitive capabilityslack_list_starsno sensitive capabilityslack_list_usersno sensitive capabilityslack_search_messagesno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.3 latest |
A 94/100 | 1 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-slack-crunchtools --online --registry pypiMore in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.