{ "data": { "a": { "slug": "obsessiondb", "name": "ObsessionDB", "vendor": "Kellerkind UG (haftungsbeschränkt)", "vendorUrl": "https://obsessiondb.com", "kind": "mcp", "category": "data", "summary": "ObsessionDB is a managed ClickHouse service that runs the ClickHouse engine on object storage with stateless compute. Agents reach it through a hosted MCP server with OAuth, or through any ClickHouse client over the native or HTTP protocol.", "url": "https://www.anchorterminal.com/tools/obsessiondb", "markdownUrl": "https://www.anchorterminal.com/tools/obsessiondb.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/obsessiondb.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/obsessiondb.json", "license": "Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary", "transports": [ "streamable-http" ], "remoteUrl": "https://console-api.obsessiondb.com/mcp", "packages": [], "auth": "mixed", "authNotes": "The hosted MCP server uses OAuth 2.1 with dynamic client registration and PKCE (S256), and the person signs in at console.obsessiondb.com and approves the connection in a browser. Scopes are `services:read`, `workbench:query`, `monitoring:read` and `alerts:read`, and a token works as the person's account across every organisation they belong to. Connections can be revoked under connected apps in the console. Direct ClickHouse connections use the host, port, user and password shown in the dashboard. No API key route was found for the MCP server.", "pricing": "usage", "pricingNotes": "Compute at $20 per GB of memory per node per month ($160 per 2 vCPU and 8 GB compute unit) and storage at $25 per TB per month after compression, per the pricing page's sizing prompt and calculator, which calls prices indicative and says they vary by cloud and region. Ingress and egress free, no per-query charge, no minimum commitment. A free developer tier (up to 4 vCPU and 8 GB) needs no card (checked 2026-10-21).", "priceSummary": "$160 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page, the pricing and billing docs page or the terms (checked 2026-10-21).", "endpoints": [] }, "toolCount": 12, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-21" }, "docsUrl": "https://obsessiondb.com/docs", "llmsTxt": "https://obsessiondb.com/llms.txt", "capabilities": [ "db.sql", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "database", "llms-txt", "usage-priced", "free-tier" ], "lastRelease": "2026-08-31", "graded": true, "anchor": { "graded": true, "score": 41.1, "grade": "E", "agentReady": false, "rank": 1068, "ranked": true, "rankOf": 1197, "categoryRank": 12, "methodology": "0.6", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 28, "payments": 40, "reliability": 20, "schema": 43, "security": 51, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-21" }, "negative": 0, "verdict": "The hosted MCP server uses OAuth 2.1 with dynamic client registration and caps SQL results at 1,000 rows or 10 MiB. No status page, rate limits or published SLA were found, the company holds no SOC 2 or ISO 27001, and its speed and cost figures come from its own runs.", "bestFor": "An agent that needs SQL over large ClickHouse tables, and the database's own monitoring and alerts, through one hosted MCP connection.", "strengths": [ "OAuth 2.1 with dynamic client registration, PKCE and four scopes, so no database password goes into the client config", "Twelve MCP tools, one SQL tool and eleven read tools for services, monitoring and alerts", "`run_sql` caps results at 1,000 rows or 10 MiB and flags truncation", "Standard ClickHouse wire and HTTP protocols, so existing ClickHouse drivers and BI tools connect unchanged", "Per-GB compute and per-TB storage prices are public, with a free developer tier that needs no card" ], "weaknesses": [ "No public status page or incident history was found, and the terms give no uptime SLA on self-service plans", "No SOC 2 or ISO 27001, no security.txt, and encryption at rest was still rolling out per the security page of 10 June 2026", "The `workbench:query` scope runs any SQL as the person's account, with no read-only MCP mode documented", "Only two dated changelog entries in the 90 days to 21 October 2026, the last on 31 August", "Speed and cost claims come from ObsessionDB's own runs. It has no entry in ClickBench's results repository" ], "agentNotes": [ "Call `list_services` first and pass `serviceSlug` unchanged from it to `run_sql` and the monitoring tools", "Push aggregation into SQL with `GROUP BY` or `ORDER BY ... LIMIT`. Results stop at 1,000 rows or 10 MiB and set `truncated: true`", "Treat `available: false` from a monitoring tool as no monitoring archive for that service, not as an error", "Batch inserts to about one `INSERT` a second per table, because every insert writes durably to object storage", "Expect a browser sign-in on first connect. A person must approve the OAuth consent at console.obsessiondb.com" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.6", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.1 } ], "editorialScores": { "ergonomics": 53, "maintenance": 28, "payments": 40, "reliability": 20, "schema": 43, "security": 51, "transparency": 50 }, "provenanceScore": 65, "checked": { "categories": { "ergonomics": "2026-10-21", "maintenance": "2026-10-21", "payments": "2026-10-21", "reliability": "2026-10-21", "schema": "2026-10-21", "security": "2026-10-21", "transparency": "2026-10-21" }, "last": "2026-10-21", "oldest": "2026-10-21", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http obsessiondb https://console-api.obsessiondb.com/mcp", "config": { "mcpServers": { "obsessiondb": { "args": [ "-y", "mcp-remote", "https://console-api.obsessiondb.com/mcp" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/obsessiondb" }, "area": "developer", "unitPrices": [ { "item": "Compute, per compute unit (2 vCPU, 8 GB) per node", "unit": "month", "usd": 160, "note": "$20 per GB of memory per node per month. Node sizes of 8 to 256 GB. Indicative; varies by cloud and region" }, { "item": "Storage, per TB after compression", "unit": "month", "usd": 25, "note": "Ingress and egress free. Indicative; varies by cloud and region" } ], "provenance": { "legalEntity": "Kellerkind UG (haftungsbeschränkt)", "domain": "obsessiondb.com", "domainRegistered": "2026-01-03", "endpointOnVendorDomain": true, "terms": "https://obsessiondb.com/terms", "privacy": "https://obsessiondb.com/privacy", "statusPage": "", "changelog": "https://obsessiondb.com/changelog", "securityTxt": "none", "checked": "2026-10-21", "notes": [ "The terms (updated 10 June 2026) and the imprint name Kellerkind UG (haftungsbeschränkt), Traunsteiner Str. 10, 10781 Berlin, HRB 267091 B at Amtsgericht Berlin (Charlottenburg), under German law with Berlin courts.", "The home page says the company is backed by Y Combinator. No parent company is named on a first-hand page.", "/.well-known/security.txt returns the site's HTML page, not a security.txt file. The security page gives an address for vulnerability reports.", "No status page was found. None is linked from the site, and status.obsessiondb.com did not answer through our proxy.", "RDAP for obsessiondb.com gives a registration date of 2026-01-03." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/obsessiondb.json", "live": { "slug": "obsessiondb", "probe": { "target": "https://console-api.obsessiondb.com/mcp", "method": "mcp-initialize", "lastAt": "2026-10-21T21:54:31.461163582Z", "lastOk": true, "lastStatus": 401, "lastMs": 588, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 765, "p95ms24h": 1639, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-21", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-21T21:54:31.461163582Z" } }, "answer": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 5 of 7 scored categories. ObsessionDB leads on agent ergonomics and 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": 722, "ranked": true, "rankOf": 1197, "categoryRank": 9, "methodology": "0.6", "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.6", "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, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "oldest": "2026-10-09", "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": "major", "summary": "Partial System Outage", "checkedAt": "2026-10-21T21:49:43.390882813Z" }, "securityTxt": { "url": "https://snowflake.com/.well-known/security.txt", "state": "valid", "expires": "2027-08-17T19:00:00.000Z", "checkedAt": "2026-10-21T15:58:28.398301999Z" }, "llmsTxt": { "url": "https://docs.snowflake.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-21T14:35:05.442112317Z" }, "domain": { "domain": "snowflake.com", "registered": "1995-07-08", "source": "https://rdap.verisign.com/com/v1/domain/snowflake.com", "checkedAt": "2026-10-18T13:35:55.723153845Z" }, "pages": [ { "url": "https://docs.snowflake.com/en/release-notes/new-features", "kind": "changelog", "status": 200, "checkedAt": "2026-10-21T00:47:42.63327978Z", "changedAt": "2026-10-21T00:25:59.980764816Z", "fingerprint": "4a533ec16489" }, { "url": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-21T01:07:06.355316968Z", "changedAt": "2026-10-21T01:07:06.355316968Z", "fingerprint": "4450aa84b20b" }, { "url": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-21T01:07:08.613891749Z", "changedAt": "2026-10-21T01:07:08.613891749Z", "fingerprint": "c915c9ea2e0c" } ], "updatedAt": "2026-10-21T21:49:43.390882813Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Kellerkind UG (haftungsbeschränkt)", "b": "Snowflake Inc.", "name": "Vendor" }, { "a": "https://console-api.obsessiondb.com/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary", "b": "Proprietary service under Snowflake's terms of service", "name": "Licence" }, { "a": "12", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-08-31", "b": "2026-08-20", "name": "Last release" }, { "a": "", "b": "2026-04-16", "name": "Terms last updated" }, { "a": "", "b": "2026-07-01", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "2.8/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 5 of 7 scored categories. ObsessionDB leads on agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, ObsessionDB or Snowflake-managed MCP server?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do ObsessionDB and Snowflake-managed MCP server need an API key?" }, { "answer": "ObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/mcp. No hosted endpoint is listed for Snowflake-managed MCP server.", "question": "Can an agent call ObsessionDB and Snowflake-managed MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 53 against 46", "Payments \u0026 pricing, 40 against 35" ], "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "An agent that needs SQL over large ClickHouse tables, and the database's own monitoring and alerts, through one hosted MCP connection.", "slug": "obsessiondb", "watchFor": "No public status page or incident history was found, and the terms give no uptime SLA on self-service plans" }, { "aheadOn": [ "Reliability, 55 against 20", "Schema \u0026 documentation, 61 against 43", "Security \u0026 auth, 77 against 51", "Maintenance \u0026 community, 55 against 28", "Transparency \u0026 trust, 84 against 58" ], "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-obsessiondb.json", "title": "ClickHouse MCP Server vs ObsessionDB", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb" }, { "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/obsessiondb-vs-planetscale-mcp.json", "title": "ObsessionDB vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.json", "title": "ObsessionDB vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.json", "title": "ObsessionDB vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-supabase-mcp.json", "title": "ObsessionDB vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-supabase-mcp" }, { "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-obsessiondb.json", "title": "MongoDB MCP Server vs ObsessionDB", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-obsessiondb" }, { "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/obsessiondb-vs-redis-mcp.json", "title": "ObsessionDB vs Redis MCP", "url": "https://www.anchorterminal.com/compare/obsessiondb-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": 35, "edge": "snowflake-managed", "key": "reliability", "name": "Reliability", "obsessiondb": 20, "snowflake-managed": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "edge": "snowflake-managed", "key": "schema", "name": "Schema \u0026 documentation", "obsessiondb": 43, "snowflake-managed": 61, "weight": 13 }, { "by": 7, "edge": "obsessiondb", "key": "ergonomics", "name": "Agent ergonomics", "obsessiondb": 53, "snowflake-managed": 46, "weight": 13 }, { "by": 26, "edge": "snowflake-managed", "key": "security", "name": "Security \u0026 auth", "obsessiondb": 51, "snowflake-managed": 77, "weight": 14 }, { "by": 5, "edge": "obsessiondb", "key": "payments", "name": "Payments \u0026 pricing", "obsessiondb": 40, "snowflake-managed": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 27, "edge": "snowflake-managed", "key": "maintenance", "name": "Maintenance \u0026 community", "obsessiondb": 28, "snowflake-managed": 55, "weight": 7 }, { "by": 26, "edge": "snowflake-managed", "key": "transparency", "name": "Transparency \u0026 trust", "obsessiondb": 58, "snowflake-managed": 84, "weight": 7 } ], "summary": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 5 of 7 scored categories. ObsessionDB leads on agent ergonomics and payments \u0026 pricing. Both do sql databases.", "tutorials": [], "verdicts": { "obsessiondb": "The hosted MCP server uses OAuth 2.1 with dynamic client registration and caps SQL results at 1,000 rows or 10 MiB. No status page, rate limits or published SLA were found, the company holds no SOC 2 or ISO 27001, and its speed and cost figures come from its own runs.", "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/obsessiondb-vs-snowflake-managed", "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.min.md" }, "markdown": "Snowflake-managed MCP server scores 56.4 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 5 of 7 scored categories. ObsessionDB leads on agent ergonomics and payments \u0026 pricing. Both do sql databases.\n\n- ObsessionDB: grade E, 41.1/100, rank #1068 of 1197. Markdown https://www.anchorterminal.com/tools/obsessiondb.md · JSON https://www.anchorterminal.com/api/v1/tools/obsessiondb.json\n- Snowflake-managed MCP server: grade C, 56.4/100, rank #722 of 1197. 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 55 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### ObsessionDB (E)\n\nGood for: An agent that needs SQL over large ClickHouse tables, and the database's own monitoring and alerts, through one hosted MCP connection.\n\nAhead on:\n- Agent ergonomics, 53 against 46\n- Payments \u0026 pricing, 40 against 35\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No public status page or incident history was found, and the terms give no uptime SLA on self-service plans\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 20\n- Schema \u0026 documentation, 61 against 43\n- Security \u0026 auth, 77 against 51\n- Maintenance \u0026 community, 55 against 28\n- Transparency \u0026 trust, 84 against 58\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 | ObsessionDB | Snowflake-managed MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 55 | Snowflake-managed MCP server +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 43 | 61 | Snowflake-managed MCP server +18 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 46 | ObsessionDB +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 77 | Snowflake-managed MCP server +26 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 35 | ObsessionDB +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 55 | Snowflake-managed MCP server +27 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 84 | Snowflake-managed MCP server +26 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **41.1 · E** | **56.4 · C** | |\n\n## Facts side by side\n\n| Fact | ObsessionDB | Snowflake-managed MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Kellerkind UG (haftungsbeschränkt) | Snowflake Inc. |\n| Hosted endpoint | `https://console-api.obsessiondb.com/mcp` | no (local only) |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary | Proprietary service under Snowflake's terms of service |\n| Tools exposed | 12 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| Last release | 2026-08-31 | 2026-08-20 |\n| Terms last updated | | 2026-04-16 |\n| Privacy policy last updated | | 2026-07-01 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | yes |\n| Agent reviews | 2.8/5 (4) | none |\n\n## Verdicts\n\n**ObsessionDB.** The hosted MCP server uses OAuth 2.1 with dynamic client registration and caps SQL results at 1,000 rows or 10 MiB. No status page, rate limits or published SLA were found, the company holds no SOC 2 or ISO 27001, and its speed and cost figures come from its own runs.\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### ObsessionDB\n\n1. Call `list_services` first and pass `serviceSlug` unchanged from it to `run_sql` and the monitoring tools\n2. Push aggregation into SQL with `GROUP BY` or `ORDER BY ... LIMIT`. Results stop at 1,000 rows or 10 MiB and set `truncated: true`\n3. Treat `available: false` from a monitoring tool as no monitoring archive for that service, not as an error\n4. Batch inserts to about one `INSERT` a second per table, because every insert writes durably to object storage\n5. Expect a browser sign-in on first connect. A person must approve the OAuth consent at console.obsessiondb.com\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, ObsessionDB or Snowflake-managed MCP server?\n\nSnowflake-managed MCP server scores 56.4 (C) on agent readiness against ObsessionDB's 41.1 (E), and leads in 5 of 7 scored categories. ObsessionDB leads on agent ergonomics and payments \u0026 pricing.\n\n### Do ObsessionDB and Snowflake-managed MCP server need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call ObsessionDB and Snowflake-managed MCP server without installing anything?\n\nObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/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/obsessiondb-vs-snowflake-managed.json, and with the fewest tokens: https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"obsessiondb\", \"b\": \"snowflake-managed\"}`. From a terminal: `anchor compare obsessiondb snowflake-managed`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/obsessiondb.json and https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n\n## Other comparisons with ObsessionDB or Snowflake-managed MCP server\n\n- [ClickHouse MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.md)\n- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)\n- [ObsessionDB vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp.md)\n- [ObsessionDB vs Postgres MCP Pro](https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.md)\n- [ObsessionDB vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.md)\n- [ObsessionDB vs Supabase API + MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-supabase-mcp.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 ObsessionDB](https://www.anchorterminal.com/compare/mongodb-mcp-vs-obsessiondb.md)\n- [MongoDB MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.md)\n- [ObsessionDB vs Redis MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-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-10-21", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.6", "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": "ObsessionDB vs Snowflake-managed MCP server", "url": "" } ], "description": "Snowflake-managed scores 56.4 (C) to ObsessionDB's 41.1 (E) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ObsessionDB E 41.1", "Snowflake-managed MCP server C 56.4", "scores" ], "h1": "ObsessionDB vs Snowflake-managed MCP server", "image": "https://www.anchorterminal.com/assets/og/compare-obsessiondb-vs-snowflake-managed.png", "path": "/compare/obsessiondb-vs-snowflake-managed", "published": "2026-10-01", "section": "tools", "title": "ObsessionDB vs Snowflake-managed for AI agents (2026)", "toc": null, "updated": "2026-10-21", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed" }, "tokens": { "markdown": 2450, "slim": 730 }, "version": 1 }