Simple Snowflake MCP Server to work behind a corporate proxy
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"simple-snowflake-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Simple Snowflake MCP server **Enhanced Snowflake MCP Server with comprehensive configuration system and full MCP protocol compliance.** A production-ready MCP server that provides seamless Snowflake integration with advanced features including configurable logging, resource subscriptions, and comprehensive error handling. Designed to work seamlessly behind corporate proxies. ## 🆕 What's new in v0.3.0 This release focuses on security hardening and reliability. See [CHANGELOG.md](CHANGELOG.md) for the full list. - **Server-governed read-only mode.** Read-only is decided solely by server config / `MCP_READ_ONLY`; the client `read_only` argument has been **removed**. All SQL funnels through one guard that strips comments and rejects multi-statement and CTE-fronted DML. - **No silent data loss.** Row-producing reads without a `LIMIT` are capped at `default_query_limit`, and a capped result now returns an explicit *"results were truncated"* notice instead of dropping rows silently. - **Stays responsive under load.** Blocking Snowflake I/O runs on a worker thread, plus an in-process rate limit and a server-side statement timeout. - **Hardened inputs.** `pattern`/`database` are allow-list validated before `LIKE`; `limit` is a bounded integer applied at the driver (never concatenated into SQL). Snowflake errors are not leaked to clients. - **New `security` config block** (`rate_limit`, `notes` bounds) and `snowflake.statement_timeout_seconds` / `connection_reuse`. - Documentation and in-code comments are now entirely in English. > ⚠️ **Breaking:** the client `read_only` tool argument has been removed — read-only mode is now governed solely by the server. `execute-snowflake-sql` is now subject to the read-only guard (it was previously unguarded), so write/DDL statements are rejected while the server is in read-only mode. (The README previously documented several tools — `query-view`, `list-schemas`, `describe-table`, etc. — that were never actually implemented; the …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.