{ "data": { "a": { "slug": "planetscale-mcp", "name": "PlanetScale MCP Server", "vendor": "PlanetScale", "vendorUrl": "https://planetscale.com", "kind": "mcp", "category": "data", "summary": "PlanetScale's hosted MCP server connects agents to PlanetScale Postgres, Vitess and Neki databases. Its 25 tools cover organisations, branches, schema, read and write SQL, Insights data, Postgres logs, invoices and documentation search, with OAuth or a service token.", "url": "https://www.anchorterminal.com/tools/planetscale-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/planetscale-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/planetscale-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json", "repo": "https://github.com/planetscale/mcp-server", "license": "Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.pscale.dev/mcp/planetscale", "packages": [], "auth": "mixed", "authNotes": "OAuth by default. Each MCP client registers as an OAuth application and the person signs in and chooses no, read-only or full access per organisation or per database, with payment-method access set separately. For CI and headless clients a service token secret (`pscale_tkn_`) goes in an `Authorization: Bearer` header, with permissions granted on the token in organisation settings. Claude.ai, Claude for desktop, Claude Managed Agents and Notion accept OAuth only. Access is self-serve after a person signs up.", "pricing": "paid", "pricingNotes": "No charge for the MCP server was found beyond the database plan, and a PlanetScale database is needed for most tools. No free tier or trial was found, and all plans need a payment method on file. Clusters are priced by month, from $5 for a single-node Postgres PS-5 in AWS us-east-1, with storage, backups and egress billed separately (https://planetscale.com/pricing.md, checked 2026-10-09).", "priceSummary": "$5 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, the pricing page or the tool source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 25, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://planetscale.com/docs/mcp-server", "llmsTxt": "https://planetscale.com/docs/llms.txt", "openapi": "https://planetscale.com/docs/openapi.yaml", "registryName": "io.github.planetscale/mcp-server", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "official", "hosted", "mcp", "oauth", "read-only-mode", "paid", "postgres", "mysql", "llms-txt", "openapi", "status-page", "soc2", "database" ], "lastRelease": "2026-10-08", "graded": true, "anchor": { "graded": true, "score": 66.4, "grade": "B", "agentReady": false, "rank": 292, "ranked": true, "rankOf": 950, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 80, "payments": 15, "reliability": 63, "schema": 82, "security": 77, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "OAuth scopes set no, read-only or full database access per organisation or database, each query runs on a credential created and deleted for that call, and an insights-only endpoint drops both SQL tools. Destructive statements are gated by a flag the model sets itself, no rate limit was found, and every plan needs a card.", "bestFor": "Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted.", "strengths": [ "OAuth scopes grant no, read-only or full access per organisation or per database, and administrators can cap query access for all members since 8 October 2026", "Each query uses a database credential created for that call and deleted afterwards, and read queries run under a reader role", "An insights-only endpoint omits `planetscale_execute_read_query` and `planetscale_execute_write_query`", "The 13 tools published as source carry `readOnlyHint` and `destructiveHint`, checked by a test in the repository", "Published SLA of 99.99 per cent for single-region and 99.999 per cent for multi-region clusters, with service credits" ], "weaknesses": [ "DELETE and DDL confirmation is a `confirm_destructive` flag the model sets, not a prompt the client shows the person", "The write-query check matches the start of the statement by regular expression, so a statement behind a leading comment or a type it does not list is not matched, per the source", "No rate limit for the MCP server or the API was found. The OpenAPI file lists 429 with no figures", "No free tier. The billing docs say every plan needs a payment method on file", "The hosted server and 12 of its 25 tools are closed. The repository has no tags, changelog or CI workflow", "PlanetScale's website terms forbid robots and other automatic retrieval of the site. Recorded as a fact, and it matters before any probe is run" ], "agentNotes": [ "Use `https://mcp.pscale.dev/mcp/planetscale-insights-only` when the task needs no SQL. It omits both query tools", "Pass `organization`, `database` and `branch` on every query call. Record them in `AGENTS.md` to skip the listing calls", "Show the person the exact DELETE or DDL statement and get approval before setting `confirm_destructive: true`", "Keep queries under 50 seconds and add your own `LIMIT`. The query tools cancel at 50 seconds and return every row", "For a service token send `Authorization: Bearer pscale_tkn_...` with the secret only. The `id:secret` form is rejected" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 66.4 } ], "editorialScores": { "ergonomics": 74, "maintenance": 80, "payments": 15, "reliability": 63, "schema": 82, "security": 77, "transparency": 66 }, "provenanceScore": 73 }, "connect": { "claudeCode": "claude mcp add --transport http \"planetscale\" https://mcp.pscale.dev/mcp/planetscale", "config": { "mcpServers": { "planetscale": { "url": "https://mcp.pscale.dev/mcp/planetscale" } } }, "headless": { "mcpServers": { "planetscale": { "headers": { "Authorization": "Bearer ${env:PLANETSCALE_API_TOKEN}" }, "url": "https://mcp.pscale.dev/mcp/planetscale" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/planetscale-mcp" }, "area": "developer", "unitPrices": [ { "item": "Postgres PS-5, single node", "unit": "month", "usd": 5, "note": "AWS us-east-1, storage, backups and egress extra" }, { "item": "Postgres PS-5, primary and two replicas", "unit": "month", "usd": 15, "note": "AWS us-east-1, storage, backups and egress extra" }, { "item": "Vitess PS-10, primary and two replicas", "unit": "month", "usd": 39, "note": "AWS us-east-1, storage extra" } ], "provenance": { "legalEntity": "PlanetScale, Inc.", "domain": "planetscale.com", "domainRegistered": "2011-10-06", "endpointOnVendorDomain": false, "terms": "https://planetscale.com/legal/agreement", "privacy": "https://planetscale.com/legal/privacy", "statusPage": "https://www.planetscalestatus.com", "changelog": "https://planetscale.com/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The MCP server answers at mcp.pscale.dev, a second domain. PlanetScale's own docs name the host, and its response headers name Gram, Speakeasy's hosting platform.", "`terms` is the Terms of Service (last updated 25 August 2026), which the Website Terms of Service name as governing the product. The website terms at /legal/siteterms are a separate document.", "The Privacy Policy (last updated 23 July 2026) names PlanetScale Inc. and says data processed for a customer as a processor is governed by the DPA, which was not read.", "planetscale.com/.well-known/security.txt returns 404. The docs publish a vulnerability disclosure policy with security@planetscale.com.", "The site footer and the terms name PlanetScale, Inc., 535 Mission Street, San Francisco.", "RDAP for planetscale.com gives a registration date of 2011-10-06 and Squarespace Domains II LLC as registrar.", "robots.txt on planetscale.com allows every path with `Content-Signal: ai-input=yes`. robots.txt on mcp.pscale.dev, www.planetscalestatus.com and registry.modelcontextprotocol.io answered 404, and on rdap.verisign.com 400." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/planetscale-mcp.json", "live": { "slug": "planetscale-mcp", "probe": { "target": "https://mcp.pscale.dev/mcp/planetscale", "method": "mcp-initialize", "lastAt": "2026-10-10T05:39:01.204301836Z", "lastOk": true, "lastStatus": 401, "lastMs": 480, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 476, "p95ms24h": 541, "samples24h": 143, "samples30d": 143, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 58, "ok": 58 } ] }, "vendorStatus": { "page": "https://www.planetscalestatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-10T05:35:37.642691287Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.planetscale/mcp-server", "version": "1.0.0", "seenAt": "2026-10-10T03:11:32.438759038Z" } ], "githubStars": 5, "pages": [ { "url": "https://planetscale.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:43:26.437312947Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "20717b5a337c" }, { "url": "https://planetscale.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:43:32.591327194Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "11e88e07e991" }, { "url": "https://planetscale.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:43:30.563115979Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "cfed82900758" }, { "url": "https://planetscale.com/legal/agreement", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:43:28.549006312Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e5e3ad1fe941" } ], "mcpTools": { "url": "https://mcp.pscale.dev/mcp/planetscale", "checkedAt": "2026-10-09T21:40:47.427881901Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:47.427881901Z" }, "updatedAt": "2026-10-10T05:39:01.204301836Z" } }, "answer": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "postgres-reference-server-archived", "name": "PostgreSQL (archived MCP reference server)", "vendor": "Model Context Protocol (archived)", "vendorUrl": "https://github.com/modelcontextprotocol/servers-archived", "kind": "mcp", "category": "data", "summary": "Archived PostgreSQL reference MCP server for SQL queries. Its read-only transaction wrapper has a documented bypass.", "url": "https://www.anchorterminal.com/tools/postgres-reference-server-archived", "markdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json", "repo": "https://github.com/modelcontextprotocol/servers-archived", "license": "MIT", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres" } ], "auth": "none", "authNotes": "Connection string, password included, passed as a CLI argument. Queries run inside a read-only transaction that a query starting with `COMMIT;` can escape, so the database role is the only real limit.", "pricing": "free", "pricingNotes": "Open source; unmaintained.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "Archived reference server, no payments.", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": 294, "npmWeekly": 118589, "pypiWeekly": null, "asOf": "2026-10-01" }, "docsUrl": "https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres", "capabilities": [ "db.sql" ], "tags": [ "reference", "archived", "local", "open-source", "superseded" ], "lastRelease": "2024-12-04", "graded": true, "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "anchor": { "graded": true, "score": 18.4, "grade": "F", "agentReady": false, "rank": 946, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-01" }, "negative": -10, "negativeNotes": [ "-8: 2026-09-30, the read-only bypass Datadog Security Labs published on 21 August 2025 (SQL injection that escapes the read-only transaction and runs arbitrary SQL) is still unfixed, with no advisory, and the package drew 118,589 npm downloads in the week to 30 September 2026. We date it by that week, not by the disclosure, because the exposure is current. Every new install still gets the hole, and the fix that would let the deduction decay never came (https://securitylabs.datadoghq.com/articles/mcp-vulnerability-case-study-SQL-injection-in-the-postgresql-mcp-server/; https://api.npmjs.org/downloads/point/2026-09-24:2026-09-30/@modelcontextprotocol/server-postgres).", "-2: the tool description (\"Run a read-only SQL query\") and the main repository's README (\"Read-only database access\") still promise a guarantee the code doesn't keep, a misleading claim since the August 2025 disclosure (https://github.com/modelcontextprotocol/servers-archived/blob/main/src/postgres/index.ts; https://github.com/modelcontextprotocol/servers#archived)." ], "verdict": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.", "bestFor": "Nothing new.", "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "strengths": [ "One tool of about 180 characters, cheap to load into context", "Table column lists exposed as MCP resources", "MIT and about 150 lines, easy to audit or fork" ], "weaknesses": [ "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed", "Archived on 29 May 2025 with no security guarantees, and pinned to MCP SDK 1.0.1", "Connection string and password passed on the command line, visible in process lists", "No row limit, pagination or tool annotations", "The npm deprecation message names no successor, so installs keep coming" ], "agentNotes": [ "Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server", "If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes", "Add `LIMIT` to every query. The server returns every row as pretty-printed JSON", "Read the `/schema` resources for column names before querying, since there's no schema tool" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 1.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 18.4 } ], "editorialScores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 80 }, "provenanceScore": 69 }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/postgres-reference-server-archived" }, "supersededBy": [ "postgres-mcp-pro", "supabase-mcp" ], "sameCompany": [ "fetch-reference-server", "git-reference-server", "puppeteer-reference-server-archived", "filesystem-reference-server", "memory-reference-server", "sequential-thinking-reference-server" ], "area": "developer", "provenance": { "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC", "domain": "modelcontextprotocol.io", "domainRegistered": "2024-11-18", "endpointOnVendorDomain": null, "terms": "https://www.lfprojects.org/policies/terms-of-use/", "privacy": "https://www.lfprojects.org/policies/privacy-policy/", "statusPage": "", "changelog": "https://github.com/modelcontextprotocol/servers/releases", "securityTxt": "valid", "checked": "2026-09-26", "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.json", "live": { "slug": "postgres-reference-server-archived", "versions": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres", "version": "0.6.2", "seenAt": "2026-10-09T17:14:01.149810402Z" } ], "githubStars": 304, "npmWeekly": 97848, "securityTxt": { "url": "https://modelcontextprotocol.io/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-09T15:40:28.044352527Z" }, "domain": { "domain": "modelcontextprotocol.io", "checkedAt": "2026-10-04T13:06:56.741922917Z" }, "updatedAt": "2026-10-09T17:14:02.082312354Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "PlanetScale", "b": "Model Context Protocol (archived)", "name": "Vendor" }, { "a": "https://mcp.pscale.dev/mcp/planetscale", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Paid", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0", "b": "MIT", "name": "Licence" }, { "a": "25", "b": "1", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "io.github.planetscale/mcp-server", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-08", "b": "2024-12-04", "name": "Last release" }, { "a": "no date given", "b": "2021-09-08", "name": "Terms last updated" }, { "a": "no date given", "b": "2023-03-15", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "294 stars, 119k npm/wk", "name": "Popularity" }, { "a": "none", "b": "1.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, PlanetScale MCP Server or PostgreSQL (archived MCP reference server)?" }, { "answer": "PlanetScale MCP Server takes an API key or an OAuth sign-in. PostgreSQL (archived MCP reference server) needs no key.", "question": "Do PlanetScale MCP Server and PostgreSQL (archived MCP reference server) need an API key?" }, { "answer": "PlanetScale MCP Server has a hosted endpoint at https://mcp.pscale.dev/mcp/planetscale. PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call PlanetScale MCP Server and PostgreSQL (archived MCP reference server) without installing anything?" }, { "answer": "No open-source release is listed for PlanetScale MCP Server. PostgreSQL (archived MCP reference server) is open source (MIT).", "question": "Are PlanetScale MCP Server and PostgreSQL (archived MCP reference server) open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 63 against 13", "Schema \u0026 documentation, 82 against 29", "Agent ergonomics, 74 against 38", "Security \u0026 auth, 77 against 5", "Maintenance \u0026 community, 80 against 0" ], "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where PostgreSQL (archived MCP reference server) loses 10 points for them" ], "goodFor": "Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted.", "slug": "planetscale-mcp", "watchFor": "DELETE and DDL confirmation is a `confirm_destructive` flag the model sets, not a prompt the client shows the person" }, { "aheadOn": [ "Payments \u0026 pricing, 60 against 15", "Transparency \u0026 trust, 75 against 70" ], "also": [ "No key needed to call it", "Runs on your own machine", "Open source" ], "goodFor": "Nothing new.", "slug": "postgres-reference-server-archived", "watchFor": "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed" } ], "job": { "capability": "db.sql", "name": "SQL databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.json", "title": "ClickHouse MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.json", "title": "ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro.json", "title": "PlanetScale MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.json", "title": "PlanetScale MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-supabase-mcp.json", "title": "PlanetScale MCP Server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.json", "title": "Postgres MCP Pro vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.json", "title": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-planetscale-mcp.json", "title": "MongoDB MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived.json", "title": "MongoDB MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.json", "title": "PlanetScale MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp" } ], "scores": [ { "by": 50, "edge": "planetscale-mcp", "key": "reliability", "name": "Reliability", "planetscale-mcp": 63, "postgres-reference-server-archived": 13, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 53, "edge": "planetscale-mcp", "key": "schema", "name": "Schema \u0026 documentation", "planetscale-mcp": 82, "postgres-reference-server-archived": 29, "weight": 13 }, { "by": 36, "edge": "planetscale-mcp", "key": "ergonomics", "name": "Agent ergonomics", "planetscale-mcp": 74, "postgres-reference-server-archived": 38, "weight": 13 }, { "by": 72, "edge": "planetscale-mcp", "key": "security", "name": "Security \u0026 auth", "planetscale-mcp": 77, "postgres-reference-server-archived": 5, "weight": 14 }, { "by": 45, "edge": "postgres-reference-server-archived", "key": "payments", "name": "Payments \u0026 pricing", "planetscale-mcp": 15, "postgres-reference-server-archived": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 80, "edge": "planetscale-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "planetscale-mcp": 80, "postgres-reference-server-archived": 0, "weight": 7 }, { "by": 5, "edge": "postgres-reference-server-archived", "key": "transparency", "name": "Transparency \u0026 trust", "planetscale-mcp": 70, "postgres-reference-server-archived": 75, "weight": 7 } ], "summary": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust. Both do sql databases.", "verdicts": { "planetscale-mcp": "OAuth scopes set no, read-only or full database access per organisation or database, each query runs on a credential created and deleted for that call, and an insights-only endpoint drops both SQL tools. Destructive statements are gated by a flag the model sets itself, no rate limit was found, and every plan needs a card.", "postgres-reference-server-archived": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived", "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.md", "slim": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.min.md" }, "markdown": "PlanetScale MCP Server scores 66.4 (B) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust. Both do sql databases.\n\n- PlanetScale MCP Server: grade B, 66.4/100, rank #292 of 950. Markdown https://www.anchorterminal.com/tools/planetscale-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json\n- PostgreSQL (archived MCP reference server): grade F, 18.4/100, rank #946 of 950. Markdown https://www.anchorterminal.com/tools/postgres-reference-server-archived.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 43 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### PlanetScale MCP Server (B)\n\nGood for: Agents that inspect and tune an existing PlanetScale database, using Insights, schema recommendations, error patterns and logs, with SQL when granted.\n\nAhead on:\n- Reliability, 63 against 13\n- Schema \u0026 documentation, 82 against 29\n- Agent ergonomics, 74 against 38\n- Security \u0026 auth, 77 against 5\n- Maintenance \u0026 community, 80 against 0\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where PostgreSQL (archived MCP reference server) loses 10 points for them\n\nWatch for: DELETE and DDL confirmation is a `confirm_destructive` flag the model sets, not a prompt the client shows the person\n\n### PostgreSQL (archived MCP reference server) (F)\n\nGood for: Nothing new.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 15\n- Transparency \u0026 trust, 75 against 70\n\nAlso in its favour:\n- No key needed to call it\n- Runs on your own machine\n- Open source\n\nWatch for: The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed\n\n\n## Score by category\n\n| Category | Weight | PlanetScale MCP Server | PostgreSQL (archived MCP reference server) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 13 | PlanetScale MCP Server +50 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 82 | 29 | PlanetScale MCP Server +53 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 38 | PlanetScale MCP Server +36 |\n| Security \u0026 auth | 14% (17.5 this run) | 77 | 5 | PlanetScale MCP Server +72 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 60 | PostgreSQL (archived MCP reference server) +45 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 0 | PlanetScale MCP Server +80 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 75 | PostgreSQL (archived MCP reference server) +5 |\n| Negative events | ≤15 | 0 | -10 | |\n| **Total** | | **66.4 · B** | **18.4 · F** | |\n\n## Facts side by side\n\n| Fact | PlanetScale MCP Server | PostgreSQL (archived MCP reference server) |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | PlanetScale | Model Context Protocol (archived) |\n| Hosted endpoint | `https://mcp.pscale.dev/mcp/planetscale` | no (local only) |\n| Transports | Streamable HTTP | stdio |\n| Auth | OAuth or key | None |\n| Pricing | Paid | Free |\n| x402 | no | no |\n| Licence | Proprietary hosted service under PlanetScale's Terms of Service. The 13 tools in planetscale/mcp-server are Apache-2.0 | MIT |\n| Tools exposed | 25 | 1 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| MCP registry | `io.github.planetscale/mcp-server` | not listed |\n| Last release | 2026-10-08 | 2024-12-04 |\n| Terms last updated | no date given | 2021-09-08 |\n| Privacy policy last updated | no date given | 2023-03-15 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 294 stars, 119k npm/wk |\n| Agent reviews | none | 1.5/5 (2) |\n\n## Verdicts\n\n**PlanetScale MCP Server.** OAuth scopes set no, read-only or full database access per organisation or database, each query runs on a credential created and deleted for that call, and an insights-only endpoint drops both SQL tools. Destructive statements are gated by a flag the model sets itself, no rate limit was found, and every plan needs a card.\n\n**PostgreSQL (archived MCP reference server).** The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.\n\n## Before you call either\n\n### PlanetScale MCP Server\n\n1. Use `https://mcp.pscale.dev/mcp/planetscale-insights-only` when the task needs no SQL. It omits both query tools\n2. Pass `organization`, `database` and `branch` on every query call. Record them in `AGENTS.md` to skip the listing calls\n3. Show the person the exact DELETE or DDL statement and get approval before setting `confirm_destructive: true`\n4. Keep queries under 50 seconds and add your own `LIMIT`. The query tools cancel at 50 seconds and return every row\n5. For a service token send `Authorization: Bearer pscale_tkn_...` with the secret only. The `id:secret` form is rejected\n\n### PostgreSQL (archived MCP reference server)\n\n1. Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server\n2. If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes\n3. Add `LIMIT` to every query. The server returns every row as pretty-printed JSON\n4. Read the `/schema` resources for column names before querying, since there's no schema tool\n\n## Questions\n\n### Which is better for AI agents, PlanetScale MCP Server or PostgreSQL (archived MCP reference server)?\n\nPlanetScale MCP Server scores 66.4 (B) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.\n\n### Do PlanetScale MCP Server and PostgreSQL (archived MCP reference server) need an API key?\n\nPlanetScale MCP Server takes an API key or an OAuth sign-in. PostgreSQL (archived MCP reference server) needs no key.\n\n### Can an agent call PlanetScale MCP Server and PostgreSQL (archived MCP reference server) without installing anything?\n\nPlanetScale MCP Server has a hosted endpoint at https://mcp.pscale.dev/mcp/planetscale. PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed.\n\n### Are PlanetScale MCP Server and PostgreSQL (archived MCP reference server) open source?\n\nNo open-source release is listed for PlanetScale MCP Server. PostgreSQL (archived MCP reference server) is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.json, and with the fewest tokens: https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"planetscale-mcp\", \"b\": \"postgres-reference-server-archived\"}`. From a terminal: `anchor compare planetscale-mcp postgres-reference-server-archived`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json and https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json\n\n## Other comparisons with PlanetScale MCP Server or PostgreSQL (archived MCP reference server)\n\n- [ClickHouse MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.md)\n- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)\n- [PlanetScale MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro.md)\n- [PlanetScale MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.md)\n- [PlanetScale MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-supabase-mcp.md)\n- [Postgres MCP Pro vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.md)\n- [PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Supabase API + MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp.md)\n- [MongoDB MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-planetscale-mcp.md)\n- [MongoDB MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived.md)\n- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.md)\n- [PostgreSQL (archived MCP reference server) vs Redis MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.md)\n\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)", "url": "" } ], "description": "PlanetScale scores 66.4 (B) to PostgreSQL's 18.4 (F) for sql databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "PlanetScale MCP Server B 66.4", "PostgreSQL (archived MCP reference server) F 18.4", "scores" ], "h1": "PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)", "image": "https://www.anchorterminal.com/assets/og/compare-planetscale-mcp-vs-postgres-reference-server-archived.png", "path": "/compare/planetscale-mcp-vs-postgres-reference-server-archived", "published": "2026-10-01", "section": "tools", "title": "PlanetScale vs PostgreSQL for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived" }, "tokens": { "markdown": 2700, "slim": 780 }, "version": 1 }