snowflake-labs-mcp@1.4.2
VERIFIED· not startedPublisher claims: "MCP server for Snowflake" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified 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
SNOWFLAKE_PASSWORDSNOWFLAKE_PATSNOWFLAKE_PRIVATE_KEYSNOWFLAKE_PRIVATE_KEY_FILESNOWFLAKE_PRIVATE_KEY_FILE_PWDor--passcode-in-passwordConfiguration, not credentials: SNOWFLAKE_ACCOUNT, SNOWFLAKE_DEFAULT_CONNECTION_NAME, SNOWFLAKE_HOST, SNOWFLAKE_MCP_ENDPOINT, SNOWFLAKE_MCP_HOST, SNOWFLAKE_MCP_PORT, SNOWFLAKE_MCP_VERBOSE, SNOWFLAKE_PASSCODE, SNOWFLAKE_ROLE, SNOWFLAKE_USER, SNOWFLAKE_WAREHOUSE- Where it talks to
- no vendor host named in the codeAlso snowflake.com, snowflakecomputing.com — 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names snowflake.com, snowflakecomputing.com as well as its own vendor. The guard injects SNOWFLAKE_PASSWORD, SNOWFLAKE_PAT, SNOWFLAKE_PRIVATE_KEY, SNOWFLAKE_PRIVATE_KEY_FILE, SNOWFLAKE_PRIVATE_KEY_FILE_PWD only into requests to the host you bind (and its subdomains) and refuses the rest.
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 (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 90/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
… -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher && sudo mv mcp-publisher /usr/local/bin/ echo "$HOME/.local/bin" >> $GITHUB_PATH…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.CMD ["mcp-server-snowflake", "--service-config-file", "/app/services/tools_config.yaml", "--transport", "streamable-http", "--endpoint", "/snowflake-mcp"]Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for snowflake-labs-mcp@1.4.2 as of 58 min ago. This is the package itself, not its dependencies.