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.
npx agentmods add mcp/uniquejtx/snowflake-generic-mcp/snowflake-python-venvgit clone --depth 1 https://github.com/uniquejtx/snowflake-generic-mcpWrote 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/uniquejtx/snowflake-generic-mcp/snowflake-python-venv)<a href="https://agentmods.dev/mcp/uniquejtx/snowflake-generic-mcp/snowflake-python-venv"><img src="https://agentmods.dev/badge/mcp/uniquejtx/snowflake-generic-mcp/snowflake-python-venv.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
snowflake-python-venv 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 3d 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-python-venv": {
"command": "/path/to/your/snowflake-mcp-server/venv/bin/python",
"args": [
"/path/to/your/snowflake-mcp-server/snowflake_mcp_server.py"
]
}
}What else claude_desktop_config.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 3d ago First seen · 8 lines scan A 6d67238b26ca
snowflake-python-venv is an MCP server published in the GitHub repository uniquejtx/snowflake-generic-mcp (4 stars, last pushed 1y ago), licensed MIT. 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
mcp-snowflake-server
A Snowflake MCP server — SQL queries, schema exploration, and data insights for AI assistants. Runs locally from the mcp-snowflake-server-nsp Python package. Needs 15 environment variables to run.
snowflake
A simple Snowflake MCP server. Runs locally from the mcp-server-snowflake Python package. Needs 14 environment variables to run.
snowflake-tools
MCP server "snowflake-tools" as configured in StringNLPLAB/FlexSQL. Runs src/mcp_server.py with .venv/bin/python. Needs 2 environment variables to run.
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.
mcp-server-mysql
MCP server "mcp-server-mysql" as configured in Kurok1/mcp-server-mysql. Runs in Docker (ghcr.io/kurok1/mcp-server-mysql:2.0.0). Needs 1 environment variable to run.
elastic-mcp
Model Context Protocol server for Elasticsearch (search, index inspection, cluster info; read-only by default with optional write tools). Runs locally from the elastic-mcp npm package.