# DBHub vs ReqRes MCP server (slim)

> DBHub scores 70.4 (BB) to ReqRes's 48.8 (D) for databases. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.md (~3,450 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.json · canonical https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp
- 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 ReqRes MCP server's 48.8 (D), and leads in every scored category. Both do databases.

- DBHub: BB 70.4, rank #201 of 1510 · https://www.anchorterminal.com/tools/dbhub.min.md
- ReqRes MCP server: D 48.8, rank #1114 of 1510 · https://www.anchorterminal.com/tools/reqres-mcp.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 30; Schema & documentation, 73 against 61; Agent ergonomics, 85 against 76; Security & auth, 43 against 33; Payments & pricing, 60 against 50; Maintenance & community, 95 against 50; Transparency & trust, 61 against 47. Also Agent-ready, a grade of BB or better; Runs on your own machine; Open source.
- ReqRes MCP server, good for Coding agents that need a throwaway or starter backend for a prototype, with no account to set up. Also A hosted endpoint, with nothing to install.

| Category | DBHub | ReqRes MCP server |
| --- | --- | --- |
| Reliability (16%) | 80 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 73 | 61 |
| Agent ergonomics (13%) | 85 | 76 |
| Security & auth (14%) | 43 | 33 |
| Payments & pricing (10%) | 60 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 95 | 50 |
| Transparency & trust (7%) | 61 | 47 |

| Fact (where they differ) | DBHub | ReqRes MCP server |
| --- | --- | --- |
| Vendor | Bytebase | ReqRes |
| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Pricing | Free | Freemium |
| Licence | MIT | none |
| Tools exposed | 2 | 7 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.bytebase/dbhub` | `in.reqres/reqres` |
| Last release | 2026-11-03 | none |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | not read yet |
| Popularity | 3.8k stars, 51k npm/wk | none |

Why the edge:
- Reliability, DBHub +50: 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.); ReqRes MCP server 30 (status.reqres.in wasn't reachable (0). No history (5). Free-plan limits published with numbers (250 requests a day, 3 collections, 100 records) (15). No retry guidance (0). No SLA found (0). Not labelled beta (10). 0 + 5 + 15 + 0 + 0 + 10 = 30.)
- Maintenance & community, DBHub +45: 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.); ReqRes MCP server 50 (Registry entry in.reqres/reqres updated 16 October 2026 (30). No dated releases found (0). Blog and docs; no changelog (5 of 15). Official registry entry under its own namespace (15). No package to read (0). 30 + 0 + 5 + 15 + 0 = 50. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Transparency & trust, DBHub +14: 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.); ReqRes MCP server 47 (Closed service under readable terms; operating company not named in the parts read (10 of 30). You own your data, unclaimed agent projects are deleted after 72 hours, and the terms say the free service can end with reasonable notice (22 of 30). That notice clause and the 72-hour rule are dated commitments (10 of 20). Subprocessors not found (5 of 20). 10 + 22 + 10 + 5 = 47.)
- Schema & documentation, DBHub +12: 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.); ReqRes MCP server 61 (Seven tools read from tools/list with JSON Schema inputs (25). llms.txt (10). A tool table says what each does (12 of 20). Records and fields are free-form objects (5 of 15). Worked flow on the MCP page, no error docs (6 of 15). Registry 1.0.0, no changelog (3 of 15). 25 + 10 + 12 + 5 + 6 + 3 = 61.)
- Security & auth, DBHub +10: 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.); ReqRes MCP server 33 (No credential to start, and project keys returned by the tool (15 of 30). Writes on the agent's own project only (12 of 20). Every successful result ends with a sponsored message, labelled and 'never written as an instruction', which still puts third-party text in the model's context (3 of 15). No audit log (0). No security programme found (3 of 20). 15 + 12 + 3 + 0 + 3 = 33.)
- Payments & pricing, DBHub +10: DBHub 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).); ReqRes MCP server 50 (No machine payment protocol (0). Plan prices public (10). Free plan (20). An agent creates a project with no person (20). 0 + 10 + 20 + 20 = 50.)