DBHub vs PostgreSQL (archived MCP reference server)

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.

PostgreSQL (archived MCP reference server) 0

Last release 0.6.2 on 4 December 2024 (0). No releases in the last 90 days (0). The repository was archived on 29 May 2025 and is read-only (0). Not in the official MCP registry (0). Pinned to MCP SDK 1.0.1 and deprecated on npm (0).

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.

PostgreSQL (archived MCP reference server) 13

Archived and superseded, so we scored what's left. Scored as a local stdio package. @modelcontextprotocol/server-postgres 0.6.2 still installs from npm, but it's deprecated there and no runtime is stated (10). No tests. package.json has no test script, and the archive has no CI for it (0). The repository is read-only, so nobody can file or fix a crash. The code releases the connection without waiting for its ROLLBACK (0). Versions 0.6.0 to 0.6.2 shipped in December 2024 with no changelog (3). Pre-1.0 and archived (0).

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.

PostgreSQL (archived MCP reference server) 38

One tool of about 180 characters (25). No row limit, no pagination and no output cap. Every row comes back as pretty-printed JSON (0). Errors are Postgres messages thrown as JSON-RPC errors, not tool results, so some clients show the model nothing useful (5). No annotations, so no readOnlyHint (0). One parameter, Node only (8). Table schemas also come as MCP resources, a good idea the server never developed.

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.

PostgreSQL (archived MCP reference server) 29

One tool, query, with an input schema typed as an object holding a string sql, but sql isn't marked required and has no description (15). The README is Markdown on GitHub. No llms.txt (5). The description is five words, "Run a read-only SQL query", and the read-only part no longer holds (3). No constraints, no length limit, no enum (3). The README has client configs only. Database errors are rethrown raw as protocol errors (3). No changelog or versioning beyond three 0.6.x releases (0).

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.

PostgreSQL (archived MCP reference server) 5

The connection string, password included, is a command-line argument and shows in process lists. Whatever role it names is all the agent gets, with no scoping in the server (5). Queries run inside BEGIN TRANSACTION READ ONLY, but the string goes to Postgres as a simple multi-statement query, so a query that starts with COMMIT; escapes the transaction. Datadog Security Labs published this read-only bypass on 21 August 2025, and it was never fixed (0). Table rows reach the model unmarked, with no injection guidance (0). No call log (0). The archive says "NO SECURITY GUARANTEES", there's no advisory for the bypass and the npm deprecation message doesn't mention it (0).

DBHub 61

MIT (30). A local server that sends data only to the configured database; no privacy statement, but nothing to state for hosted processing (15). Removed flags fail loudly with a message pointing at the TOML replacement (--readonly, READONLY, MAX_ROWS), but there is no written deprecation policy (10). No telemetry found in the source, though the README doesn't say so (12). 30 + 15 + 10 + 12 = 67.

PostgreSQL (archived MCP reference server) 77

MIT, an OSI licence (30). Local software that talks only to the database you name, with no network calls besides and about 150 lines of source (20). The GitHub banner dates the archive to 29 May 2025 and the archive README says no security updates will follow. Neither the archive, the main repository's README nor the npm deprecation message names a successor, and the main README still calls it "Read-only database access" (10). No telemetry (20).