{ "data": { "a": { "slug": "neon-mcp", "name": "Neon MCP Server", "vendor": "Neon (Databricks)", "vendorUrl": "https://neon.com/docs/ai/neon-mcp-server", "kind": "mcp", "category": "data", "summary": "Neon's official remote MCP server at mcp.neon.tech/mcp lets agents manage Neon Postgres projects, branches, roles and computes, run SQL and migrations on temporary branches, and configure Neon Auth, Data API and storage, through OAuth or an API key.", "url": "https://www.anchorterminal.com/tools/neon-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/neon-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neon-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neon-mcp.json", "dns": "neon-mcp.grade.anchorterminal.com", "repo": "https://github.com/neondatabase/mcp-server-neon", "license": "MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.neon.tech/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.1 with dynamic client registration or Client ID Metadata Documents, advertising `read` and `write` scopes; the consent screen lets the user untick writes and pick one project, a Postgres role and tool categories, or a parameterised URL fixes that grant. A Neon API key in a Bearer header also works, with readonly, projectId, category and roleName read from the URL on each request. The `neon mcp` CLI command can mint a key for the server. The local stdio package is deprecated.", "pricing": "freemium", "pricingNotes": "The MCP server is free; Neon usage is billed. The Free plan is $0 with no card (100 projects, 100 CU-hours and 0.5 GB storage per project, 1 GB storage). Launch and Scale are pay as you go, compute $0.106 a CU-hour on Launch and $0.222 on Scale, storage $0.35 a GB-month.", "priceSummary": "$0.106 / unit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP server, docs or pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 138, "popularity": { "githubStars": 663, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://neon.com/docs/ai/neon-mcp-server", "llmsTxt": "https://neon.com/llms.txt", "openapi": "https://neon.com/docs/reference/api-reference", "registryName": "com.neon/mcp", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "hosted", "freemium", "mcp", "remote-mcp", "oauth", "mcp-registry", "llms-txt", "openapi", "postgres", "read-only-mode", "branching", "databricks" ], "lastRelease": "2026-11-05", "graded": true, "anchor": { "graded": true, "score": 72.5, "grade": "BB", "agentReady": true, "rank": 125, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 80, "payments": 40, "reliability": 72, "schema": 90, "security": 69, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.", "bestFor": "Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.", "strengths": [ "OAuth 2.1 with read and write scopes, and grants fixed to one project, one Postgres role and chosen categories", "Read-only mode runs SQL in READ ONLY transactions and withholds connection strings", "Migrations and query tuning run on a temporary branch before they touch the main one", "Descriptions say how to resolve IDs and which tools must never run without the user", "MIT source, dated CHANGELOG and com.neon/mcp in the official registry at 2.0.0" ], "weaknesses": [ "138 tools listed when no category or project is set", "The README says it isn't recommended for production databases", "Segment receives account ID, name and email on connect, with no opt-out on the hosted server", "The MCP server has no status component and no stated release stage", "No security.txt on neon.com" ], "agentNotes": [ "Connect with ?category=querying\u0026category=schema\u0026projectId=... or untick Allow writes at consent to cut 138 tools to a handful", "Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing", "Pass branch IDs (br-...), not names; call list_branches to resolve a name", "On 429 back off exponentially, and on 423 Locked wait for the running operation to finish" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.5 } ], "editorialScores": { "ergonomics": 79, "maintenance": 80, "payments": 40, "reliability": 72, "schema": 90, "security": 69, "transparency": 79 }, "provenanceScore": 71, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http neon https://mcp.neon.tech/mcp", "config": { "mcpServers": { "Neon": { "url": "https://mcp.neon.tech/mcp?readonly=true" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/neon-mcp" }, "area": "developer", "unitPrices": [ { "item": "Compute, Launch", "unit": "compute-unit", "usd": 0.106, "note": "Per CU-hour" }, { "item": "Compute, Scale", "unit": "compute-unit", "usd": 0.222, "note": "Per CU-hour" }, { "item": "Storage", "unit": "gb-month", "usd": 0.35, "note": "Launch and Scale" } ], "provenance": { "legalEntity": "Neon, LLC (subsidiary of Databricks, Inc.)", "domain": "neon.com", "domainRegistered": "1994-08-18", "endpointOnVendorDomain": false, "terms": "https://neon.com/terms-of-service", "privacy": "https://neon.com/privacy-policy", "statusPage": "https://neonstatus.com", "changelog": "https://github.com/neondatabase/mcp-server-neon/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The MCP endpoint is on mcp.neon.tech, Neon's older domain, while docs and legal pages are on neon.com.", "The Neon product schedule, last updated 14 October 2026, is between Databricks, Inc., the parent company of Neon, LLC, and the customer. The privacy notice is Databricks', last updated 9 January 2026.", "neon.com/security lists annual SOC 2 Type II audits with a public SOC 3 report, ISO 27001, ISO 27701, HIPAA, GDPR and CCPA.", "neon.com/.well-known/security.txt returns 404.", "neon.com/robots.txt allows all and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. mcp.neon.tech has no robots.txt.", "RDAP gives neon.com a registration date of 18 August 1994; the domain predates Neon." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/neon-mcp.json", "live": { "slug": "neon-mcp", "probe": { "target": "https://mcp.neon.tech/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T19:22:21.502866963Z", "lastOk": true, "lastStatus": 401, "lastMs": 151, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 147, "p95ms24h": 366, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://neonstatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:15.209607696Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.neon/mcp", "version": "2.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 663, "securityTxt": { "url": "https://neon.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:24.319288694Z" }, "llmsTxt": { "url": "https://neon.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:18.8105724Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/neondatabase/mcp-server-neon/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:22:07.888479491Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "22d617e6b187" }, { "url": "https://neon.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:57.338873736Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c96cd96f185b" }, { "url": "https://neon.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:59.695502864Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d25bd3a3dc6e" } ], "mcpTools": { "url": "https://mcp.neon.tech/mcp", "checkedAt": "2026-11-07T01:52:00.41377208Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-03T22:16:15.261722522Z" }, "updatedAt": "2026-11-07T19:22:21.502866963Z" } }, "answer": "Neon MCP Server scores 72.5 (BB) on agent readiness against Snowflake-managed MCP server's 52.7 (D), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security \u0026 auth and transparency \u0026 trust.", "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", "dns": "snowflake-managed.grade.anchorterminal.com", "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": 52.7, "grade": "D", "agentReady": false, "rank": 978, "ranked": true, "rankOf": 1510, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 35, "payments": 35, "reliability": 50, "schema": 61, "security": 77, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -3, "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, and clients reading one JSON body broke. The only dated notice recorded is the behaviour change note dated 20 August, the day the change took effect, so it takes the same-day -3 (the 9 October check charged -2). Per the 9 October check, not re-read on 4 November (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, with no way to disable it and no earlier dated notice found", "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": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.7 } ], "editorialScores": { "ergonomics": 46, "maintenance": 35, "payments": 35, "reliability": 50, "schema": 61, "security": 77, "transparency": 68 }, "provenanceScore": 99, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "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-11-07T19:23:43.43476569Z" }, "securityTxt": { "url": "https://snowflake.com/.well-known/security.txt", "state": "valid", "expires": "2027-08-17T19:00:00.000Z", "checkedAt": "2026-11-07T16:00:39.831604087Z" }, "llmsTxt": { "url": "https://docs.snowflake.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:58.213669404Z" }, "domain": { "domain": "snowflake.com", "registered": "1995-07-08", "source": "https://rdap.verisign.com/com/v1/domain/snowflake.com", "checkedAt": "2026-11-01T14:11:27.42351034Z" }, "pages": [ { "url": "https://docs.snowflake.com/en/release-notes/new-features", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:08:04.843173451Z", "changedAt": "2026-11-07T14:08:04.843173451Z", "fingerprint": "91d64a1e3041" }, { "url": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:34:55.792924408Z", "changedAt": "2026-11-06T13:55:24.956430204Z", "fingerprint": "36988bbe7385" }, { "url": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:34:57.839669214Z", "changedAt": "2026-11-06T13:55:27.763689662Z", "fingerprint": "42d8071a6e9d" } ], "updatedAt": "2026-11-07T19:23:43.43476569Z" } }, "edges": [ { "by": 45, "category": "maintenance", "leads": "neon-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 80.", "b": "Per the 9 October check, not re-read on 4 November (snowflake.com's site terms bar robots). The last dated change to the MCP server is the SSE note of 20 August 2026, 76 days before 4 November, and platform release notes ran to 9 October (20). Of the three dated MCP entries recorded (22 July, 7 August and 20 August 2026), two fall in the 90 days from 6 August, and newer entries couldn't be looked for (0, cause time). A public changelog and a support route through cases and the community, whose answers were not sampled (10). The managed server is not in the official MCP registry, which lists only the separate open-source `io.github.Snowflake-Labs/mcp` (0). Nothing to install. The REST API specification repository was last updated on 10 September 2026 (5). 20+0+10+0+5 = 35." }, "scores": { "a": 80, "b": 35 } }, { "by": 33, "category": "ergonomics", "leads": "neon-mcp", "name": "Agent ergonomics", "reasons": { "a": "138 tools with no grant, far over 30 (5), with category, projectId and readonly to cut the list (plus 10). List tools take limits and cursors from the API, and describe_branch returns a tree (16). API errors return with their kind and status, path errors are tool errors, and unknown categories come back as a notice (16). readOnlyHint and destructiveHint on every definition, and the grant filter tells the model never to run destructive tools autonomously (18). Official TypeScript and Python SDKs for the Neon API; a no-auth tool preview endpoint (14). 15 + 16 + 16 + 18 + 14 = 79.", "b": "The tool list is whatever the operator declares, up to 50 a server, and Snowflake recommends one Cortex Agent tool per server with further servers for other uses (18). The search tool takes `columns` and `limit`. SQL and custom tool responses are cut at 250 KB with no paging, and agent tool responses carry every intermediate step and can pass 200 KB (8). Errors are documented as a symptom table, and `invalid_client` covers both wrong credentials and a network policy block (6). The SQL tool is read-only by default. No `readOnlyHint` or `destructiveHint` annotations and no idempotency support are documented (6). Few required arguments and standard MCP clients work with no SDK, but each client needs a hand-made OAuth integration and some clients can't choose a role (8). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 79, "b": 46 } }, { "by": 29, "category": "schema", "leads": "neon-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not (\"branch_id is a branch id, not a branch name. Call list_branches to resolve a name\", \"NEVER run autonomously\") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.", "b": "No OpenAPI or published schema covers the MCP endpoint, and the snowflake-rest-api-specs repository has no MCP server file. Custom tools carry a JSON Schema the operator writes in `input_schema`, and built-in tools take fixed arguments shown only as examples. The schemas `tools/list` returns were not read (15). llms.txt and a Markdown copy of every docs page (10). Tool names and descriptions are written by the operator, and Snowflake's own examples are one line each, such as \"cortex search service for all products\" (8). Typed inputs for custom tools, with free-text SQL and a single `message` string for the analyst and agent tools (8). Request and response examples for two tool types, a troubleshooting table and OAuth failure modes, with no JSON-RPC error codes and an empty object as the search response example (8). Dated release notes, behaviour change notes and a stated protocol revision of 2025-11-25 (12). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 90, "b": 61 } }, { "by": 22, "category": "reliability", "leads": "neon-mcp", "name": "Reliability", "reasons": { "a": "Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.", "b": "Graded as a hosted service. Snowflake's site terms (14 April 2025) bar robots, spiders and scrapers on snowflake.com, so the docs, the status page and www.snowflake.com were not re-read on 4 November and the 9 October readings stand. Statuspage at status.snowflake.com with components by cloud region, and no component for Cortex or the MCP server was recorded (15, the value for a vendor status page with no component for the product). Only the front page's 15 days to 9 October were read, with two incidents marked critical (one region for 68 minutes on 25 September 2026, other regions for 35 minutes on 27 September), one marked major (Snowsight connectivity, 6 October) and one minor (8 October). The rest of the window from 6 August is unread and gets no credit, so the incident line is held at the recorded 10. No rate limit for the MCP endpoint found (0). The REST API's OpenAPI files describe 429 and retry with backoff, but the MCP page gives no retry or idempotency guidance (5, partial value held). 99.9 per cent monthly SLA with service credits (10). Generally available since 4 November 2025 (10). 15+10+0+5+10+10 = 50." }, "scores": { "a": 72, "b": 50 } }, { "by": 9, "category": "transparency", "leads": "snowflake-managed", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.", "b": "Closed service with clear published terms, an acceptable use policy and a consumption table (15). A DPA and Security Addendum of 11 January 2026 with 72-hour incident notice and customer-chosen regions. The DPA says leftover data is deleted promptly after termination without a day count, and the Privacy Notice excludes Customer Data (22). A written behaviour change policy with an eight-week bundle period and dated notes, though the August 2026 MCP change shipped outside it (15). Four sub-processors and 28 affiliates listed with locations and 28 days' notice of additions. AI model providers are not named on the list (16). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 75, "b": 84 } }, { "by": 8, "category": "security", "leads": "snowflake-managed", "name": "Security \u0026 auth", "reasons": { "a": "OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.", "b": "OAuth 2.0 with PKCE, role scopes, an allowed-roles list, binding to an external identity provider and RFC 9728 metadata. Programmatic access tokens expire (15 days by default, 365 at most), can be rotated and need a network policy by default. No dynamic client registration (28). Each tool needs its own grant, the SQL tool defaults to read-only, and the docs advise a separate least-privileged server for direct SQL. No confirmation step for writes is documented (15). The docs warn about tool poisoning, tool shadowing and recursive loops and cap recursion at 10. Nothing covers instructions arriving in query or search results (6). Account Usage has query, login and access history and a Cortex Agent usage view. No log of MCP tool calls was found (10). security.txt valid to 17 August 2027 with a HackerOne policy, SOC 2 Type II, ISO 27001, HITRUST and FedRAMP per the Security Addendum. The HackerOne page was not read (18). Per the 9 October check, not re-read on 4 November." }, "scores": { "a": 69, "b": 77 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Neon (Databricks)", "b": "Snowflake Inc.", "name": "Vendor" }, { "a": "https://mcp.neon.tech/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "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": "138", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.neon/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-11-05", "b": "2026-08-20", "name": "Last release" }, { "a": "2026-10-14", "b": "2026-04-16", "name": "Terms last updated" }, { "a": "2026-01-09", "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": "663 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Neon MCP Server scores 72.5 (BB) on agent readiness against Snowflake-managed MCP server's 52.7 (D), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security \u0026 auth and transparency \u0026 trust.", "question": "Which is better for AI agents, Neon MCP Server or Snowflake-managed MCP server?" }, { "answer": "Neon MCP Server uses an OAuth sign-in. Snowflake-managed MCP server takes an API key or an OAuth sign-in.", "question": "Do Neon MCP Server and Snowflake-managed MCP server need an API key?" }, { "answer": "Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp. No hosted endpoint is listed for Snowflake-managed MCP server.", "question": "Can an agent call Neon MCP Server and Snowflake-managed MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 50", "Schema \u0026 documentation, 90 against 61", "Agent ergonomics, 79 against 46", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 80 against 35" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "No incidents deducted, where Snowflake-managed MCP server loses 3 points for them" ], "goodFor": "Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.", "slug": "neon-mcp", "watchFor": "138 tools listed when no category or project is set" }, { "aheadOn": [ "Security \u0026 auth, 77 against 69", "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" } ], "history": { "neon-mcp": null, "snowflake-managed": [ { "causes": [ "correction", "time" ], "date": "2026-11-04", "delta": -3.7, "from": 56.4, "fromGrade": "C", "to": 52.7, "toGrade": "D" } ] }, "job": { "capability": "db.sql", "name": "SQL databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.json", "title": "ClickHouse MCP Server vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp" }, { "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/dbhub-vs-neon-mcp.json", "title": "DBHub vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-snowflake-managed.json", "title": "DBHub vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.json", "title": "MCP Toolbox for Databases vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-snowflake-managed.json", "title": "MCP Toolbox for Databases vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.json", "title": "Neon MCP Server vs ObsessionDB", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.json", "title": "Neon MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.json", "title": "Neon MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.json", "title": "Neon MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.json", "title": "Neon MCP Server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.json", "title": "ObsessionDB vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed" }, { "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-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-snowflake-managed.json", "title": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed" }, { "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-neon-mcp.json", "title": "MongoDB MCP Server vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp" }, { "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/neon-mcp-vs-redis-mcp.json", "title": "Neon MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.json", "title": "Neon MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-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" }, { "json": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.json", "title": "ReqRes MCP server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed" } ], "panel": null, "scores": [ { "by": 22, "edge": "neon-mcp", "key": "reliability", "name": "Reliability", "neon-mcp": 72, "snowflake-managed": 50, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 29, "edge": "neon-mcp", "key": "schema", "name": "Schema \u0026 documentation", "neon-mcp": 90, "snowflake-managed": 61, "weight": 13 }, { "by": 33, "edge": "neon-mcp", "key": "ergonomics", "name": "Agent ergonomics", "neon-mcp": 79, "snowflake-managed": 46, "weight": 13 }, { "by": 8, "edge": "snowflake-managed", "key": "security", "name": "Security \u0026 auth", "neon-mcp": 69, "snowflake-managed": 77, "weight": 14 }, { "by": 5, "edge": "neon-mcp", "key": "payments", "name": "Payments \u0026 pricing", "neon-mcp": 40, "snowflake-managed": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 45, "edge": "neon-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "neon-mcp": 80, "snowflake-managed": 35, "weight": 7 }, { "by": 9, "edge": "snowflake-managed", "key": "transparency", "name": "Transparency \u0026 trust", "neon-mcp": 75, "snowflake-managed": 84, "weight": 7 } ], "summary": "Neon MCP Server scores 72.5 (BB) on agent readiness against Snowflake-managed MCP server's 52.7 (D), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security \u0026 auth and transparency \u0026 trust. Both do sql databases.", "tasks": null, "tutorials": [], "verdicts": { "neon-mcp": "OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.", "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/neon-mcp-vs-snowflake-managed", "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.min.md" }, "markdown": "Neon MCP Server scores 72.5 (BB) on agent readiness against Snowflake-managed MCP server's 52.7 (D), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security \u0026 auth and transparency \u0026 trust. Both do sql databases.\n\n- Neon MCP Server: grade BB, 72.5/100, rank #125 of 1510. Markdown https://www.anchorterminal.com/tools/neon-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neon-mcp.json\n- Snowflake-managed MCP server: grade D, 52.7/100, rank #978 of 1510. 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 111 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### Neon MCP Server (BB)\n\nGood for: Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.\n\nAhead on:\n- Reliability, 72 against 50\n- Schema \u0026 documentation, 90 against 61\n- Agent ergonomics, 79 against 46\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 80 against 35\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Snowflake-managed MCP server loses 3 points for them\n\nWatch for: 138 tools listed when no category or project is set\n\n### Snowflake-managed MCP server (D)\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- Security \u0026 auth, 77 against 69\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## Why the edge\n\n### Maintenance \u0026 community: Neon MCP Server +45\n\n- Neon MCP Server (80): v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 80.\n- Snowflake-managed MCP server (35): Per the 9 October check, not re-read on 4 November (snowflake.com's site terms bar robots). The last dated change to the MCP server is the SSE note of 20 August 2026, 76 days before 4 November, and platform release notes ran to 9 October (20). Of the three dated MCP entries recorded (22 July, 7 August and 20 August 2026), two fall in the 90 days from 6 August, and newer entries couldn't be looked for (0, cause time). A public changelog and a support route through cases and the community, whose answers were not sampled (10). The managed server is not in the official MCP registry, which lists only the separate open-source `io.github.Snowflake-Labs/mcp` (0). Nothing to install. The REST API specification repository was last updated on 10 September 2026 (5). 20+0+10+0+5 = 35.\n\n### Agent ergonomics: Neon MCP Server +33\n\n- Neon MCP Server (79): 138 tools with no grant, far over 30 (5), with category, projectId and readonly to cut the list (plus 10). List tools take limits and cursors from the API, and describe_branch returns a tree (16). API errors return with their kind and status, path errors are tool errors, and unknown categories come back as a notice (16). readOnlyHint and destructiveHint on every definition, and the grant filter tells the model never to run destructive tools autonomously (18). Official TypeScript and Python SDKs for the Neon API; a no-auth tool preview endpoint (14). 15 + 16 + 16 + 18 + 14 = 79.\n- Snowflake-managed MCP server (46): The tool list is whatever the operator declares, up to 50 a server, and Snowflake recommends one Cortex Agent tool per server with further servers for other uses (18). The search tool takes `columns` and `limit`. SQL and custom tool responses are cut at 250 KB with no paging, and agent tool responses carry every intermediate step and can pass 200 KB (8). Errors are documented as a symptom table, and `invalid_client` covers both wrong credentials and a network policy block (6). The SQL tool is read-only by default. No `readOnlyHint` or `destructiveHint` annotations and no idempotency support are documented (6). Few required arguments and standard MCP clients work with no SDK, but each client needs a hand-made OAuth integration and some clients can't choose a role (8). Per the 9 October check, not re-read on 4 November.\n\n### Schema \u0026 documentation: Neon MCP Server +29\n\n- Neon MCP Server (90): Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not (\"branch_id is a branch id, not a branch name. Call list_branches to resolve a name\", \"NEVER run autonomously\") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.\n- Snowflake-managed MCP server (61): No OpenAPI or published schema covers the MCP endpoint, and the snowflake-rest-api-specs repository has no MCP server file. Custom tools carry a JSON Schema the operator writes in `input_schema`, and built-in tools take fixed arguments shown only as examples. The schemas `tools/list` returns were not read (15). llms.txt and a Markdown copy of every docs page (10). Tool names and descriptions are written by the operator, and Snowflake's own examples are one line each, such as \"cortex search service for all products\" (8). Typed inputs for custom tools, with free-text SQL and a single `message` string for the analyst and agent tools (8). Request and response examples for two tool types, a troubleshooting table and OAuth failure modes, with no JSON-RPC error codes and an empty object as the search response example (8). Dated release notes, behaviour change notes and a stated protocol revision of 2025-11-25 (12). Per the 9 October check, not re-read on 4 November.\n\n### Reliability: Neon MCP Server +22\n\n- Neon MCP Server (72): Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.\n- Snowflake-managed MCP server (50): Graded as a hosted service. Snowflake's site terms (14 April 2025) bar robots, spiders and scrapers on snowflake.com, so the docs, the status page and www.snowflake.com were not re-read on 4 November and the 9 October readings stand. Statuspage at status.snowflake.com with components by cloud region, and no component for Cortex or the MCP server was recorded (15, the value for a vendor status page with no component for the product). Only the front page's 15 days to 9 October were read, with two incidents marked critical (one region for 68 minutes on 25 September 2026, other regions for 35 minutes on 27 September), one marked major (Snowsight connectivity, 6 October) and one minor (8 October). The rest of the window from 6 August is unread and gets no credit, so the incident line is held at the recorded 10. No rate limit for the MCP endpoint found (0). The REST API's OpenAPI files describe 429 and retry with backoff, but the MCP page gives no retry or idempotency guidance (5, partial value held). 99.9 per cent monthly SLA with service credits (10). Generally available since 4 November 2025 (10). 15+10+0+5+10+10 = 50.\n\n### Transparency \u0026 trust: Snowflake-managed MCP server +9\n\n- Neon MCP Server (75): MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.\n- Snowflake-managed MCP server (84): Closed service with clear published terms, an acceptable use policy and a consumption table (15). A DPA and Security Addendum of 11 January 2026 with 72-hour incident notice and customer-chosen regions. The DPA says leftover data is deleted promptly after termination without a day count, and the Privacy Notice excludes Customer Data (22). A written behaviour change policy with an eight-week bundle period and dated notes, though the August 2026 MCP change shipped outside it (15). Four sub-processors and 28 affiliates listed with locations and 28 days' notice of additions. AI model providers are not named on the list (16). Per the 9 October check, not re-read on 4 November.\n\n### Security \u0026 auth: Snowflake-managed MCP server +8\n\n- Neon MCP Server (69): OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.\n- Snowflake-managed MCP server (77): OAuth 2.0 with PKCE, role scopes, an allowed-roles list, binding to an external identity provider and RFC 9728 metadata. Programmatic access tokens expire (15 days by default, 365 at most), can be rotated and need a network policy by default. No dynamic client registration (28). Each tool needs its own grant, the SQL tool defaults to read-only, and the docs advise a separate least-privileged server for direct SQL. No confirmation step for writes is documented (15). The docs warn about tool poisoning, tool shadowing and recursive loops and cap recursion at 10. Nothing covers instructions arriving in query or search results (6). Account Usage has query, login and access history and a Cortex Agent usage view. No log of MCP tool calls was found (10). security.txt valid to 17 August 2027 with a HackerOne policy, SOC 2 Type II, ISO 27001, HITRUST and FedRAMP per the Security Addendum. The HackerOne page was not read (18). Per the 9 October check, not re-read on 4 November.\n\n## Score by category\n\n| Category | Weight | Neon MCP Server | Snowflake-managed MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 50 | Neon MCP Server +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 61 | Neon MCP Server +29 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 46 | Neon MCP Server +33 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 77 | Snowflake-managed MCP server +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | Neon MCP Server +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 35 | Neon MCP Server +45 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 84 | Snowflake-managed MCP server +9 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **72.5 · BB** | **52.7 · D** | |\n\n## Facts side by side\n\n| Fact | Neon MCP Server | Snowflake-managed MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Neon (Databricks) | Snowflake Inc. |\n| Hosted endpoint | `https://mcp.neon.tech/mcp` | no (local only) |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under Snowflake's terms of service |\n| Tools exposed | 138 | none |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | `com.neon/mcp` | not listed |\n| Last release | 2026-11-05 | 2026-08-20 |\n| Terms last updated | 2026-10-14 | 2026-04-16 |\n| Privacy policy last updated | 2026-01-09 | 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 | 663 stars | none |\n\n## How the scores have moved\n\n### Neon MCP Server\n\nNo score change since it was listed.\n\n### Snowflake-managed MCP server\n\n- -3.7 on 4 November 2026 (C to D): correction, time\n\n## Verdicts\n\n**Neon MCP Server.** OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.\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### Neon MCP Server\n\n1. Connect with ?category=querying\u0026category=schema\u0026projectId=... or untick Allow writes at consent to cut 138 tools to a handful\n2. Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing\n3. Pass branch IDs (br-...), not names; call list_branches to resolve a name\n4. On 429 back off exponentially, and on 423 Locked wait for the running operation to finish\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, Neon MCP Server or Snowflake-managed MCP server?\n\nNeon MCP Server scores 72.5 (BB) on agent readiness against Snowflake-managed MCP server's 52.7 (D), and leads in 5 of 7 scored categories. Snowflake-managed MCP server leads on security \u0026 auth and transparency \u0026 trust.\n\n### Do Neon MCP Server and Snowflake-managed MCP server need an API key?\n\nNeon MCP Server uses an OAuth sign-in. Snowflake-managed MCP server takes an API key or an OAuth sign-in.\n\n### Can an agent call Neon MCP Server and Snowflake-managed MCP server without installing anything?\n\nNeon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp. No hosted endpoint is listed for Snowflake-managed MCP server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.json, and with the fewest tokens: https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"neon-mcp\", \"b\": \"snowflake-managed\"}`. From a terminal: `anchor compare neon-mcp snowflake-managed`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/neon-mcp.json and https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n\n## Other comparisons with Neon MCP Server or Snowflake-managed MCP server\n\n- [ClickHouse MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.md)\n- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)\n- [DBHub vs Neon MCP Server](https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.md)\n- [DBHub vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/dbhub-vs-snowflake-managed.md)\n- [MCP Toolbox for Databases vs Neon MCP Server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.md)\n- [MCP Toolbox for Databases vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-snowflake-managed.md)\n- [Neon MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.md)\n- [Neon MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.md)\n- [Neon MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.md)\n- [Neon MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.md)\n- [Neon MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.md)\n- [ObsessionDB vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.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 Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.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 Neon MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp.md)\n- [MongoDB MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.md)\n- [Neon MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.md)\n- [Neon MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md)\n- [ReqRes MCP server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Neon MCP Server vs Snowflake-managed MCP server", "url": "" } ], "description": "Neon scores 72.5 (BB) to Snowflake-managed's 52.7 (D) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Neon MCP Server BB 72.5", "Snowflake-managed MCP server D 52.7", "scores" ], "h1": "Neon MCP Server vs Snowflake-managed MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/neon-mcp-vs-snowflake-managed", "published": "2026-10-01", "section": "tools", "title": "Neon vs Snowflake-managed for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed" }, "tokens": { "markdown": 5150, "slim": 3130 }, "version": 1 }