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/mcp-tg/snowflake-developer-kit/snowflake-mcp-servergit clone --depth 1 https://github.com/mcp-tg/snowflake-developer-kitWrote 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/mcp-tg/snowflake-developer-kit/snowflake-mcp-server)<a href="https://agentmods.dev/mcp/mcp-tg/snowflake-developer-kit/snowflake-mcp-server"><img src="https://agentmods.dev/badge/mcp/mcp-tg/snowflake-developer-kit/snowflake-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
snowflake-mcp-server 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 4d 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-mcp-server": { "command": "uvx", "args": [ "snowflake-mcp-server" ] } }
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.
- 4d ago First seen · 8 lines scan A edf91f365aee
snowflake-mcp-server is an MCP server published in the GitHub repository mcp-tg/snowflake-developer-kit (0 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
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.
mcp-database-server
Add your description here. Runs locally from the mcp-database-server Python package.
sql-server-mcp
Local, single-user MCP server for read-only SQL Server / MS Fabric queries - one process per tenant. Runs locally from the sql-server-mcp Python package.
mcp-opensearch
Read-only MCP server for OpenSearch and OpenSearch Dashboards. Runs locally from the mcp-opensearch Python package.
android-sqlite-mcp
A Model Context Protocol (MCP) server to connect AI agents directly to the embedded SQLite/Room databases of your Android applications. Runs locally from the android-sqlite-mcp npm package.
mcp-server-neon
Lets the agent create and manage Neon Postgres projects, branches and databases and run SQL. Runs locally from the @neondatabase/mcp-server-neon npm package.