Slack (vitruviansoftware) MCP Server
@vitruviansoftware/mcp-slack
npm
v1.0.3
Published by @vitruviansoftware — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
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 the deduction.
Findings 2
medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003
In the server's implementation (`dist/index.js:493`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://slack.com/api/${method}?${qs}`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
low Package has no source repositoryMTC-SUP-011
"@vitruviansoftware/mcp-slack" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package @vitruviansoftware/mcp-slack
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
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 |
|---|---|---|---|---|
v1.0.3 latest |
A 98/100 | 2 | 1.5.0 | 2026-07-22 |
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 @vitruviansoftware/mcp-slack --onlineOther implementations of Slack 24
Independent packages implementing the same tool, scanned with the same engine. Compare all 25 side by side →
Session-based, local-first Slack MCP server with 21 tools that works without OAuth.
Slack workspace MCP server covering channels, messages, threads, reactions, users, files, bookmarks, and message scheduling via the Slack Web API.
Security scan results for the Slack (avidian) MCP server.
Security scan results for the Slack (axivo) MCP server.
Security scan results for the Slack (korotovsky) MCP server.
Security scan results for the Slack (mintmcp) MCP server.
More in Communication & Collaboration
Security scan results for the Agent Recall MCP server.
Security scan results for the Agentcanary MCP server.
Security scan results for the Agy Discord MCP server.
Security scan results for the Ai Checker MCP server.
Security scan results for the Any Chat Completions MCP server.
Security scan results for the Arko MCP server.