# DBHub vs PlanetScale MCP Server (slim)

> DBHub and PlanetScale score within a point of each other for sql databases, 70.4 and 69.6 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dbhub-vs-planetscale-mcp.md (~4,900 tokens) · this version ~3,130 tokens · JSON https://www.anchorterminal.com/compare/dbhub-vs-planetscale-mcp.json · canonical https://www.anchorterminal.com/compare/dbhub-vs-planetscale-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 and PlanetScale MCP Server score within a point of each other on agent readiness, 70.4 (BB) and 69.6 (B). PlanetScale MCP Server leads on schema & documentation, security & auth and transparency & trust. Both do sql databases.

- DBHub: BB 70.4, rank #200 of 1486 · https://www.anchorterminal.com/tools/dbhub.min.md
- PlanetScale MCP Server: B 69.6, rank #233 of 1486 · https://www.anchorterminal.com/tools/planetscale-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 Agent ergonomics, 85 against 74; Payments & pricing, 60 against 15; Maintenance & community, 95 against 80. Also Agent-ready, a grade of BB or better; No key needed to call it; Runs on your own machine; Open source.
- PlanetScale MCP Server, good for Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted. Ahead on Schema & documentation, 82 against 73; Security & auth, 77 against 43; Transparency & trust, 72 against 61. Also A hosted endpoint, with nothing to install.

| Category | DBHub | PlanetScale MCP Server |
| --- | --- | --- |
| Reliability (16%) | 80 | 78 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 73 | 82 |
| Agent ergonomics (13%) | 85 | 74 |
| Security & auth (14%) | 43 | 77 |
| Payments & pricing (10%) | 60 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 95 | 80 |
| Transparency & trust (7%) | 61 | 72 |

| Fact (where they differ) | DBHub | PlanetScale MCP Server |
| --- | --- | --- |
| Vendor | Bytebase | PlanetScale |
| Hosted endpoint | no (local only) | `https://mcp.pscale.dev/mcp/planetscale` |
| Transports | stdio, Streamable HTTP | Streamable HTTP |
| Auth | None | OAuth or key |
| Pricing | Free | Paid |
| Licence | MIT | Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0 |
| Tools exposed | 2 | 26 |
| MCP registry | `io.github.bytebase/dbhub` | `io.github.planetscale/mcp-server` |
| Last release | 2026-11-03 | 2026-10-11 |
| Terms last updated | no document linked | no date given |
| 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 | 3.5/5 (4) |

Why the edge:
- Payments & pricing, DBHub +45: DBHub 60 (Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0).); PlanetScale MCP Server 15 (No x402, MPP or L402 in the MCP docs, the pricing page or the source (0). Monthly prices for every cluster size are public without a login, as a Markdown page and as a read-only SQL catalogue, from $5 a month for a single-node Postgres PS-5. Storage, backup and egress rates were not on the page read, and there is no per-call price (15). No free tier or trial was found, and the billing docs say all plans need a valid payment method on file (0). A person signs up in a browser and authorises OAuth or creates a service token in organisation settings (0). Total 15.)
- Security & auth, PlanetScale MCP Server +34: 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.); PlanetScale MCP Server 77 (OAuth with each client registered as an OAuth application, scopes that set no, read-only or full access per organisation or per database, a separate payment-method scope, and service tokens with per-permission grants for headless use. Each query runs on a database credential created for the call and deleted after it (30). Read queries use a reader password on Vitess and a `pg_read_all_data` role on Postgres that does not bypass row-level security. An insights-only endpoint has no SQL tools, and since 8 October 2026 administrators can cap members' grants at none, read-only or read and write. TRUNCATE and UPDATE or DELETE without WHERE are blocked. DELETE and DDL need `confirm_destructive`, which the model sets itself, and the check is a regular expression on the start of the statement. Write queries run as the `postgres` role or a Vitess admin password. Read and write is the default (16). Query results return database content to the model. The docs warn about write access to production, and no prompt-injection guidance or result wrapping was found (4). Organisation audit log and security log on all plans, service tokens showing the IP address they were last used from since 26 October, every MCP query tagged `source=planetscale-mcp` in Insights, and a list of installed OAuth apps with revoke (13). Vulnerability disclosure policy with security@planetscale.com, SOC 1 Type 2 and SOC 2 Type 2 with HIPAA, PCI DSS for PlanetScale Managed. security.txt returned 404 on 1 November and no bug bounty was found (14). Total 77.)
- Maintenance & community, DBHub +15: 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.); PlanetScale MCP Server 80 (The changelog's newest MCP entry is 9 October 2026 (`planetscale_get_branch_metrics`), and the repository's last commit is 11 October 2026 (30). Commits on 13 days from 18 August to 11 October added query tags, payment tools, annotations, Neki support and branch metrics, and the changelog has MCP or OAuth entries on 28 September, 8 October and 9 October (20). Closed hosted service with a dated public changelog, a support desk and a Discord community. The repository's issues and pull requests were not read (10). Listed in the official MCP registry as `io.github.planetscale/mcp-server`, a GitHub-verified namespace, still at version 1.0.0 published 15 April 2026 (15). Dependencies are current (`@modelcontextprotocol/sdk` ^1.30, zod 4) and the repository has unit tests, but no CI workflow is published (5). Total 80.)
- Agent ergonomics, DBHub +11: 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.); PlanetScale MCP Server 74 (26 tools since `planetscale_get_branch_metrics` arrived on 9 October (15). The insights-only endpoint drops the two SQL tools, and OAuth scopes limit which tool groups a client is granted (5). Insights, error, tag and log tools take `limit` with documented maxima and report `truncated` or `has_next`, and the logs tool pages. `planetscale_execute_read_query` returns every row with no cap (15). Error texts say what to do next, for example the safe-migrations message with two ways forward, the `postgres_rls_active` warning on empty results and the full-access message on a payment 403 (15). The 14 source tools set `readOnlyHint` and `destructiveHint`, with a test that fails on a missing annotation. Annotations on the 12 generated tools were not read. No idempotency for writes was found, though the payment tool tells the model not to start a second setup while one is pending (15). Sensible defaults (replica routing, 24-hour windows, curated metrics), but three identifiers are required on nearly every call. Official SDKs do not apply to a hosted MCP server and none were checked (9). Total 74.)
- Transparency & trust, PlanetScale MCP Server +11: 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.); PlanetScale MCP Server 72 (The tools PlanetScale maintains by hand are public under Apache-2.0. The hosted server, its OAuth layer and the 12 generated tools are closed, under the Terms of Service of 25 August 2026 (22). Privacy Policy of 23 July 2026, a DPA covering all plans and a data-locality statement in the security docs. Retention is described without periods, and the DPA was not read (20). The Terms of Service promise at least six months' notice before material functionality is discontinued, with exceptions. The docs say the local `pscale mcp` server has been removed, with no date (14). Customers choose the cloud region and the security docs refer to sub-processors, but the list was not read. The MCP endpoint's response headers name Gram, Speakeasy's hosting platform, and no page read says how tool calls are handled there (10). Total 66.)
- Schema & documentation, PlanetScale MCP Server +9: 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.); PlanetScale MCP Server 82 (The 14 tools in planetscale/mcp-server have typed zod input schemas, and the other 12 are generated from the public OpenAPI file at planetscale.com/docs/openapi.yaml, 304 operations (25). llms.txt and a Markdown twin of every docs page (10). The custom descriptions state purpose, limits and when to ask the person, for example the 50-second limit, row-level security on Postgres reads and the Checkout sequence for the payment tools. The generated tools are one-line summaries (17). Enums for log levels and summary fields, clamped limits and required fields. `organization`, `database` and `branch` are free strings and SQL is free text by nature (12). The docs give example prompts and a permissions table per tool. Tool errors are plain text beginning `Error:` with the API status code (10). The product changelog is dated and carries MCP entries, but the server has no version history of its own. The package is 0.0.0, the repository has no tags or changelog, and the registry entry has stayed at 1.0.0 since 15 April 2026 (8). Total 82. The tool definitions were read from the source and the docs, not from the live server, which answered 401 without a token on 9 October.)