# DBHub vs ObsessionDB (slim)

> DBHub scores 70.4 (BB) to ObsessionDB's 41.1 (E) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dbhub-vs-obsessiondb.md (~4,550 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/dbhub-vs-obsessiondb.json · canonical https://www.anchorterminal.com/compare/dbhub-vs-obsessiondb
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

DBHub scores 70.4 (BB) on agent readiness against ObsessionDB's 41.1 (E), and leads in 6 of 7 scored categories. ObsessionDB leads on security & auth. Both do sql databases.

- DBHub: BB 70.4, rank #200 of 1486 · https://www.anchorterminal.com/tools/dbhub.min.md
- ObsessionDB: E 41.1, rank #1289 of 1486 · https://www.anchorterminal.com/tools/obsessiondb.min.md
- DBHub, good for Coding agents exploring and querying a local or staging database across several engines. postgres-mcp-pro, mongodb-mcp, clickhouse-mcp-server and supabase-mcp are the nearest listings; MCP Toolbox for Databases covers more sources with more tools. Ahead on Reliability, 80 against 20; Schema & documentation, 73 against 43; Agent ergonomics, 85 against 53; Payments & pricing, 60 against 40; Maintenance & community, 95 against 28. Also Agent-ready, a grade of BB or better; No key needed to call it; Runs on your own machine; Open source.
- ObsessionDB, good for An agent that needs SQL over large ClickHouse tables, and the database's own monitoring and alerts, through one hosted MCP connection. Ahead on Security & auth, 51 against 43. Also A hosted endpoint, with nothing to install.

| Category | DBHub | ObsessionDB |
| --- | --- | --- |
| Reliability (16%) | 80 | 20 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 73 | 43 |
| Agent ergonomics (13%) | 85 | 53 |
| Security & auth (14%) | 43 | 51 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 95 | 28 |
| Transparency & trust (7%) | 61 | 59 |

| Fact (where they differ) | DBHub | ObsessionDB |
| --- | --- | --- |
| Vendor | Bytebase | Kellerkind UG (haftungsbeschränkt) |
| Hosted endpoint | no (local only) | `https://console-api.obsessiondb.com/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Pay per use |
| Licence | MIT | Proprietary service under ObsessionDB's terms of service. The query engine is the open-source ClickHouse engine; the storage layer is proprietary |
| Tools exposed | 2 | 12 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.bytebase/dbhub` | not listed |
| Last release | 2026-11-03 | 2026-08-31 |
| Terms last updated | no document linked | 2026-06-10 |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 3.8k stars, 51k npm/wk | none |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Maintenance & community, DBHub +67: DBHub 95 (v1.5.1 on 3 November 2026, 3 days before this check (30). Eleven tags from v1.2.0 (1 August) to v1.5.1 in the 90 days (20). Issues and pull requests are closed quickly, most within days, and only 7 are open (22). Listed in the official MCP registry as io.github.bytebase/dbhub at the current version (15). CI on push and pull request, a Docker publish workflow and pinned pnpm (8). 30 + 20 + 22 + 15 + 8 = 95.); ObsessionDB 28 (Graded as a closed service. The last dated changelog entry is ClickHouse 26.8 LTS on 31 August 2026, 51 days before the check (20). Two dated entries in the 90 days to 21 October 2026, 21 and 31 August, short of three (0). A public changelog, in-console live chat since June 2026, a shared Slack channel for customers and email support. Replies were not sampled (8 of 15). Not in the official MCP registry and no SDKs of its own (0). Nothing to install for the service. chkit, its open-source CLI, had 93 commits in the 90 days and CI workflows on its default branch (0 of 10 for the service, as there's no package to check).)
- Reliability, DBHub +60: DBHub 80 (Scored as a local stdio and HTTP package. Official npm package @bytebase/dbhub with Node.js 22.5 or later stated (20). A run-tests workflow runs unit and container-based integration suites on push and pull request; the pass state wasn't read (15). Of the latest 25 issues, 22 are closed, most crash and regression reports fixed within days, such as the dropped-connection crash closed 21 October and duplicate column names closed 3 November (22). Semver tags for every release but no changelog file, and release notes weren't read (8). 1.0.0 since 28 July 2026 (15). 20 + 15 + 22 + 8 + 15 = 80.); ObsessionDB 20 (Graded as a hosted service. No status page was found. None is linked from the site, status.obsessiondb.com did not answer through our proxy, and the home page sets its contractual SLAs against 'a status page' (0). No readable incident history (5). No request rate limit found for the MCP server or the ClickHouse endpoints. The 1,000-row or 10 MiB `run_sql` cap and the one-insert-a-second guidance are result and usage guidance, read under ergonomics (0). No 429 or backoff guidance. Insert deduplication is handled by the coordination layer and Jobs runs large SQL as retryable tasks (5 of 15). The terms (10 June 2026) give no contractual uptime SLA on self-service plans and the enterprise SLAs are not published (0). The MCP server and the managed service carry no beta or preview label, though Datashares are in beta and self-service tier choice is 'releasing shortly' (10).)
- Agent ergonomics, DBHub +32: DBHub 85 (Two tools by default, about 1.4k tokens by the README's count, with opt-in extras (25). max_rows caps results and flags truncation, search_objects has names, summary and full detail levels and a limit (18). Errors return as tool errors with the database's message (12). readOnlyHint and destructiveHint follow the access policy, though idempotentHint is always false (18). Few required settings, one DSN, and no SDK is needed for a local server (12). 25 + 18 + 12 + 18 + 12 = 85.); ObsessionDB 53 (Twelve tools with short descriptions, all but `run_sql` read-only by name. Whether a person can approve fewer scopes at consent was not found (15). `run_sql` stops at 1,000 rows or 10 MiB and flags truncation, `monitoring_list_query_executions` filters to failed runs, and pattern tools take a time window. No paging was documented (12 of 20). Errors return in a field rather than failing the call, monitoring tools answer `available: false` where there is no archive, and a slug clash returns a rename request. ClickHouse error codes are documented upstream (12 of 20). No `readOnlyHint` or `destructiveHint` could be read from the docs, and no idempotency guidance for `run_sql` (4 of 20). Two required inputs for most calls. ObsessionDB ships no SDK of its own; ClickHouse's own drivers in Go, Python, JavaScript, Rust, .NET and Java are documented with per-driver setup pages (10 of 15).)
- Schema & documentation, DBHub +30: DBHub 73 (Both default tools take zod schemas, so inputs are typed JSON Schema (25). dbhub.ai serves llms.txt (10). Descriptions are short and generated per source ("Execute SQL queries on the postgres database [READ-ONLY MODE]"), with the row cap stated, and say little about when not to use a tool (10). search_objects has enums for object type and detail level and a result limit; SQL is free text by nature (12). Docs pages per tool with examples; error formats aren't documented (9). Semver tags without a changelog (7). 25 + 10 + 10 + 12 + 9 + 7 = 73.); ObsessionDB 43 (No public contract for the MCP tools. Their input schemas come back only from `tools/list` with a signed-in token, which we didn't obtain, and the ClickHouse HTTP interface has no OpenAPI file. The OAuth metadata documents are machine-readable but don't describe tools (0). llms.txt and a Markdown copy of each docs page (10). The docs give one line per tool, say to call `list_services` first, explain slug clashes and when to push work into SQL. ObsessionDB's post of 18 June 2026 quotes one tool calling itself 'the entry point for service-wide error investigation' (10 of 20). Inputs are a service slug and a free-text SQL string, with four documented scopes. No enums or constraints could be read (5 of 15). Setup examples for eleven clients, and documented `truncated: true` and `available: false` results. ClickHouse errors come back in a field per the 18 June post, with no error catalogue. The stdio bridge is called 'Anthropic's `mcp-remote` proxy', and npm names Glen Maddern as its author (8 of 15). A dated public changelog with 19 entries that tracks the ClickHouse release (26.8 LTS), with no version for the MCP server (10 of 15).)
- Payments & pricing, DBHub +20: DBHub 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).); ObsessionDB 40 (No x402, MPP or L402 (0). Compute at $20 per GB of memory per node per month and storage at $25 per TB per month are public on the pricing page without a login, which calls them indicative (20). A free developer tier of up to 4 vCPU and 8 GB with 'No credit card required' (20). A person signs up in a browser and approves OAuth consent before an agent can connect (0).)
- Security & auth, ObsessionDB +8: DBHub 43 (The server holds database credentials, and the MCP side has no credential over stdio. Over HTTP a bearer token is optional and off by default while the default bind is 0.0.0.0, so an exposed port answers anyone the host allow-list admits (12). Read-only mode classifies statements and adds engine-level read-only transactions on PostgreSQL, with row limits and timeouts; there is no confirmation step for writes when read-only is off (16). Rows reach the model unmarked, and no guidance on treating results as untrusted was found beyond a blog post on the lethal trifecta (4). The workbench shows request traces (8). No SECURITY.md, disclosure policy or security.txt found (3). 12 + 16 + 4 + 8 + 3 = 43.); ObsessionDB 51 (OAuth 2.1 with dynamic client registration, S256 PKCE, refresh tokens, header-only bearer tokens and four scopes, revocable from the console. The authorisation server metadata was read on 21 October 2026. Less 4 because `workbench:query` runs any SQL as the person's account across every organisation they belong to, with no per-service scope (26 of 30). The MCP docs describe no read-only mode or confirmation step for `run_sql`. ClickHouse roles down to table and column, a global read-only role since May 2026 and read-only Datashares give least-privilege options to an operator who sets them up (8 of 20). `run_sql` returns stored rows to the model as they are, and no prompt-injection guidance was found. The agent context button masks passwords and keys in captured SQL (2 of 15). ClickHouse's `system.query_log` records each query and the console keeps a one-week monitoring archive. Whether MCP calls are attributed to a client was not found (10 of 15). No SOC 2 or ISO 27001 (stated on the security page), no security.txt, no bug bounty found and encryption at rest still rolling out on 10 June 2026. The security page names an address for vulnerability reports (5 of 20).)