DBHub vs Redis MCP

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.

Redis MCP 47

0.5.1 was tagged on 4 August 2026 and published on GitHub and PyPI on 5 August, 91 days before this check, and no release has followed (10). No release in the 90 days from 6 August. The 32 commits since 0.5.1, up to 3 November, are dependency updates and the removal of an unused dev dependency, with the version still 0.5.1 (0). 19 open items per the 9 October check, when Redis staff had answered #156, #163 and #169 within weeks and merged the mcp pin the day it was reported, while #174, #137 and #31 had no reply and #45 on streamable HTTP had been open since August 2025 (14 of 25). Listed in the official MCP registry as io.github.redis/mcp-redis, a GitHub-verified namespace, with 0.5.1 marked latest per the 9 October check, and the repository's server.json still names it (15). Dependabot updates merged up to 3 November 2026, a lock file and the mcp dependency pinned below 2 (8 of 10).

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.

Redis MCP 39

53 tools load at once, about 15,700 characters of descriptions, with no toolsets, dynamic loading or read-only subset. Pull request #161 for an allowlist has been open since 28 July 2026 (5 of 25). scan_keys pages with a cursor, lrange and zrange take ranges, xrange and xreadgroup take a count, read_messages caps at 100 and the vector tools take k. scan_all_keys, hgetall, smembers and json_get return everything with no limit (12 of 20). Failures come back as ordinary results, a string starting Error or a dictionary with an error key, carrying the Redis error text. Input checks return clear messages, such as the refusal of block_ms=0. Nothing marks a result as an MCP error and no error list is documented (9 of 20). No tool declares readOnlyHint, destructiveHint or idempotentHint, and pull request #181 adding them was opened on 8 October 2026. No retry guidance was found, and lpush, xadd and publish are not safe to repeat (3 of 20). Most tools need one or two arguments and defaults are stated in the descriptions. The server is a Python package only (10 of 15).

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.

Redis MCP 52

Scored as local software, since the owner runs it over stdio. Official PyPI package redis-mcp-server with Python 3.10 to 3.14 stated in the metadata, though the README badge says 3.14 and later (20). The CI workflow runs on pushes, pull requests and nightly, on a five-version Python matrix against a live Redis with pytest and an 80 per cent coverage floor, but its run results couldn't be read on 4 November 2026 (GitHub's pages and API answered 403), so 15 under this run's reading for test CI with an unreadable result. Fresh PyPI installs failed to start from 28 July to 5 August 2026 after mcp 2.0.0 removed the module the server imports, fixed in 0.5.1 (issues #163 and #169). Issue #156, where the console command ignores REDIS_HOST and REDIS_PORT, was open with two unmerged fixes per the 9 October check (13 of 25). Tagged releases with numbers in semantic form, but no changelog file, release notes that are lists of pull request titles, and a patch release (0.5.1) that changed the unsubscribe input and added six tools. Issue #137 asking for semver tags had no reply (4 of 15). Version 0.5.1 with the classifier Development Status :: 4 - Beta (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.

Redis MCP 77

MIT (30). Local software that connects to the configured Redis. search_redis_documents sends each question to redis.io, which the README mentions through MCP_DOCS_SEARCH_URL without saying what is sent or kept. The Redis Privacy Policy, last updated 29 November 2024, does not address this software, and no telemetry code was found in the 0.5.1 source (18 of 30). No deprecation policy. The README warns that the main branch may contain breaking changes, and the unsubscribe change in 0.5.1 came with no notice (4 of 20). No usage statistics on the evidence of the source. The docs search call can be redirected or switched off with an empty MCP_DOCS_SEARCH_URL, which the README does not present as an opt-out (13 of 20).

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.

Redis MCP 54

The server holds one Redis username and password, which Redis ACL rules can scope to keys and command categories and an admin can revoke, or Entra ID credentials for Azure Managed Redis with token renewal. TLS certificate checks are required by default. The README's main example passes the password inside --url on the command line, and every caller shares the one user (22 of 30). The server has no read-only mode, no allowlist and no confirmation before delete, json_del, xdel or xgroup_destroy. The README gives an ACL example for a read-only user, and no tool runs an arbitrary command, so FLUSHALL, CONFIG and EVAL are out of reach (9 of 20). Stored values, pub/sub messages and docs search results reach the model as they are. No injection guidance was found in the README or the docs pages read (2 of 15). Logging goes to stderr at WARNING by default, so calls are not recorded unless the level is lowered. The connection names itself redis-py(mcp-server_v0.5.1), which Redis shows in CLIENT LIST (6 of 15). Redis has a valid security.txt, a HackerOne disclosure programme, and SOC 2 Type 2 and ISO/IEC 27001 on its trust centre. CI runs Bandit and hardened runners, and Dependabot updates are merged within days. The repository has no SECURITY.md and no published advisories (15 of 20).

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.

Redis MCP 64

Each tool is built from a typed Python signature through FastMCP, so inputs carry JSON Schema, read from the source since we do not run vendor software. get_vector_from_hash has no return type, several tools return either a value or an error string, and there are no output schemas (21 of 25). redis.io serves llms.txt and a Markdown form of each docs page, and the README is Markdown (10). Most descriptions are one line plus an argument list. scan_keys, scan_all_keys, hybrid_search and xreadgroup say when to use them and what to avoid, and the rest do not (11 of 20). Required fields and defaults are typed, but there are no enums (distance_metric and the info section are free strings) and the bounds on block_ms, timeout_ms and max_messages are checked in code, not declared in the schema (8 of 15). The README and docs pages give client configuration examples. Tool examples exist only inside a few descriptions, and no list of error responses was found (6 of 15). Tagged versions and GitHub release notes, with no changelog file. The 0.4.0 notes name the docs tool search_documents where the source has search_redis_documents, and Redis's docs page still links a Smithery install that the README dropped in 0.3.5 (8 of 15).