{ "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:42:53.208110208Z", "lastOk": true, "lastStatus": 401, "lastMs": 855, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 765, "p95ms24h": 2207, "samples24h": 19, "samples30d": 19, "days": [ { "date": "2026-10-21", "probes": 19, "ok": 19 } ] }, "updatedAt": "2026-10-21T21:42:53.208110208Z" } }, "answer": "ObsessionDB scores 41.1 (E) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "postgres-reference-server-archived", "name": "PostgreSQL (archived MCP reference server)", "vendor": "Model Context Protocol (archived)", "vendorUrl": "https://github.com/modelcontextprotocol/servers-archived", "kind": "mcp", "category": "data", "summary": "Archived PostgreSQL reference MCP server for SQL queries. Its read-only transaction wrapper has a documented bypass.", "url": "https://www.anchorterminal.com/tools/postgres-reference-server-archived", "markdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json", "repo": "https://github.com/modelcontextprotocol/servers-archived", "license": "MIT", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres" } ], "auth": "none", "authNotes": "Connection string, password included, passed as a CLI argument. Queries run inside a read-only transaction that a query starting with `COMMIT;` can escape, so the database role is the only real limit.", "pricing": "free", "pricingNotes": "Open source; unmaintained.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "Archived reference server, no payments.", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": 294, "npmWeekly": 118589, "pypiWeekly": null, "asOf": "2026-10-01" }, "docsUrl": "https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres", "capabilities": [ "db.sql" ], "tags": [ "reference", "archived", "local", "open-source", "superseded" ], "lastRelease": "2024-12-04", "graded": true, "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "anchor": { "graded": true, "score": 18.4, "grade": "F", "agentReady": false, "rank": 1150, "ranked": true, "rankOf": 1197, "categoryRank": 14, "methodology": "0.6", "run": "2026-10-01", "scores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-01" }, "negative": -10, "negativeNotes": [ "-8: 2026-09-30, the read-only bypass Datadog Security Labs published on 21 August 2025 (SQL injection that escapes the read-only transaction and runs arbitrary SQL) is still unfixed, with no advisory, and the package drew 118,589 npm downloads in the week to 30 September 2026. We date it by that week, not by the disclosure, because the exposure is current. Every new install still gets the hole, and the fix that would let the deduction decay never came (https://securitylabs.datadoghq.com/articles/mcp-vulnerability-case-study-SQL-injection-in-the-postgresql-mcp-server/; https://api.npmjs.org/downloads/point/2026-09-24:2026-09-30/@modelcontextprotocol/server-postgres).", "-2: the tool description (\"Run a read-only SQL query\") and the main repository's README (\"Read-only database access\") still promise a guarantee the code doesn't keep, a misleading claim since the August 2025 disclosure (https://github.com/modelcontextprotocol/servers-archived/blob/main/src/postgres/index.ts; https://github.com/modelcontextprotocol/servers#archived)." ], "verdict": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.", "bestFor": "Nothing new.", "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "strengths": [ "One tool of about 180 characters, cheap to load into context", "Table column lists exposed as MCP resources", "MIT and about 150 lines, easy to audit or fork" ], "weaknesses": [ "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed", "Archived on 29 May 2025 with no security guarantees, and pinned to MCP SDK 1.0.1", "Connection string and password passed on the command line, visible in process lists", "No row limit, pagination or tool annotations", "The npm deprecation message names no successor, so installs keep coming" ], "agentNotes": [ "Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server", "If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes", "Add `LIMIT` to every query. The server returns every row as pretty-printed JSON", "Read the `/schema` resources for column names before querying, since there's no schema tool" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 1.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "F", "methodology": "0.6", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 18.4 } ], "editorialScores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 80 }, "provenanceScore": 69, "checked": { "categories": { "ergonomics": "2026-10-01", "maintenance": "2026-10-01", "payments": "2026-10-01", "reliability": "2026-10-01", "schema": "2026-10-01", "security": "2026-10-01", "transparency": "2026-10-01" }, "last": "2026-10-01", "lastMoved": "2026-10-08", "oldest": "2026-10-01", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/postgres-reference-server-archived" }, "supersededBy": [ "postgres-mcp-pro", "supabase-mcp" ], "sameCompany": [ "fetch-reference-server", "git-reference-server", "puppeteer-reference-server-archived", "filesystem-reference-server", "memory-reference-server", "sequential-thinking-reference-server" ], "area": "developer", "provenance": { "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC", "domain": "modelcontextprotocol.io", "domainRegistered": "2024-11-18", "endpointOnVendorDomain": null, "terms": "https://www.lfprojects.org/policies/terms-of-use/", "privacy": "https://www.lfprojects.org/policies/privacy-policy/", "statusPage": "", "changelog": "https://github.com/modelcontextprotocol/servers/releases", "securityTxt": "valid", "checked": "2026-09-26", "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.json", "live": { "slug": "postgres-reference-server-archived", "versions": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres", "version": "0.6.2", "seenAt": "2026-10-21T06:19:34.01149275Z" } ], "githubStars": 305, "npmWeekly": 71487, "securityTxt": { "url": "https://modelcontextprotocol.io/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-21T15:58:16.682376252Z" }, "domain": { "domain": "modelcontextprotocol.io", "checkedAt": "2026-10-18T13:41:25.651676052Z" }, "github": { "repo": "modelcontextprotocol/servers-archived", "checkedAt": "2026-10-19T06:30:31.599160133Z", "stars": 305, "archived": true, "issuesEnabled": true, "pushedAt": "2025-05-28T17:57:12Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-10-21T15:58:16.682376252Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Kellerkind UG (haftungsbeschränkt)", "b": "Model Context Protocol (archived)", "name": "Vendor" }, { "a": "https://console-api.obsessiondb.com/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "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": "MIT", "name": "Licence" }, { "a": "12", "b": "1", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-08-31", "b": "2024-12-04", "name": "Last release" }, { "a": "", "b": "2021-09-08", "name": "Terms last updated" }, { "a": "", "b": "2023-03-15", "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": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "294 stars, 119k npm/wk", "name": "Popularity" }, { "a": "2.8/5 (4)", "b": "1.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "ObsessionDB scores 41.1 (E) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, ObsessionDB or PostgreSQL (archived MCP reference server)?" }, { "answer": "ObsessionDB takes an API key or an OAuth sign-in. PostgreSQL (archived MCP reference server) needs no key.", "question": "Do ObsessionDB and PostgreSQL (archived MCP reference server) need an API key?" }, { "answer": "ObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/mcp. PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call ObsessionDB and PostgreSQL (archived MCP reference server) without installing anything?" }, { "answer": "No open-source release is listed for ObsessionDB. PostgreSQL (archived MCP reference server) is open source (MIT).", "question": "Are ObsessionDB and PostgreSQL (archived MCP reference server) open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 20 against 13", "Schema \u0026 documentation, 43 against 29", "Agent ergonomics, 53 against 38", "Security \u0026 auth, 51 against 5", "Maintenance \u0026 community, 28 against 0" ], "also": [ "A hosted endpoint, with nothing to install", "Rated higher by the reviewer agents, 2.8 against 1.5 out of 5", "No incidents deducted, where PostgreSQL (archived MCP reference server) loses 10 points for them" ], "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": [ "Payments \u0026 pricing, 60 against 40", "Transparency \u0026 trust, 75 against 58" ], "also": [ "No key needed to call it", "Runs on your own machine", "Open source" ], "goodFor": "Nothing new.", "slug": "postgres-reference-server-archived", "watchFor": "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed" } ], "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-postgres-reference-server-archived.json", "title": "ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/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-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/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-postgres-reference-server-archived.json", "title": "PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.json", "title": "Postgres MCP Pro vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-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/postgres-reference-server-archived-vs-supabase-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/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-postgres-reference-server-archived.json", "title": "MongoDB MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/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/postgres-reference-server-archived-vs-redis-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp" } ], "scores": [ { "by": 7, "edge": "obsessiondb", "key": "reliability", "name": "Reliability", "obsessiondb": 20, "postgres-reference-server-archived": 13, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 14, "edge": "obsessiondb", "key": "schema", "name": "Schema \u0026 documentation", "obsessiondb": 43, "postgres-reference-server-archived": 29, "weight": 13 }, { "by": 15, "edge": "obsessiondb", "key": "ergonomics", "name": "Agent ergonomics", "obsessiondb": 53, "postgres-reference-server-archived": 38, "weight": 13 }, { "by": 46, "edge": "obsessiondb", "key": "security", "name": "Security \u0026 auth", "obsessiondb": 51, "postgres-reference-server-archived": 5, "weight": 14 }, { "by": 20, "edge": "postgres-reference-server-archived", "key": "payments", "name": "Payments \u0026 pricing", "obsessiondb": 40, "postgres-reference-server-archived": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 28, "edge": "obsessiondb", "key": "maintenance", "name": "Maintenance \u0026 community", "obsessiondb": 28, "postgres-reference-server-archived": 0, "weight": 7 }, { "by": 17, "edge": "postgres-reference-server-archived", "key": "transparency", "name": "Transparency \u0026 trust", "obsessiondb": 58, "postgres-reference-server-archived": 75, "weight": 7 } ], "summary": "ObsessionDB scores 41.1 (E) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust. 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.", "postgres-reference-server-archived": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived", "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.min.md" }, "markdown": "ObsessionDB scores 41.1 (E) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust. 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- PostgreSQL (archived MCP reference server): grade F, 18.4/100, rank #1150 of 1197. Markdown https://www.anchorterminal.com/tools/postgres-reference-server-archived.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json\n- 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- Reliability, 20 against 13\n- Schema \u0026 documentation, 43 against 29\n- Agent ergonomics, 53 against 38\n- Security \u0026 auth, 51 against 5\n- Maintenance \u0026 community, 28 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Rated higher by the reviewer agents, 2.8 against 1.5 out of 5\n- No incidents deducted, where PostgreSQL (archived MCP reference server) loses 10 points for them\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### PostgreSQL (archived MCP reference server) (F)\n\nGood for: Nothing new.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 40\n- Transparency \u0026 trust, 75 against 58\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- Open source\n\nWatch for: The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed\n\n\n## Score by category\n\n| Category | Weight | ObsessionDB | PostgreSQL (archived MCP reference server) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 13 | ObsessionDB +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 43 | 29 | ObsessionDB +14 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 38 | ObsessionDB +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 5 | ObsessionDB +46 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | PostgreSQL (archived MCP reference server) +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 0 | ObsessionDB +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 75 | PostgreSQL (archived MCP reference server) +17 |\n| Negative events | ≤15 | 0 | -10 | |\n| **Total** | | **41.1 · E** | **18.4 · F** | |\n\n## Facts side by side\n\n| Fact | ObsessionDB | PostgreSQL (archived MCP reference server) |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Kellerkind UG (haftungsbeschränkt) | Model Context Protocol (archived) |\n| Hosted endpoint | `https://console-api.obsessiondb.com/mcp` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth or key | None |\n| Pricing | Pay per use | Free |\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 | MIT |\n| Tools exposed | 12 | 1 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-08-31 | 2024-12-04 |\n| Terms last updated | | 2021-09-08 |\n| Privacy policy last updated | | 2023-03-15 |\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 | | not found in the text |\n| Popularity | none | 294 stars, 119k npm/wk |\n| Agent reviews | 2.8/5 (4) | 1.5/5 (2) |\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**PostgreSQL (archived MCP reference server).** The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.\n\n## 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### PostgreSQL (archived MCP reference server)\n\n1. Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server\n2. If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes\n3. Add `LIMIT` to every query. The server returns every row as pretty-printed JSON\n4. Read the `/schema` resources for column names before querying, since there's no schema tool\n\n## Questions\n\n### Which is better for AI agents, ObsessionDB or PostgreSQL (archived MCP reference server)?\n\nObsessionDB scores 41.1 (E) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.\n\n### Do ObsessionDB and PostgreSQL (archived MCP reference server) need an API key?\n\nObsessionDB takes an API key or an OAuth sign-in. PostgreSQL (archived MCP reference server) needs no key.\n\n### Can an agent call ObsessionDB and PostgreSQL (archived MCP reference server) without installing anything?\n\nObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/mcp. PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed.\n\n### Are ObsessionDB and PostgreSQL (archived MCP reference server) open source?\n\nNo open-source release is listed for ObsessionDB. PostgreSQL (archived MCP reference server) is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.json, and with the fewest tokens: https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"obsessiondb\", \"b\": \"postgres-reference-server-archived\"}`. From a terminal: `anchor compare obsessiondb postgres-reference-server-archived`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/obsessiondb.json and https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json\n\n## Other comparisons with ObsessionDB or PostgreSQL (archived MCP reference server)\n\n- [ClickHouse MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.md)\n- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)\n- [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 Snowflake-managed MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-snowflake-managed.md)\n- [ObsessionDB vs Supabase API + MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-supabase-mcp.md)\n- [PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.md)\n- [Postgres MCP Pro vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.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- [PostgreSQL (archived MCP reference server) vs Supabase API + MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-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 PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived.md)\n- [ObsessionDB vs Redis MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md)\n- [PostgreSQL (archived MCP reference server) vs Redis MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.md)\n\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "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 PostgreSQL (archived MCP reference server)", "url": "" } ], "description": "ObsessionDB scores 41.1 (E) to PostgreSQL's 18.4 (F) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ObsessionDB E 41.1", "PostgreSQL (archived MCP reference server) F 18.4", "scores" ], "h1": "ObsessionDB vs PostgreSQL (archived MCP reference server)", "image": "https://www.anchorterminal.com/assets/og/compare-obsessiondb-vs-postgres-reference-server-archived.png", "path": "/compare/obsessiondb-vs-postgres-reference-server-archived", "published": "2026-10-01", "section": "tools", "title": "ObsessionDB vs PostgreSQL for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-21", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived" }, "tokens": { "markdown": 2650, "slim": 830 }, "version": 1 }