Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/christianclaudio/mcp-server-snowflakeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/christianclaudio/mcp-server-snowflake/snowflake)<a href="https://agentmods.dev/mcp/christianclaudio/mcp-server-snowflake/snowflake"><img src="https://agentmods.dev/badge/mcp/christianclaudio/mcp-server-snowflake/snowflake.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
snowflake scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"snowflake": {
"command": "uvx",
"args": [
"mcp-server-snowflake"
],
"env": {
"SNOWFLAKE_ACCOUNT": "",
"SNOWFLAKE_USER": "",
"SNOWFLAKE_PASSWORD": "",
"SNOWFLAKE_TOKEN": "",
"SNOWFLAKE_PRIVATE_KEY_PATH": "",
"SNOWFLAKE_PRIVATE_KEY_RAW": "",
"SNOWFLAKE_PRIVATE_KEY_PASSPHRASE": "",
"SNOWFLAKE_AUTHENTICATOR": "",
"SNOWFLAKE_CONNECTION_NAME": "",
"SNOWFLAKE_ROLE": "",
"SNOWFLAKE_WAREHOUSE": "",
"SNOWFLAKE_DATABASE": "",
"SNOWFLAKE_SCHEMA": "",
"SNOWFLAKE_MCP_READONLY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 24 lines scan A a0e380fa657d
snowflake is an MCP server published in the GitHub repository christianclaudio/mcp-server-snowflake (0 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
airtable-mcp-server
Read and write access to Airtable database schemas, tables, and records. Runs locally from the airtable-mcp-server npm package. Needs 1 environment variable to run.
mcp-turso-cloud
MCP server for integrating Turso with LLMs. Runs locally from the mcp-turso-cloud npm package. Needs 5 environment variables to run.
postgres
MCP server "postgres" as configured in gabrimatic/mcp-web-search-tool. Runs in Docker (mcp/postgres).
sqlike-mcp
SQL static analysis & query-equivalence for Postgres, MySQL, SQLite, and SQL Server. Runs locally from the @sqlike/mcp npm package. Needs 1 environment variable to run.
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.
database-mcp-mariadb
MCP server for MariaDB. Read-only by default, row caps, timeouts, secrets never logged. Runs locally from the @database-mcp/mariadb npm package. Needs 4 environment variables to run.