slack@0.6.2
CAUTION· install onlyPublisher claims: "Interact with Slack Workspaces over the Slack API." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso astral.sh — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-14 and scored it 76/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Collapsed <details> block carrying instructions; Collapsed <details> block carrying instructions. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
kill -0 "$SERVER_PID" 2>/dev/null || { echo "server exited before listening" >&2; exit 1; }Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.npx -y @modelcontextprotocol/[email protected] --web --protocol-era legacy -- \Fix: Pin versions and sources; vendor anything fetched at install time.return { ...env, ...(server.env?.(ctx) ?? {}), ...extra };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.group (`detached: true`) and kill the group when the script ends, so theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.`MEMORY_FILE_PATH=… npx …` has no effect on the server; pass it with `-e`:Fix: Pin versions and sources; vendor anything fetched at install time.trap 'kill "$SERVER_PID" 2>/dev/null' EXIT # stops it however the subshell endsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.<summary>Using Docker</summary> ```json { "mcp": { "servers": { "time": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/time"] } } } } ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.npx -y @modelcontextprotocol/[email protected] --web --protocol-era modern -- \Fix: Pin versions and sources; vendor anything fetched at install time.INSPECT="npx -y @modelcontextprotocol/inspector --cli"Fix: Pin versions and sources; vendor anything fetched at install time.<summary>Using docker</summary> ```json { "mcpServers": { "fetch": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/fetch"] } } } ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary>Using Docker</summary> ```json { "mcp": { "servers": { "fetch": { "command": "docker", "args": ["run", "-i", "--rm", "mcp/fetch"] } } } } ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.env: envFor(server, ctx, {}, installed?.env),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary>Using docker</summary> ```json { "mcpServers": { "time": { "command": "docker", "args": ["run", "-i", "--rm", "-e", "LOCAL_TIMEZONE", "mcp/time"] } } }Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.installed?.env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx -y ./src/sequentialthinking # the workspace's bin, from its dist/Fix: Pin versions and sources; vendor anything fetched at install time.- **Pace every write loop** by `AGENTS.md` **Pacing GitHub writes**, andFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.echo "mcp-server-$s $v $(curl -s -o /dev/null -w '%{http_code}' "https://pypi.org/pypi/mcp-server-$s/$v/json")"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.<summary>Using docker</summary> * Note: replace '/Users/username' with a path that you want to be accessible by this tool * Note: the `-e` lines set the identitFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.npx -y @modelcontextprotocol/inspector --cli <server command> [-- ] <inspector options>Fix: Pin versions and sources; vendor anything fetched at install time.// Ctrl-C and a plain kill are the obvious ones; Ctrl-\ (SIGQUIT) is the oneFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// undefined for any other path. npx and npm install the server underFix: Pin versions and sources; vendor anything fetched at install time.// so arguments go through the same `winShellArgs` quoting the npm/npx callFix: Pin versions and sources; vendor anything fetched at install time."build": "tsc && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.// and npm treats that tree as its own: a reinstall, an update or a cleared npxFix: Pin versions and sources; vendor anything fetched at install time.(code === 0 ? console.log : console.error)(output);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."build": "tsc && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.env: { ...process.env, ...env },Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* @param {{ spawnFn?: typeof spawn, killProcess?: typeof process.kill }} [io]Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own."which npm manages: reinstalling or updating the server, or clearing the npx cache, " +Fix: Pin versions and sources; vendor anything fetched at install time.{ spawnFn = spawn, killProcess = process.kill } = {},Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.* client dir up the node_modules tree exactly as `npx --no-install tsc` walkedFix: Pin versions and sources; vendor anything fetched at install time.RUN apt-get update && apt-get install -y git git-lfs && rm -rf /var/lib/apt/lists/* \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."build": "tsc && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.RUN mkdir /data && chown node:node /dataFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.// the umask can only narrow that. The chmod then restores any bits theFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts."build": "tsc && shx cp -r docs dist/ && shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
4 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim modelcontextprotocol: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.