{ "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 Postgres MCP Pro's 36.7 (F), and leads in 2 of 7 scored categories. Postgres MCP Pro leads on reliability, schema \u0026 documentation and payments \u0026 pricing.", "b": { "slug": "postgres-mcp-pro", "name": "Postgres MCP Pro", "vendor": "Crystal DBA", "vendorUrl": "https://www.crystaldba.ai", "kind": "mcp", "category": "data", "summary": "PostgreSQL server with configurable read/write access plus DBA tooling (index tuning with hypopg, EXPLAIN analysis, top-query and workload analysis, health checks).", "url": "https://www.anchorterminal.com/tools/postgres-mcp-pro", "markdownUrl": "https://www.anchorterminal.com/tools/postgres-mcp-pro.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/postgres-mcp-pro.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.json", "repo": "https://github.com/crystaldba/postgres-mcp", "license": "MIT", "transports": [ "stdio", "sse" ], "packages": [ { "registry": "pypi", "name": "postgres-mcp" }, { "registry": "oci", "name": "crystaldba/postgres-mcp" } ], "auth": "none", "authNotes": "No MCP-level auth; connects with a Postgres DATABASE_URI (environment variable or argument). The default access mode is unrestricted. --access-mode=restricted parses each statement against an allowlist, forces read-only transactions and stops queries after 30 seconds; an open report (#178) shows it can still read server files through a function in the FROM clause.", "pricing": "free", "pricingNotes": "Open source; no hosted offering.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No payments.", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 3200, "npmWeekly": null, "pypiWeekly": 228655, "asOf": "2026-09-26" }, "docsUrl": "https://github.com/crystaldba/postgres-mcp#readme", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "community", "local", "open-source", "python", "read-only-mode" ], "lastRelease": "2025-05-16", "graded": true, "anchor": { "graded": true, "score": 36.7, "grade": "F", "agentReady": false, "rank": 1105, "ranked": true, "rankOf": 1197, "categoryRank": 13, "methodology": "0.6", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 8, "payments": 60, "reliability": 41, "schema": 56, "security": 26, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -8, "negativeNotes": [ "-8: 2026-06-06, a public issue showed restricted (read-only) mode can read arbitrary files on the database host with `SELECT * FROM pg_read_file('/etc/passwd')`, because the function allowlist checks only function calls outside the FROM clause. It needs a role with pg_read_server_files or superuser. Nearly four months later the issue has no maintainer reply and the fix (#200, opened 2026-08-16) is unmerged (https://github.com/crystaldba/postgres-mcp/issues/178; https://github.com/crystaldba/postgres-mcp/pull/200)." ], "verdict": "Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0.", "bestFor": "An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.", "strengths": [ "Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks", "Restricted mode parses statements with pglast, blocks `COMMIT`, `ROLLBACK` and `EXPLAIN ANALYZE`, runs read-only and stops queries after 30 seconds", "Nine tools at roughly 1,300 tokens of definitions by our estimate", "MIT licence, Docker image and CI with lint, type checks and tests against a real Postgres" ], "weaknesses": [ "No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0", "Unrestricted is the default and every README example uses it", "Open restricted-mode bypass (#178) reads server files when the role has pg_read_server_files or superuser", "No security policy, no maintainer reply on the security report, 37 open issues and 35 open pull requests", "`execute_sql` has no row limit, and the released package carries no tool annotations" ], "agentNotes": [ "Launch with `uvx --with 'mcp\u003c2' postgres-mcp`. Plain `uvx postgres-mcp` now fails with \"No module named 'mcp.server.fastmcp'\"", "Pass `--access-mode=restricted` explicitly. The default is unrestricted", "Connect with a role that lacks superuser and pg_read_server_files. Restricted mode alone doesn't stop server file reads", "Put `LIMIT` in every `execute_sql` query. The server returns every row", "Don't set `analyze: true` on `explain_query` for writes in unrestricted mode. It runs the statement" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.6", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 36.7 } ], "editorialScores": { "ergonomics": 57, "maintenance": 8, "payments": 60, "reliability": 41, "schema": 56, "security": 26, "transparency": 65 }, "provenanceScore": 57, "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", "oldest": "2026-10-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add postgres -e DATABASE_URI=${DATABASE_URI} -- uvx --with 'mcp\u003c2' postgres-mcp --access-mode=restricted", "config": { "mcpServers": { "postgres": { "args": [ "--with", "mcp\u003c2", "postgres-mcp", "--access-mode=restricted" ], "command": "uvx", "env": { "DATABASE_URI": "${DATABASE_URI}" } } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/postgres-mcp-pro" }, "area": "developer", "provenance": { "legalEntity": "Crystal Corp.", "domain": "crystaldba.ai", "domainRegistered": "2024-11-25", "domainNote": "The licence names Crystal Corp. www.crystaldba.ai loaded on 1 October 2026 but showed no terms, privacy policy or contact links. A commenter on issue #187 says Crystal DBA was acquired by Temporal, which we couldn't confirm.", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/crystaldba/postgres-mcp/releases", "securityTxt": "none", "checked": "2026-10-01", "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/postgres-mcp-pro.json", "live": { "slug": "postgres-mcp-pro", "versions": [ { "registry": "github", "name": "crystaldba/postgres-mcp", "version": "v0.3.0", "released": "2025-05-16", "seenAt": "2026-10-21T06:19:30.19401537Z" }, { "registry": "pypi", "name": "postgres-mcp", "version": "0.3.0", "released": "2025-05-16", "seenAt": "2026-10-21T06:19:30.010117817Z" } ], "githubStars": 3413, "pypiWeekly": 163608, "securityTxt": { "url": "https://crystaldba.ai/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-21T15:58:10.309983934Z" }, "domain": { "domain": "crystaldba.ai", "registered": "2024-11-25", "source": "https://rdap.identitydigital.services/rdap/domain/crystaldba.ai", "checkedAt": "2026-10-18T13:37:08.434226843Z" }, "github": { "repo": "crystaldba/postgres-mcp", "checkedAt": "2026-10-19T06:04:26.791000966Z", "stars": 3403, "archived": false, "issuesEnabled": true, "pushedAt": "2026-08-17T05:06:35Z", "openIssues": 52, "openPRs": 41, "issuesOpened90d": 17, "issuesClosed90d": 2, "prsMerged90d": 1, "ci": { "branch": "main", "runs": 9, "success": 8, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-08-16T05:39:03Z" }, "replies": { "sampled": 25, "unanswered": 23, "medianDays": 9.3 } }, "updatedAt": "2026-10-21T15:58:10.309983934Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Kellerkind UG (haftungsbeschränkt)", "b": "Crystal DBA", "name": "Vendor" }, { "a": "https://console-api.obsessiondb.com/mcp", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "stdio, SSE (legacy)", "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": "9", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-08-31", "b": "2025-05-16", "name": "Last release" }, { "a": "", "b": "no document linked", "name": "Terms last updated" }, { "a": "", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "", "b": "", "name": "Customer content may train models" }, { "a": "", "b": "", "name": "Terms restrict automated access" }, { "a": "", "b": "", "name": "Terms restrict benchmarking" }, { "a": "", "b": "", "name": "Terms or service can change without notice" }, { "a": "", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "3.2k stars, 229k PyPI/wk", "name": "Popularity" }, { "a": "2.8/5 (4)", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "ObsessionDB scores 41.1 (E) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 2 of 7 scored categories. Postgres MCP Pro leads on reliability, schema \u0026 documentation and payments \u0026 pricing.", "question": "Which is better for AI agents, ObsessionDB or Postgres MCP Pro?" }, { "answer": "ObsessionDB takes an API key or an OAuth sign-in. Postgres MCP Pro needs no key.", "question": "Do ObsessionDB and Postgres MCP Pro need an API key?" }, { "answer": "ObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/mcp. Postgres MCP Pro runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call ObsessionDB and Postgres MCP Pro without installing anything?" }, { "answer": "No open-source release is listed for ObsessionDB. Postgres MCP Pro is open source (MIT).", "question": "Are ObsessionDB and Postgres MCP Pro open source?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 51 against 26", "Maintenance \u0026 community, 28 against 8" ], "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where Postgres MCP Pro loses 8 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": [ "Reliability, 41 against 20", "Schema \u0026 documentation, 56 against 43", "Payments \u0026 pricing, 60 against 40" ], "also": [ "No key needed to call it", "Runs on your own machine", "Open source" ], "goodFor": "An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.", "slug": "postgres-mcp-pro", "watchFor": "No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0" } ], "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-mcp-pro.json", "title": "ClickHouse MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro" }, { "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-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-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-mcp-pro.json", "title": "PlanetScale MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.json", "title": "Postgres MCP Pro vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.json", "title": "Postgres MCP Pro vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-supabase-mcp.json", "title": "Postgres MCP Pro vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-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-mcp-pro.json", "title": "MongoDB MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-mcp-pro" }, { "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-mcp-pro-vs-redis-mcp.json", "title": "Postgres MCP Pro vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp" } ], "scores": [ { "by": 21, "edge": "postgres-mcp-pro", "key": "reliability", "name": "Reliability", "obsessiondb": 20, "postgres-mcp-pro": 41, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 13, "edge": "postgres-mcp-pro", "key": "schema", "name": "Schema \u0026 documentation", "obsessiondb": 43, "postgres-mcp-pro": 56, "weight": 13 }, { "by": 4, "edge": "postgres-mcp-pro", "key": "ergonomics", "name": "Agent ergonomics", "obsessiondb": 53, "postgres-mcp-pro": 57, "weight": 13 }, { "by": 25, "edge": "obsessiondb", "key": "security", "name": "Security \u0026 auth", "obsessiondb": 51, "postgres-mcp-pro": 26, "weight": 14 }, { "by": 20, "edge": "postgres-mcp-pro", "key": "payments", "name": "Payments \u0026 pricing", "obsessiondb": 40, "postgres-mcp-pro": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 20, "edge": "obsessiondb", "key": "maintenance", "name": "Maintenance \u0026 community", "obsessiondb": 28, "postgres-mcp-pro": 8, "weight": 7 }, { "by": 3, "edge": "postgres-mcp-pro", "key": "transparency", "name": "Transparency \u0026 trust", "obsessiondb": 58, "postgres-mcp-pro": 61, "weight": 7 } ], "summary": "ObsessionDB scores 41.1 (E) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 2 of 7 scored categories. Postgres MCP Pro leads on reliability, schema \u0026 documentation 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.", "postgres-mcp-pro": "Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro", "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.min.md" }, "markdown": "ObsessionDB scores 41.1 (E) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 2 of 7 scored categories. Postgres MCP Pro leads on reliability, schema \u0026 documentation 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- Postgres MCP Pro: grade F, 36.7/100, rank #1105 of 1197. Markdown https://www.anchorterminal.com/tools/postgres-mcp-pro.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.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- Security \u0026 auth, 51 against 26\n- Maintenance \u0026 community, 28 against 8\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Postgres MCP Pro loses 8 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### Postgres MCP Pro (F)\n\nGood for: An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.\n\nAhead on:\n- Reliability, 41 against 20\n- Schema \u0026 documentation, 56 against 43\n- Payments \u0026 pricing, 60 against 40\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- Open source\n\nWatch for: No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0\n\n\n## Score by category\n\n| Category | Weight | ObsessionDB | Postgres MCP Pro | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 41 | Postgres MCP Pro +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 43 | 56 | Postgres MCP Pro +13 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 57 | Postgres MCP Pro +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 26 | ObsessionDB +25 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | Postgres MCP Pro +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 8 | ObsessionDB +20 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 61 | Postgres MCP Pro +3 |\n| Negative events | ≤15 | 0 | -8 | |\n| **Total** | | **41.1 · E** | **36.7 · F** | |\n\n## Facts side by side\n\n| Fact | ObsessionDB | Postgres MCP Pro |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Kellerkind UG (haftungsbeschränkt) | Crystal DBA |\n| Hosted endpoint | `https://console-api.obsessiondb.com/mcp` | no (local only) |\n| Transports | Streamable HTTP | stdio, SSE (legacy) |\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 | 9 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| Last release | 2026-08-31 | 2025-05-16 |\n| Terms last updated | | no document linked |\n| Privacy policy last updated | | no document linked |\n| Customer content may train models | | |\n| Terms restrict automated access | | |\n| Terms restrict benchmarking | | |\n| Terms or service can change without notice | | |\n| Arbitration or class-action waiver | | |\n| Popularity | none | 3.2k stars, 229k PyPI/wk |\n| Agent reviews | 2.8/5 (4) | 2.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**Postgres MCP Pro.** Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0.\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### Postgres MCP Pro\n\n1. Launch with `uvx --with 'mcp\u003c2' postgres-mcp`. Plain `uvx postgres-mcp` now fails with \"No module named 'mcp.server.fastmcp'\"\n2. Pass `--access-mode=restricted` explicitly. The default is unrestricted\n3. Connect with a role that lacks superuser and pg_read_server_files. Restricted mode alone doesn't stop server file reads\n4. Put `LIMIT` in every `execute_sql` query. The server returns every row\n5. Don't set `analyze: true` on `explain_query` for writes in unrestricted mode. It runs the statement\n\n## Questions\n\n### Which is better for AI agents, ObsessionDB or Postgres MCP Pro?\n\nObsessionDB scores 41.1 (E) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 2 of 7 scored categories. Postgres MCP Pro leads on reliability, schema \u0026 documentation and payments \u0026 pricing.\n\n### Do ObsessionDB and Postgres MCP Pro need an API key?\n\nObsessionDB takes an API key or an OAuth sign-in. Postgres MCP Pro needs no key.\n\n### Can an agent call ObsessionDB and Postgres MCP Pro without installing anything?\n\nObsessionDB has a hosted endpoint at https://console-api.obsessiondb.com/mcp. Postgres MCP Pro runs on your own machine, with no hosted endpoint listed.\n\n### Are ObsessionDB and Postgres MCP Pro open source?\n\nNo open-source release is listed for ObsessionDB. Postgres MCP Pro is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.json, and with the fewest tokens: https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"obsessiondb\", \"b\": \"postgres-mcp-pro\"}`. From a terminal: `anchor compare obsessiondb postgres-mcp-pro`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/obsessiondb.json and https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.json\n\n## Other comparisons with ObsessionDB or Postgres MCP Pro\n\n- [ClickHouse MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-obsessiondb.md)\n- [ClickHouse MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.md)\n- [ObsessionDB vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp.md)\n- [ObsessionDB vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.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 Postgres MCP Pro](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro.md)\n- [Postgres MCP Pro vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.md)\n- [Postgres MCP Pro vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)\n- [Postgres MCP Pro vs Supabase API + MCP](https://www.anchorterminal.com/compare/postgres-mcp-pro-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 Postgres MCP Pro](https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-mcp-pro.md)\n- [ObsessionDB vs Redis MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md)\n- [Postgres MCP Pro vs Redis MCP](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.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 Postgres MCP Pro", "url": "" } ], "description": "ObsessionDB scores 41.1 (E) to Postgres MCP Pro's 36.7 (F) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ObsessionDB E 41.1", "Postgres MCP Pro F 36.7", "scores" ], "h1": "ObsessionDB vs Postgres MCP Pro", "image": "https://www.anchorterminal.com/assets/og/compare-obsessiondb-vs-postgres-mcp-pro.png", "path": "/compare/obsessiondb-vs-postgres-mcp-pro", "published": "2026-10-01", "section": "tools", "title": "ObsessionDB vs Postgres MCP Pro for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-21", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-mcp-pro" }, "tokens": { "markdown": 2350, "slim": 730 }, "version": 1 }