{ "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 26 tools cover organisations, branches, schema, read and write SQL, Insights data, branch metrics, 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", "dns": "planetscale-mcp.grade.anchorterminal.com", "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": 26, "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-11", "graded": true, "anchor": { "graded": true, "score": 69.6, "grade": "B", "agentReady": false, "rank": 234, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 80, "payments": 15, "reliability": 78, "schema": 82, "security": 77, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "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 limit is stated for the MCP server, 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 14 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", "The API's 600 requests a minute is the only limit found. The MCP docs state none, and 429 comes with no Retry-After", "No free tier. The billing docs say every plan needs a payment method on file", "The hosted server and 12 of its 26 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": 4, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 69.6 } ], "editorialScores": { "ergonomics": 74, "maintenance": 80, "payments": 15, "reliability": 78, "schema": 82, "security": 77, "transparency": 66 }, "provenanceScore": 77, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "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": 77 }, "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-11-07T23:26:48.707653247Z", "lastOk": true, "lastStatus": 401, "lastMs": 155, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.96, "p50ms24h": 145, "p95ms24h": 248, "samples24h": 244, "samples30d": 7256, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 252 }, { "date": "2026-10-16", "probes": 252, "ok": 251 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 249 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 238, "ok": 238 } ] }, "vendorStatus": { "page": "https://www.planetscalestatus.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T23:32:22.208302211Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.planetscale/mcp-server", "version": "1.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 5, "securityTxt": { "url": "https://planetscale.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:22.635023202Z" }, "llmsTxt": { "url": "https://planetscale.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:38.858290913Z" }, "domain": { "domain": "planetscale.com", "registered": "2011-10-06", "source": "https://rdap.verisign.com/com/v1/domain/planetscale.com", "checkedAt": "2026-11-01T14:21:13.086590033Z" }, "pages": [ { "url": "https://planetscale.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:16:37.190584149Z", "changedAt": "2026-11-06T13:38:16.294850604Z", "fingerprint": "d7627cafb558" }, { "url": "https://planetscale.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:16:43.415420482Z", "changedAt": "2026-11-07T14:16:43.415420482Z", "fingerprint": "0374efa5fd79" }, { "url": "https://planetscale.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:16:41.451426869Z", "changedAt": "2026-10-15T21:32:02.525502284Z", "fingerprint": "b25e6011bf8d" }, { "url": "https://planetscale.com/legal/agreement", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:16:39.383842996Z", "changedAt": "2026-10-15T21:32:00.376386679Z", "fingerprint": "124953c991ef" } ], "mcpTools": { "url": "https://mcp.pscale.dev/mcp/planetscale", "checkedAt": "2026-11-07T01:46:52.450368686Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:47.427881901Z" }, "github": { "repo": "planetscale/mcp-server", "checkedAt": "2026-11-02T09:17:17.901900393Z", "stars": 5, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-11T14:05:49Z", "openIssues": 0, "openPRs": 17, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 17 }, "updatedAt": "2026-11-07T23:32:22.208302211Z" } }, "answer": "PlanetScale MCP Server scores 69.6 (B) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing.", "b": { "slug": "reqres-mcp", "name": "ReqRes MCP server", "vendor": "ReqRes", "vendorUrl": "https://reqres.in", "kind": "mcp", "category": "data", "summary": "ReqRes' hosted MCP server lets a coding agent create a real hosted REST backend with no account, persistent JSON collections and API keys, then read and write its records. Unclaimed projects are deleted after 72 hours.", "url": "https://www.anchorterminal.com/tools/reqres-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/reqres-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/reqres-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json", "dns": "reqres-mcp.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://reqres.in/mcp", "packages": [], "auth": "none", "authNotes": "No authentication. create_project returns a manage key and a public key for the new project, and a claim link that moves it to a ReqRes account.", "pricing": "freemium", "pricingNotes": "Free plan, 250 requests a day, 3 collections and 100 records a project, with a daily cap on new projects; paid plans raise it to 10,000 requests a day and more (prices on the pricing page). Tool results end with a sponsored line unless ?sponsor=0 is added (checked 2026-11-07).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://reqres.in/mcp", "llmsTxt": "https://reqres.in/llms.txt", "registryName": "in.reqres/reqres", "capabilities": [ "db.document", "code.backend", "data.store" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "no-auth", "freemium", "free-tier", "llms-txt", "mcp-registry", "annotated-tools", "sponsored-results" ], "graded": true, "anchor": { "graded": true, "score": 48.8, "grade": "D", "agentReady": false, "rank": 1114, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 76, "maintenance": 50, "payments": 50, "reliability": 30, "schema": 61, "security": 33, "transparency": 47 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "ReqRes' MCP server is the quickest way for a coding agent to stand up a real hosted backend, with no account, seven annotated tools and paginated records. Every result carries a sponsored line by default, the free tier is small, and unclaimed projects vanish after 72 hours.", "bestFor": "Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.", "strengths": [ "A hosted backend from one call, with no account", "Seven compact annotated tools with paginated records", "A claim link moves the project to an account with data intact", "llms.txt and a plain REST API behind the tools" ], "weaknesses": [ "A sponsored line in every successful result unless ?sponsor=0", "Unclaimed projects are deleted after 72 hours", "Free plan of 250 requests a day", "Status page unreachable and no changelog" ], "agentNotes": [ "Add ?sponsor=0 to the server URL to keep ads out of context", "Give the user the claim link so the project survives 72 hours", "Use the public key in frontend code and keep the manage key server-side" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.8 } ], "editorialScores": { "ergonomics": 76, "maintenance": 50, "payments": 50, "reliability": 30, "schema": 61, "security": 33, "transparency": 47 }, "provenanceScore": 46, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http reqres 'https://reqres.in/mcp?sponsor=0'", "config": { "mcpServers": { "reqres": { "url": "https://reqres.in/mcp?sponsor=0" } } } }, "letme": { "capability": "https://letme.dev/db.document", "tool": "https://letme.dev/reqres-mcp" }, "area": "developer", "provenance": { "legalEntity": "ReqRes", "domain": "reqres.in", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "https://reqres.in/terms", "privacy": "https://reqres.in/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The operating company wasn't named in the parts of the terms and privacy policy read." ], "score": 46 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/reqres-mcp.json", "live": { "slug": "reqres-mcp", "probe": { "target": "https://reqres.in/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T23:26:51.623285274Z", "lastOk": true, "lastStatus": 200, "lastMs": 74, "lastNote": "initialize answered", "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 92, "p95ms24h": 188, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-07", "probes": 48, "ok": 48 } ] }, "updatedAt": "2026-11-07T23:26:51.623285274Z" } }, "edges": [ { "by": 48, "category": "reliability", "leads": "planetscale-mcp", "name": "Reliability", "reasons": { "a": "Graded as a hosted service. Status page at planetscalestatus.com on incident.io with per-region components (20). Its incident feed, readable on 1 November, lists six incidents since 3 August, each partial. Postgres management pages and API endpoints returned 500 errors from 12:17 to 12:24 UTC on 2 September, Vitess databases in four GCP regions lost connectivity on 5 September, branch creation was delayed in GCP europe-west-1 on 28 September, AWS us-east-1 cross-zone networking failed on 9 October, us-east-1 dashboard metrics had a gap on 20 October, and on 26 October \"certain branches\" of Vitess lost connectivity and credential changes were delayed for about 1 hour 40 minutes, which touches the query tools' per-call credentials. Minor only (20). The API reference's rate-limit page gives 600 requests a minute for the PlanetScale API, \"subject to change\". The MCP docs don't say whether tool calls count against it. Twelve of the tools are generated from the API's own operations, and supabase-mcp, cloudflare-mcp, github-mcp-server and stripe-mcp take their vendor API's published limit for the server (15). The OpenAPI file and the rate-limit page list a 429 response with no Retry-After or backoff guidance, and no idempotency key for writes. The 50-second query limit is documented (3). The SLA commits to 99.99 per cent for single-region and 99.999 per cent for multi-region clusters with service credits, and excludes single-node clusters and beta functions (10). The docs give the MCP server no beta or preview label and the registry entry is 1.0.0 (10). 20 + 20 + 15 + 3 + 10 + 10 = 78.", "b": "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." }, "scores": { "a": 78, "b": 30 } }, { "by": 44, "category": "security", "leads": "planetscale-mcp", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 77, "b": 33 } }, { "by": 35, "category": "payments", "leads": "reqres-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 15, "b": 50 } }, { "by": 30, "category": "maintenance", "leads": "planetscale-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 80, "b": 50 } }, { "by": 25, "category": "transparency", "leads": "planetscale-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 72, "b": 47 } }, { "by": 21, "category": "schema", "leads": "planetscale-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 82, "b": 61 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "PlanetScale", "b": "ReqRes", "name": "Vendor" }, { "a": "https://mcp.pscale.dev/mcp/planetscale", "b": "https://reqres.in/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "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": "none", "name": "Licence" }, { "a": "26", "b": "7", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.planetscale/mcp-server", "b": "in.reqres/reqres", "name": "MCP registry" }, { "a": "2026-10-11", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "not read yet", "name": "Terms last updated" }, { "a": "no date given", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "3.5/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "PlanetScale MCP Server scores 69.6 (B) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing.", "question": "Which is better for AI agents, PlanetScale MCP Server or ReqRes MCP server?" }, { "answer": "PlanetScale MCP Server takes an API key or an OAuth sign-in. ReqRes MCP server needs no key.", "question": "Do PlanetScale MCP Server and ReqRes MCP server need an API key?" }, { "answer": "Yes. PlanetScale MCP Server has a hosted endpoint at https://mcp.pscale.dev/mcp/planetscale and ReqRes MCP server at https://reqres.in/mcp.", "question": "Can an agent call PlanetScale MCP Server and ReqRes MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 78 against 30", "Schema \u0026 documentation, 82 against 61", "Security \u0026 auth, 77 against 33", "Maintenance \u0026 community, 80 against 50", "Transparency \u0026 trust, 72 against 47" ], "also": null, "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, 50 against 15" ], "also": [ "No key needed to call it" ], "goodFor": "Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.", "slug": "reqres-mcp", "watchFor": "A sponsored line in every successful result unless ?sponsor=0" } ], "history": { "planetscale-mcp": [ { "causes": [ "evidence" ], "date": "2026-11-01", "delta": 3, "from": 66.6, "fromGrade": "B", "to": 69.6, "toGrade": "B" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 66.4, "fromGrade": "B", "to": 66.6, "toGrade": "B" } ], "reqres-mcp": null }, "job": { "capability": "db.database", "name": "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/dbhub-vs-planetscale-mcp.json", "title": "DBHub vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-planetscale-mcp.json", "title": "MCP Toolbox for Databases vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.json", "title": "Neon MCP Server vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp.json", "title": "ObsessionDB vs PlanetScale MCP Server", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp" }, { "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-postgres-reference-server-archived.json", "title": "PlanetScale MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived" }, { "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/clickhouse-mcp-server-vs-reqres-mcp.json", "title": "ClickHouse MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.json", "title": "DBHub vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-reqres-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/neon-mcp-vs-reqres-mcp.json", "title": "Neon MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.json", "title": "ObsessionDB vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp" }, { "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-mcp-pro-vs-reqres-mcp.json", "title": "Postgres MCP Pro vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.json", "title": "ReqRes MCP server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp.json", "title": "ReqRes MCP server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp.json", "title": "MCP Toolbox for Databases vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.json", "title": "MongoDB MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp" }, { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.json", "title": "Redis MCP vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp" } ], "panel": null, "scores": [ { "by": 48, "edge": "planetscale-mcp", "key": "reliability", "name": "Reliability", "planetscale-mcp": 78, "reqres-mcp": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 21, "edge": "planetscale-mcp", "key": "schema", "name": "Schema \u0026 documentation", "planetscale-mcp": 82, "reqres-mcp": 61, "weight": 13 }, { "by": 2, "edge": "reqres-mcp", "key": "ergonomics", "name": "Agent ergonomics", "planetscale-mcp": 74, "reqres-mcp": 76, "weight": 13 }, { "by": 44, "edge": "planetscale-mcp", "key": "security", "name": "Security \u0026 auth", "planetscale-mcp": 77, "reqres-mcp": 33, "weight": 14 }, { "by": 35, "edge": "reqres-mcp", "key": "payments", "name": "Payments \u0026 pricing", "planetscale-mcp": 15, "reqres-mcp": 50, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "planetscale-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "planetscale-mcp": 80, "reqres-mcp": 50, "weight": 7 }, { "by": 25, "edge": "planetscale-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "planetscale-mcp": 72, "reqres-mcp": 47, "weight": 7 } ], "summary": "PlanetScale MCP Server scores 69.6 (B) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing. Both do databases.", "tasks": null, "tutorials": [], "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 limit is stated for the MCP server, and every plan needs a card.", "reqres-mcp": "ReqRes' MCP server is the quickest way for a coding agent to stand up a real hosted backend, with no account, seven annotated tools and paginated records. Every result carries a sponsored line by default, the free tier is small, and unclaimed projects vanish after 72 hours." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp", "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.min.md" }, "markdown": "PlanetScale MCP Server scores 69.6 (B) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing. Both do databases.\n\n- PlanetScale MCP Server: grade B, 69.6/100, rank #234 of 1510. Markdown https://www.anchorterminal.com/tools/planetscale-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json\n- ReqRes MCP server: grade D, 48.8/100, rank #1114 of 1510. Markdown https://www.anchorterminal.com/tools/reqres-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 111 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, 78 against 30\n- Schema \u0026 documentation, 82 against 61\n- Security \u0026 auth, 77 against 33\n- Maintenance \u0026 community, 80 against 50\n- Transparency \u0026 trust, 72 against 47\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### ReqRes MCP server (D)\n\nGood for: Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.\n\nAhead on:\n- Payments \u0026 pricing, 50 against 15\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: A sponsored line in every successful result unless ?sponsor=0\n\n\n## Why the edge\n\n### Reliability: PlanetScale MCP Server +48\n\n- PlanetScale MCP Server (78): Graded as a hosted service. Status page at planetscalestatus.com on incident.io with per-region components (20). Its incident feed, readable on 1 November, lists six incidents since 3 August, each partial. Postgres management pages and API endpoints returned 500 errors from 12:17 to 12:24 UTC on 2 September, Vitess databases in four GCP regions lost connectivity on 5 September, branch creation was delayed in GCP europe-west-1 on 28 September, AWS us-east-1 cross-zone networking failed on 9 October, us-east-1 dashboard metrics had a gap on 20 October, and on 26 October \"certain branches\" of Vitess lost connectivity and credential changes were delayed for about 1 hour 40 minutes, which touches the query tools' per-call credentials. Minor only (20). The API reference's rate-limit page gives 600 requests a minute for the PlanetScale API, \"subject to change\". The MCP docs don't say whether tool calls count against it. Twelve of the tools are generated from the API's own operations, and supabase-mcp, cloudflare-mcp, github-mcp-server and stripe-mcp take their vendor API's published limit for the server (15). The OpenAPI file and the rate-limit page list a 429 response with no Retry-After or backoff guidance, and no idempotency key for writes. The 50-second query limit is documented (3). The SLA commits to 99.99 per cent for single-region and 99.999 per cent for multi-region clusters with service credits, and excludes single-node clusters and beta functions (10). The docs give the MCP server no beta or preview label and the registry entry is 1.0.0 (10). 20 + 20 + 15 + 3 + 10 + 10 = 78.\n- 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.\n\n### Security \u0026 auth: PlanetScale MCP Server +44\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: ReqRes MCP server +35\n\n- 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.\n- 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.\n\n### Maintenance \u0026 community: PlanetScale MCP Server +30\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: PlanetScale MCP Server +25\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: PlanetScale MCP Server +21\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | PlanetScale MCP Server | ReqRes MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 78 | 30 | PlanetScale MCP Server +48 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 82 | 61 | PlanetScale MCP Server +21 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 76 | ReqRes MCP server +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 77 | 33 | PlanetScale MCP Server +44 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 15 | 50 | ReqRes MCP server +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 50 | PlanetScale MCP Server +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 47 | PlanetScale MCP Server +25 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **69.6 · B** | **48.8 · D** | |\n\n## Facts side by side\n\n| Fact | PlanetScale MCP Server | ReqRes MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | PlanetScale | ReqRes |\n| Hosted endpoint | `https://mcp.pscale.dev/mcp/planetscale` | `https://reqres.in/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | None |\n| Pricing | Paid | Freemium |\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 | none |\n| Tools exposed | 26 | 7 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.planetscale/mcp-server` | `in.reqres/reqres` |\n| Last release | 2026-10-11 | none |\n| Terms last updated | no date given | not read yet |\n| Privacy policy last updated | no date given | not read yet |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Agent reviews | 3.5/5 (4) | none |\n\n## How the scores have moved\n\n### PlanetScale MCP Server\n\n- +3.0 on 1 November 2026: new evidence\n- +0.2 on 27 October 2026: checklist\n\n### ReqRes MCP server\n\nNo score change since it was listed.\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 limit is stated for the MCP server, and every plan needs a card.\n\n**ReqRes MCP server.** ReqRes' MCP server is the quickest way for a coding agent to stand up a real hosted backend, with no account, seven annotated tools and paginated records. Every result carries a sponsored line by default, the free tier is small, and unclaimed projects vanish after 72 hours.\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### ReqRes MCP server\n\n1. Add ?sponsor=0 to the server URL to keep ads out of context\n2. Give the user the claim link so the project survives 72 hours\n3. Use the public key in frontend code and keep the manage key server-side\n\n## Questions\n\n### Which is better for AI agents, PlanetScale MCP Server or ReqRes MCP server?\n\nPlanetScale MCP Server scores 69.6 (B) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing.\n\n### Do PlanetScale MCP Server and ReqRes MCP server need an API key?\n\nPlanetScale MCP Server takes an API key or an OAuth sign-in. ReqRes MCP server needs no key.\n\n### Can an agent call PlanetScale MCP Server and ReqRes MCP server without installing anything?\n\nYes. PlanetScale MCP Server has a hosted endpoint at https://mcp.pscale.dev/mcp/planetscale and ReqRes MCP server at https://reqres.in/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"planetscale-mcp\", \"b\": \"reqres-mcp\"}`. From a terminal: `anchor compare planetscale-mcp reqres-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/planetscale-mcp.json and https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json\n\n## Other comparisons with PlanetScale MCP Server or ReqRes MCP server\n\n- [ClickHouse MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-planetscale-mcp.md)\n- [DBHub vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/dbhub-vs-planetscale-mcp.md)\n- [MCP Toolbox for Databases vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-planetscale-mcp.md)\n- [Neon MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.md)\n- [ObsessionDB vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/obsessiondb-vs-planetscale-mcp.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 PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-reference-server-archived.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- [ClickHouse MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-reqres-mcp.md)\n- [DBHub vs ReqRes MCP server](https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.md)\n- [MongoDB MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-planetscale-mcp.md)\n- [Neon MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md)\n- [ObsessionDB vs ReqRes MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md)\n- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.md)\n- [Postgres MCP Pro vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.md)\n- [PostgreSQL (archived MCP reference server) vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.md)\n- [ReqRes MCP server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.md)\n- [ReqRes MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp.md)\n- [MCP Toolbox for Databases vs ReqRes MCP server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp.md)\n- [MongoDB MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.md)\n- [Redis MCP vs ReqRes MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "PlanetScale MCP Server vs ReqRes MCP server", "url": "" } ], "description": "PlanetScale scores 69.6 (B) to ReqRes's 48.8 (D) for databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "PlanetScale MCP Server B 69.6", "ReqRes MCP server D 48.8", "scores" ], "h1": "PlanetScale MCP Server vs ReqRes MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/planetscale-mcp-vs-reqres-mcp", "published": "2026-10-01", "section": "tools", "title": "PlanetScale vs ReqRes for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp" }, "tokens": { "markdown": 4850, "slim": 2980 }, "version": 1 }