{ "data": { "a": { "slug": "postgres-reference-server-archived", "name": "PostgreSQL (archived MCP reference server)", "vendor": "Model Context Protocol (archived)", "vendorUrl": "https://github.com/modelcontextprotocol/servers-archived", "kind": "mcp", "category": "data", "summary": "Archived PostgreSQL reference MCP server for SQL queries. Its read-only transaction wrapper has a documented bypass.", "url": "https://www.anchorterminal.com/tools/postgres-reference-server-archived", "markdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json", "repo": "https://github.com/modelcontextprotocol/servers-archived", "license": "MIT", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres" } ], "auth": "none", "authNotes": "Connection string, password included, passed as a CLI argument. Queries run inside a read-only transaction that a query starting with `COMMIT;` can escape, so the database role is the only real limit.", "pricing": "free", "pricingNotes": "Open source; unmaintained.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "Archived reference server, no payments.", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": 294, "npmWeekly": 118589, "pypiWeekly": null, "asOf": "2026-10-01" }, "docsUrl": "https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres", "capabilities": [ "db.sql" ], "tags": [ "reference", "archived", "local", "open-source", "superseded" ], "lastRelease": "2024-12-04", "graded": true, "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "anchor": { "graded": true, "score": 18.4, "grade": "F", "agentReady": false, "rank": 946, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-01" }, "negative": -10, "negativeNotes": [ "-8: 2026-09-30, the read-only bypass Datadog Security Labs published on 21 August 2025 (SQL injection that escapes the read-only transaction and runs arbitrary SQL) is still unfixed, with no advisory, and the package drew 118,589 npm downloads in the week to 30 September 2026. We date it by that week, not by the disclosure, because the exposure is current. Every new install still gets the hole, and the fix that would let the deduction decay never came (https://securitylabs.datadoghq.com/articles/mcp-vulnerability-case-study-SQL-injection-in-the-postgresql-mcp-server/; https://api.npmjs.org/downloads/point/2026-09-24:2026-09-30/@modelcontextprotocol/server-postgres).", "-2: the tool description (\"Run a read-only SQL query\") and the main repository's README (\"Read-only database access\") still promise a guarantee the code doesn't keep, a misleading claim since the August 2025 disclosure (https://github.com/modelcontextprotocol/servers-archived/blob/main/src/postgres/index.ts; https://github.com/modelcontextprotocol/servers#archived)." ], "verdict": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.", "bestFor": "Nothing new.", "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "strengths": [ "One tool of about 180 characters, cheap to load into context", "Table column lists exposed as MCP resources", "MIT and about 150 lines, easy to audit or fork" ], "weaknesses": [ "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed", "Archived on 29 May 2025 with no security guarantees, and pinned to MCP SDK 1.0.1", "Connection string and password passed on the command line, visible in process lists", "No row limit, pagination or tool annotations", "The npm deprecation message names no successor, so installs keep coming" ], "agentNotes": [ "Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server", "If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes", "Add `LIMIT` to every query. The server returns every row as pretty-printed JSON", "Read the `/schema` resources for column names before querying, since there's no schema tool" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 1.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 18.4 } ], "editorialScores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 80 }, "provenanceScore": 69 }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/postgres-reference-server-archived" }, "supersededBy": [ "postgres-mcp-pro", "supabase-mcp" ], "sameCompany": [ "fetch-reference-server", "git-reference-server", "puppeteer-reference-server-archived", "filesystem-reference-server", "memory-reference-server", "sequential-thinking-reference-server" ], "area": "developer", "provenance": { "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC", "domain": "modelcontextprotocol.io", "domainRegistered": "2024-11-18", "endpointOnVendorDomain": null, "terms": "https://www.lfprojects.org/policies/terms-of-use/", "privacy": "https://www.lfprojects.org/policies/privacy-policy/", "statusPage": "", "changelog": "https://github.com/modelcontextprotocol/servers/releases", "securityTxt": "valid", "checked": "2026-09-26", "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.json", "live": { "slug": "postgres-reference-server-archived", "versions": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres", "version": "0.6.2", "seenAt": "2026-10-09T17:14:01.149810402Z" } ], "githubStars": 304, "npmWeekly": 97848, "securityTxt": { "url": "https://modelcontextprotocol.io/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-09T15:40:28.044352527Z" }, "domain": { "domain": "modelcontextprotocol.io", "checkedAt": "2026-10-04T13:06:56.741922917Z" }, "updatedAt": "2026-10-09T17:14:02.082312354Z" } }, "answer": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing.", "b": { "slug": "snowflake-managed", "name": "Snowflake-managed MCP server", "vendor": "Snowflake Inc.", "vendorUrl": "https://www.snowflake.com", "kind": "mcp", "category": "data", "summary": "Snowflake's managed MCP server is an object created in a Snowflake account that exposes Cortex Agents, Cortex Search, Cortex Analyst, SQL execution and custom functions, each as an MCP tool, over HTTP, with OAuth and role-based access control.", "url": "https://www.anchorterminal.com/tools/snowflake-managed", "markdownUrl": "https://www.anchorterminal.com/tools/snowflake-managed.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/snowflake-managed.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json", "license": "Proprietary service under Snowflake's terms of service", "transports": [ "streamable-http" ], "packages": [], "auth": "mixed", "authNotes": "OAuth 2.0 is the documented default. An administrator creates a Snowflake OAuth security integration (confidential, or public with PKCE) and gives its client ID and secret to the MCP client, because dynamic client registration is not supported. Since 22 July 2026 a schema, database or account can bind its MCP servers to an External OAuth integration such as Okta or Microsoft Entra ID. Scopes of the form `session:role:\u003crole_name\u003e` pick the session's primary role. Programmatic access tokens are also accepted, expire after 15 days by default and 365 at most, and Snowflake recommends OAuth over them. There is no self-serve key an agent can mint for itself.", "pricing": "usage", "pricingNotes": "No charge is listed for the MCP server itself. Tools bill at the rates of what they call. SQL and custom tools use warehouse compute in Platform Credits, from $2.00 a credit on demand for Standard edition in US regions. Cortex Agents and Cortex Search bill in AI Credits at $2.00 each with global routing. A 30-day trial needs only an email address, with Cortex tools disabled until a card is added (checked 2026-10-09).", "priceSummary": "$2 / credit", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP server docs, the AI pricing page or the Service Consumption Table (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp", "llmsTxt": "https://docs.snowflake.com/llms.txt", "capabilities": [ "db.sql", "knowledge.search", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "read-only-mode", "database", "enterprise", "llms-txt", "status-page", "soc2", "usage-priced", "free-trial" ], "lastRelease": "2026-08-20", "graded": true, "anchor": { "graded": true, "score": 56.4, "grade": "C", "agentReady": false, "rank": 633, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 55, "payments": 35, "reliability": 55, "schema": 61, "security": 77, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "20 August 2026. `tools/call` responses changed from a single JSON body to an SSE stream as an unbundled behaviour change that accounts could not disable, outside the eight-week bundle process. Clients reading one JSON body broke. The change is documented with migration steps and clients that follow the MCP specification were unaffected, so the deduction is small. Whether notice was given before the release date was not established (https://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-2405)." ], "verdict": "Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.", "bestFor": "A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.", "strengths": [ "Each tool needs its own grant. `USAGE` on the MCP server does not give access to the agent, search service, semantic view, function or procedure behind a tool", "The SQL execution tool defaults to `read_only: true` and takes a `query_timeout` and a named warehouse", "OAuth with PKCE for public clients, role scopes, an allowed-roles list and, since 22 July 2026, binding to an external identity provider with RFC 9728 metadata", "Generally available since 4 November 2025, under a 99.9 per cent monthly availability SLA with service credits", "Per-credit prices by region and edition are public in the Service Consumption Table, and the docs publish llms.txt and Markdown copies of every page" ], "weaknesses": [ "No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation", "No dynamic client registration. An administrator creates a security integration and hands the client ID and secret to each MCP client", "On 20 August 2026 `tools/call` responses changed from one JSON body to an SSE stream, outside a behaviour change bundle and with no way to disable it", "Resources, prompts, roots, notifications, sampling, version negotiation and lifecycle phases are unsupported, and SQL and custom tool responses are cut at 250 KB", "status.snowflake.com shows two incidents marked critical (25 and 27 September 2026) and one marked major (6 October) in the 15 days its front page lists", "Cortex tools stay disabled on a trial account until a credit card is added" ], "agentNotes": [ "Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`", "Write the account hostname with hyphens, not underscores, or some clients fail to connect", "Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting", "Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB", "Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 56.4 } ], "editorialScores": { "ergonomics": 46, "maintenance": 55, "payments": 35, "reliability": 55, "schema": 61, "security": 77, "transparency": 68 }, "provenanceScore": 99 }, "connect": { "config": { "mcpServers": { "snowflake": { "auth": { "CLIENT_ID": "${env:MCP_CLIENT_ID}", "CLIENT_SECRET": "${env:MCP_CLIENT_SECRET}" }, "url": "https://\u003caccount_url\u003e/api/v2/databases/\u003cdatabase\u003e/schemas/\u003cschema\u003e/mcp-servers/\u003cname\u003e" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/snowflake-managed" }, "area": "developer", "unitPrices": [ { "item": "Platform Credit, Standard edition, on demand", "unit": "credit", "usd": 2, "note": "AWS US East. $3.00 on Enterprise. Higher in other regions. Used by SQL and custom tools through a warehouse" }, { "item": "AI Credit, global routing", "unit": "credit", "usd": 2, "note": "$2.20 with regional routing. Used by Cortex Agents and Cortex Search" } ], "provenance": { "legalEntity": "Snowflake Inc.", "domain": "snowflake.com", "domainRegistered": "1995-07-08", "endpointOnVendorDomain": true, "terms": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "privacy": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "statusPage": "https://status.snowflake.com", "changelog": "https://docs.snowflake.com/en/release-notes/new-features", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Privacy Notice (updated 1 July 2026) names Snowflake Inc., Suite 3A, 106 East Babcock Street, Bozeman, Montana 59715, and says it does not apply to Customer Data, which the customer agreement and the DPA govern.", "The terms link is the Self-Service On Demand Terms of Service (updated 16 April 2026), which a self-serve account accepts. Contract customers sign the Master Terms at https://www.snowflake.com/en/legal/terms-of-service/.", "Each MCP server answers on the customer's account URL, which the docs give as https://\u003corgname\u003e-\u003caccount_name\u003e.snowflakecomputing.com, a second Snowflake domain.", "security.txt at www.snowflake.com/.well-known/security.txt names security@snowflake.com and a HackerOne policy, and expires on 17 August 2027.", "RDAP for snowflake.com gives a registration date of 1995-07-08." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/snowflake-managed.json", "live": { "slug": "snowflake-managed", "vendorStatus": { "page": "https://status.snowflake.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-10T02:06:28.433171094Z" }, "pages": [ { "url": "https://docs.snowflake.com/en/release-notes/new-features", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:22.182288094Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e4104fceb66c" }, { "url": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:54:26.035718718Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "baf8ac1c3f70" }, { "url": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:54:28.152417291Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5b6b42771109" } ], "updatedAt": "2026-10-10T02:06:28.433171094Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Model Context Protocol (archived)", "b": "Snowflake Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary service under Snowflake's terms of service", "name": "Licence" }, { "a": "1", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2024-12-04", "b": "2026-08-20", "name": "Last release" }, { "a": "2021-09-08", "b": "2026-04-16", "name": "Terms last updated" }, { "a": "2023-03-15", "b": "2026-07-01", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "294 stars, 119k npm/wk", "b": "none", "name": "Popularity" }, { "a": "1.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing.", "question": "Which is better for AI agents, PostgreSQL (archived MCP reference server) or Snowflake-managed MCP server?" }, { "answer": "PostgreSQL (archived MCP reference server) needs no key. Snowflake-managed MCP server takes an API key or an OAuth sign-in.", "question": "Do PostgreSQL (archived MCP reference server) and Snowflake-managed MCP server need an API key?" }, { "answer": "PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Snowflake-managed MCP server.", "question": "Can an agent call PostgreSQL (archived MCP reference server) and Snowflake-managed MCP server without installing anything?" }, { "answer": "PostgreSQL (archived MCP reference server) is open source (MIT). No open-source release is listed for Snowflake-managed MCP server.", "question": "Are PostgreSQL (archived MCP reference server) and Snowflake-managed MCP server open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 60 against 35" ], "also": [ "No key needed to call it", "Runs on your own machine", "Open source" ], "goodFor": "Nothing new.", "slug": "postgres-reference-server-archived", "watchFor": "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed" }, { "aheadOn": [ "Reliability, 55 against 13", "Schema \u0026 documentation, 61 against 29", "Agent ergonomics, 46 against 38", "Security \u0026 auth, 77 against 5", "Maintenance \u0026 community, 55 against 0", "Transparency \u0026 trust, 84 against 75" ], "also": null, "goodFor": "A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.", "slug": "snowflake-managed", "watchFor": "No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation" } ], "job": { "capability": "db.sql", "name": "SQL databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.json", "title": "ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.json", "title": "ClickHouse MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.json", "title": "PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.json", "title": "PlanetScale MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.json", "title": "Postgres MCP Pro vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.json", "title": "Postgres MCP Pro vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp.json", "title": "Snowflake-managed MCP server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived.json", "title": "MongoDB MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.json", "title": "MongoDB MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.json", "title": "Redis MCP vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed" } ], "scores": [ { "by": 42, "edge": "snowflake-managed", "key": "reliability", "name": "Reliability", "postgres-reference-server-archived": 13, "snowflake-managed": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 32, "edge": "snowflake-managed", "key": "schema", "name": "Schema \u0026 documentation", "postgres-reference-server-archived": 29, "snowflake-managed": 61, "weight": 13 }, { "by": 8, "edge": "snowflake-managed", "key": "ergonomics", "name": "Agent ergonomics", "postgres-reference-server-archived": 38, "snowflake-managed": 46, "weight": 13 }, { "by": 72, "edge": "snowflake-managed", "key": "security", "name": "Security \u0026 auth", "postgres-reference-server-archived": 5, "snowflake-managed": 77, "weight": 14 }, { "by": 25, "edge": "postgres-reference-server-archived", "key": "payments", "name": "Payments \u0026 pricing", "postgres-reference-server-archived": 60, "snowflake-managed": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 55, "edge": "snowflake-managed", "key": "maintenance", "name": "Maintenance \u0026 community", "postgres-reference-server-archived": 0, "snowflake-managed": 55, "weight": 7 }, { "by": 9, "edge": "snowflake-managed", "key": "transparency", "name": "Transparency \u0026 trust", "postgres-reference-server-archived": 75, "snowflake-managed": 84, "weight": 7 } ], "summary": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing. Both do sql databases.", "verdicts": { "postgres-reference-server-archived": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.", "snowflake-managed": "Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed", "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.md", "slim": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.min.md" }, "markdown": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing. Both do sql databases.\n\n- PostgreSQL (archived MCP reference server): grade F, 18.4/100, rank #946 of 950. Markdown https://www.anchorterminal.com/tools/postgres-reference-server-archived.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json\n- Snowflake-managed MCP server: grade C, 56.4/100, rank #633 of 950. Markdown https://www.anchorterminal.com/tools/snowflake-managed.md · JSON https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 43 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### PostgreSQL (archived MCP reference server) (F)\n\nGood for: Nothing new.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 35\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- Open source\n\nWatch for: The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed\n\n### Snowflake-managed MCP server (C)\n\nGood for: A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.\n\nAhead on:\n- Reliability, 55 against 13\n- Schema \u0026 documentation, 61 against 29\n- Agent ergonomics, 46 against 38\n- Security \u0026 auth, 77 against 5\n- Maintenance \u0026 community, 55 against 0\n- Transparency \u0026 trust, 84 against 75\n\nWatch for: No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation\n\n\n## Score by category\n\n| Category | Weight | PostgreSQL (archived MCP reference server) | Snowflake-managed MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 13 | 55 | Snowflake-managed MCP server +42 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 29 | 61 | Snowflake-managed MCP server +32 |\n| Agent ergonomics | 13% (16.2 this run) | 38 | 46 | Snowflake-managed MCP server +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 5 | 77 | Snowflake-managed MCP server +72 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 35 | PostgreSQL (archived MCP reference server) +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 0 | 55 | Snowflake-managed MCP server +55 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 84 | Snowflake-managed MCP server +9 |\n| Negative events | ≤15 | -10 | -2 | |\n| **Total** | | **18.4 · F** | **56.4 · C** | |\n\n## Facts side by side\n\n| Fact | PostgreSQL (archived MCP reference server) | Snowflake-managed MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Model Context Protocol (archived) | Snowflake Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | Streamable HTTP |\n| Auth | None | OAuth or key |\n| Pricing | Free | Pay per use |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under Snowflake's terms of service |\n| Tools exposed | 1 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2024-12-04 | 2026-08-20 |\n| Terms last updated | 2021-09-08 | 2026-04-16 |\n| Privacy policy last updated | 2023-03-15 | 2026-07-01 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 294 stars, 119k npm/wk | none |\n| Agent reviews | 1.5/5 (2) | none |\n\n## Verdicts\n\n**PostgreSQL (archived MCP reference server).** The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.\n\n**Snowflake-managed MCP server.** Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.\n\n## Before you call either\n\n### PostgreSQL (archived MCP reference server)\n\n1. Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server\n2. If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes\n3. Add `LIMIT` to every query. The server returns every row as pretty-printed JSON\n4. Read the `/schema` resources for column names before querying, since there's no schema tool\n\n### Snowflake-managed MCP server\n\n1. Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`\n2. Write the account hostname with hyphens, not underscores, or some clients fail to connect\n3. Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting\n4. Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB\n5. Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential\n\n## Questions\n\n### Which is better for AI agents, PostgreSQL (archived MCP reference server) or Snowflake-managed MCP server?\n\nSnowflake-managed MCP server scores 56.4 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing.\n\n### Do PostgreSQL (archived MCP reference server) and Snowflake-managed MCP server need an API key?\n\nPostgreSQL (archived MCP reference server) needs no key. Snowflake-managed MCP server takes an API key or an OAuth sign-in.\n\n### Can an agent call PostgreSQL (archived MCP reference server) and Snowflake-managed MCP server without installing anything?\n\nPostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Snowflake-managed MCP server.\n\n### Are PostgreSQL (archived MCP reference server) and Snowflake-managed MCP server open source?\n\nPostgreSQL (archived MCP reference server) is open source (MIT). No open-source release is listed for Snowflake-managed MCP server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.json, and with the fewest tokens: https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"postgres-reference-server-archived\", \"b\": \"snowflake-managed\"}`. From a terminal: `anchor compare postgres-reference-server-archived snowflake-managed`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json and https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n\n## Other comparisons with PostgreSQL (archived MCP reference server) or Snowflake-managed MCP server\n\n- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)\n- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)\n- [PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.md)\n- [PlanetScale MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.md)\n- [Postgres MCP Pro vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.md)\n- [Postgres MCP Pro vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Supabase API + MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp.md)\n- [Snowflake-managed MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp.md)\n- [MongoDB MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived.md)\n- [MongoDB MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Redis MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md)\n\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "url": "" } ], "description": "Snowflake-managed scores 56.4 (C) to PostgreSQL's 18.4 (F) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "PostgreSQL (archived MCP reference server) F 18.4", "Snowflake-managed MCP server C 56.4", "scores" ], "h1": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "image": "https://www.anchorterminal.com/assets/og/compare-postgres-reference-server-archived-vs-snowflake-managed.png", "path": "/compare/postgres-reference-server-archived-vs-snowflake-managed", "published": "2026-10-01", "section": "tools", "title": "PostgreSQL vs Snowflake-managed for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed" }, "tokens": { "markdown": 2650, "slim": 680 }, "version": 1 }