{ "data": { "a": { "slug": "neon-mcp", "name": "Neon MCP Server", "vendor": "Neon (Databricks)", "vendorUrl": "https://neon.com/docs/ai/neon-mcp-server", "kind": "mcp", "category": "data", "summary": "Neon's official remote MCP server at mcp.neon.tech/mcp lets agents manage Neon Postgres projects, branches, roles and computes, run SQL and migrations on temporary branches, and configure Neon Auth, Data API and storage, through OAuth or an API key.", "url": "https://www.anchorterminal.com/tools/neon-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/neon-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/neon-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/neon-mcp.json", "dns": "neon-mcp.grade.anchorterminal.com", "repo": "https://github.com/neondatabase/mcp-server-neon", "license": "MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.neon.tech/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.1 with dynamic client registration or Client ID Metadata Documents, advertising `read` and `write` scopes; the consent screen lets the user untick writes and pick one project, a Postgres role and tool categories, or a parameterised URL fixes that grant. A Neon API key in a Bearer header also works, with readonly, projectId, category and roleName read from the URL on each request. The `neon mcp` CLI command can mint a key for the server. The local stdio package is deprecated.", "pricing": "freemium", "pricingNotes": "The MCP server is free; Neon usage is billed. The Free plan is $0 with no card (100 projects, 100 CU-hours and 0.5 GB storage per project, 1 GB storage). Launch and Scale are pay as you go, compute $0.106 a CU-hour on Launch and $0.222 on Scale, storage $0.35 a GB-month.", "priceSummary": "$0.106 / unit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP server, docs or pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 138, "popularity": { "githubStars": 663, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://neon.com/docs/ai/neon-mcp-server", "llmsTxt": "https://neon.com/llms.txt", "openapi": "https://neon.com/docs/reference/api-reference", "registryName": "com.neon/mcp", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "hosted", "freemium", "mcp", "remote-mcp", "oauth", "mcp-registry", "llms-txt", "openapi", "postgres", "read-only-mode", "branching", "databricks" ], "lastRelease": "2026-11-05", "graded": true, "anchor": { "graded": true, "score": 72.5, "grade": "BB", "agentReady": true, "rank": 125, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 80, "payments": 40, "reliability": 72, "schema": 90, "security": 69, "transparency": 75 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.", "bestFor": "Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.", "strengths": [ "OAuth 2.1 with read and write scopes, and grants fixed to one project, one Postgres role and chosen categories", "Read-only mode runs SQL in READ ONLY transactions and withholds connection strings", "Migrations and query tuning run on a temporary branch before they touch the main one", "Descriptions say how to resolve IDs and which tools must never run without the user", "MIT source, dated CHANGELOG and com.neon/mcp in the official registry at 2.0.0" ], "weaknesses": [ "138 tools listed when no category or project is set", "The README says it isn't recommended for production databases", "Segment receives account ID, name and email on connect, with no opt-out on the hosted server", "The MCP server has no status component and no stated release stage", "No security.txt on neon.com" ], "agentNotes": [ "Connect with ?category=querying\u0026category=schema\u0026projectId=... or untick Allow writes at consent to cut 138 tools to a handful", "Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing", "Pass branch IDs (br-...), not names; call list_branches to resolve a name", "On 429 back off exponentially, and on 423 Locked wait for the running operation to finish" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.5 } ], "editorialScores": { "ergonomics": 79, "maintenance": 80, "payments": 40, "reliability": 72, "schema": 90, "security": 69, "transparency": 79 }, "provenanceScore": 71, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http neon https://mcp.neon.tech/mcp", "config": { "mcpServers": { "Neon": { "url": "https://mcp.neon.tech/mcp?readonly=true" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/neon-mcp" }, "area": "developer", "unitPrices": [ { "item": "Compute, Launch", "unit": "compute-unit", "usd": 0.106, "note": "Per CU-hour" }, { "item": "Compute, Scale", "unit": "compute-unit", "usd": 0.222, "note": "Per CU-hour" }, { "item": "Storage", "unit": "gb-month", "usd": 0.35, "note": "Launch and Scale" } ], "provenance": { "legalEntity": "Neon, LLC (subsidiary of Databricks, Inc.)", "domain": "neon.com", "domainRegistered": "1994-08-18", "endpointOnVendorDomain": false, "terms": "https://neon.com/terms-of-service", "privacy": "https://neon.com/privacy-policy", "statusPage": "https://neonstatus.com", "changelog": "https://github.com/neondatabase/mcp-server-neon/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The MCP endpoint is on mcp.neon.tech, Neon's older domain, while docs and legal pages are on neon.com.", "The Neon product schedule, last updated 14 October 2026, is between Databricks, Inc., the parent company of Neon, LLC, and the customer. The privacy notice is Databricks', last updated 9 January 2026.", "neon.com/security lists annual SOC 2 Type II audits with a public SOC 3 report, ISO 27001, ISO 27701, HIPAA, GDPR and CCPA.", "neon.com/.well-known/security.txt returns 404.", "neon.com/robots.txt allows all and carries Content-Signal ai-train=yes, search=yes, ai-input=yes. mcp.neon.tech has no robots.txt.", "RDAP gives neon.com a registration date of 18 August 1994; the domain predates Neon." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/neon-mcp.json", "live": { "slug": "neon-mcp", "probe": { "target": "https://mcp.neon.tech/mcp", "method": "mcp-initialize", "lastAt": "2026-11-07T23:26:44.089224326Z", "lastOk": true, "lastStatus": 401, "lastMs": 124, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 149, "p95ms24h": 383, "samples24h": 244, "samples30d": 251, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 238, "ok": 238 } ] }, "vendorStatus": { "page": "https://neonstatus.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:15.209607696Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.neon/mcp", "version": "2.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 663, "securityTxt": { "url": "https://neon.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:24.319288694Z" }, "llmsTxt": { "url": "https://neon.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:18.8105724Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/neondatabase/mcp-server-neon/main/CHANGELOG.md", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:22:07.888479491Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "22d617e6b187" }, { "url": "https://neon.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:14:57.338873736Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c96cd96f185b" }, { "url": "https://neon.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:14:59.695502864Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d25bd3a3dc6e" } ], "mcpTools": { "url": "https://mcp.neon.tech/mcp", "checkedAt": "2026-11-07T01:52:00.41377208Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-03T22:16:15.261722522Z" }, "updatedAt": "2026-11-07T23:26:44.089224326Z" } }, "answer": "Neon MCP Server scores 72.5 (BB) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 6 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": 42, "category": "reliability", "leads": "neon-mcp", "name": "Reliability", "reasons": { "a": "Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.", "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": 72, "b": 30 } }, { "by": 36, "category": "security", "leads": "neon-mcp", "name": "Security \u0026 auth", "reasons": { "a": "OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.", "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": 69, "b": 33 } }, { "by": 30, "category": "maintenance", "leads": "neon-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 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": 29, "category": "schema", "leads": "neon-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not (\"branch_id is a branch id, not a branch name. Call list_branches to resolve a name\", \"NEVER run autonomously\") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.", "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": 90, "b": 61 } }, { "by": 28, "category": "transparency", "leads": "neon-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.", "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": 75, "b": 47 } }, { "by": 10, "category": "payments", "leads": "reqres-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-unit prices are public, compute per CU-hour and storage per GB-month (20). Free plan with no card (20). A person signs up and authorises in a browser; the CLI can mint a key only after a login (0). 0 + 20 + 20 + 0 = 40.", "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": 40, "b": 50 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Neon (Databricks)", "b": "ReqRes", "name": "Vendor" }, { "a": "https://mcp.neon.tech/mcp", "b": "https://reqres.in/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "None", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "none", "name": "Licence" }, { "a": "138", "b": "7", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.neon/mcp", "b": "in.reqres/reqres", "name": "MCP registry" }, { "a": "2026-11-05", "b": "none", "name": "Last release" }, { "a": "2026-10-14", "b": "not read yet", "name": "Terms last updated" }, { "a": "2026-01-09", "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": "663 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Neon MCP Server scores 72.5 (BB) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 6 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Neon MCP Server or ReqRes MCP server?" }, { "answer": "Neon MCP Server uses an OAuth sign-in. ReqRes MCP server needs no key.", "question": "Do Neon MCP Server and ReqRes MCP server need an API key?" }, { "answer": "Yes. Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp and ReqRes MCP server at https://reqres.in/mcp.", "question": "Can an agent call Neon MCP Server and ReqRes MCP server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 30", "Schema \u0026 documentation, 90 against 61", "Security \u0026 auth, 69 against 33", "Maintenance \u0026 community, 80 against 50", "Transparency \u0026 trust, 75 against 47" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.", "slug": "neon-mcp", "watchFor": "138 tools listed when no category or project is set" }, { "aheadOn": [ "Payments \u0026 pricing, 50 against 40" ], "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": null, "job": { "capability": "db.database", "name": "Databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.json", "title": "ClickHouse MCP Server vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.json", "title": "DBHub vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.json", "title": "MCP Toolbox for Databases vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.json", "title": "Neon MCP Server vs ObsessionDB", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb" }, { "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/neon-mcp-vs-postgres-mcp-pro.json", "title": "Neon MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.json", "title": "Neon MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.json", "title": "Neon MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.json", "title": "Neon MCP Server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/neon-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-neon-mcp.json", "title": "MongoDB MCP Server vs Neon MCP Server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp" }, { "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.json", "title": "Neon MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-redis-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-reqres-mcp.json", "title": "PlanetScale MCP Server vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-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": 42, "edge": "neon-mcp", "key": "reliability", "name": "Reliability", "neon-mcp": 72, "reqres-mcp": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 29, "edge": "neon-mcp", "key": "schema", "name": "Schema \u0026 documentation", "neon-mcp": 90, "reqres-mcp": 61, "weight": 13 }, { "by": 3, "edge": "neon-mcp", "key": "ergonomics", "name": "Agent ergonomics", "neon-mcp": 79, "reqres-mcp": 76, "weight": 13 }, { "by": 36, "edge": "neon-mcp", "key": "security", "name": "Security \u0026 auth", "neon-mcp": 69, "reqres-mcp": 33, "weight": 14 }, { "by": 10, "edge": "reqres-mcp", "key": "payments", "name": "Payments \u0026 pricing", "neon-mcp": 40, "reqres-mcp": 50, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 30, "edge": "neon-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "neon-mcp": 80, "reqres-mcp": 50, "weight": 7 }, { "by": 28, "edge": "neon-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "neon-mcp": 75, "reqres-mcp": 47, "weight": 7 } ], "summary": "Neon MCP Server scores 72.5 (BB) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 6 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing. Both do databases.", "tasks": null, "tutorials": [], "verdicts": { "neon-mcp": "OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.", "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/neon-mcp-vs-reqres-mcp", "json": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.min.md" }, "markdown": "Neon MCP Server scores 72.5 (BB) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 6 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing. Both do databases.\n\n- Neon MCP Server: grade BB, 72.5/100, rank #125 of 1510. Markdown https://www.anchorterminal.com/tools/neon-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/neon-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### Neon MCP Server (BB)\n\nGood for: Agents building on Neon Postgres in development, especially branch-per-change workflows. supabase-mcp and planetscale-mcp are the nearest listings; Neon itself advises against pointing it at production.\n\nAhead on:\n- Reliability, 72 against 30\n- Schema \u0026 documentation, 90 against 61\n- Security \u0026 auth, 69 against 33\n- Maintenance \u0026 community, 80 against 50\n- Transparency \u0026 trust, 75 against 47\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: 138 tools listed when no category or project is set\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 40\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: Neon MCP Server +42\n\n- Neon MCP Server (72): Hosted reading. neonstatus.com on status.io with components per region, though no MCP component (20). The page shows only the last 30 days, three incidents, a partial disruption of monitoring data on 21 October (1 hour 22 minutes), slow compute starts in us-east-2 on 2 November (2 hours 14 minutes) and 26 minutes of console and API errors on 2 November; August and September weren't readable (15). The Neon API publishes 700 requests a minute with a 40-a-second burst per route (15). 429 with exponential backoff advice and 423 Locked for overlapping operations with retry guidance, but no idempotency keys (12). An uptime SLA on Scale only, with no percentage on the pricing page (5). The docs give the server no status label and the README says it isn't recommended for production (5). 20 + 15 + 15 + 12 + 5 + 5 = 72.\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: Neon MCP Server +36\n\n- Neon MCP Server (69): OAuth 2.1 with read and write scopes, per-project and per-role fixed grants, Client ID Metadata Documents and RFC 9207 iss on redirects, or API keys (28). Read-only mode keeps SQL in READ ONLY transactions and withholds connection strings, roleName limits SQL to a role's grants, and destructive tools ask the model to confirm with the user; with an API key anyone who can edit the URL can widen the grant (17). The README warns to review every action and keep the server away from production, but we found no prompt-injection guidance for query results (5). Neon has project audit logs, but we didn't read whether MCP calls appear (5). SOC 2 Type II with a public SOC 3, ISO 27001 and 27701, HIPAA; no security.txt on neon.com (14). 28 + 17 + 5 + 5 + 14 = 69.\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### Maintenance \u0026 community: Neon MCP Server +30\n\n- Neon MCP Server (80): v2.0.0 on 5 November 2026, one day before this check (30). 1.0.0 (registry, 17 September) and 2.0.0 in the 90 days, two releases (10). 53 open issues and pull requests, with commits most days; reply times weren't measured (15). com.neon/mcp in the official registry, a domain-verified namespace, at 2.0.0 (15). Unit, integration and end-to-end test suites, knip and lint in CI (10). 30 + 10 + 15 + 15 + 10 = 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### Schema \u0026 documentation: Neon MCP Server +29\n\n- Neon MCP Server (90): Every tool has a JSON Schema, many generated from the Neon OpenAPI spec (25). neon.com serves llms.txt and Markdown pages (10). Descriptions say when and when not (\"branch_id is a branch id, not a branch name. Call list_branches to resolve a name\", \"NEVER run autonomously\") (18). Typed inputs with enums such as access read_only or read_write, and path arguments checked for . and .. since 2.0.0 (13). Examples in the README and docs, and API 4xx errors classified by kind (11). CHANGELOG with dated releases and a registry version (13). 25 + 10 + 18 + 13 + 11 + 13 = 90.\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### Transparency \u0026 trust: Neon MCP Server +28\n\n- Neon MCP Server (75): MIT (30). Databricks' privacy notice (9 January 2026), the Neon product schedule (14 October 2026) with a DPA and a sub-contractor list linked from every page (24). The SSE retirement returns 410 with a pointer, and the stdio package is marked deprecated, but no notice period is stated (15). Telemetry is disclosed in the README, Segment identify with account ID, name and email plus every tool call, but hosted users have no opt-out (10). 30 + 24 + 15 + 10 = 79.\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### Payments \u0026 pricing: ReqRes MCP server +10\n\n- Neon MCP Server (40): No x402, MPP or L402 (0). Per-unit prices are public, compute per CU-hour and storage per GB-month (20). Free plan with no card (20). A person signs up and authorises in a browser; the CLI can mint a key only after a login (0). 0 + 20 + 20 + 0 = 40.\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## Score by category\n\n| Category | Weight | Neon MCP Server | ReqRes MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 30 | Neon MCP Server +42 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 90 | 61 | Neon MCP Server +29 |\n| Agent ergonomics | 13% (16.2 this run) | 79 | 76 | Neon MCP Server +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 33 | Neon MCP Server +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 50 | ReqRes MCP server +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 50 | Neon MCP Server +30 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 47 | Neon MCP Server +28 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.5 · BB** | **48.8 · D** | |\n\n## Facts side by side\n\n| Fact | Neon MCP Server | ReqRes MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Neon (Databricks) | ReqRes |\n| Hosted endpoint | `https://mcp.neon.tech/mcp` | `https://reqres.in/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth | None |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | MIT | none |\n| Tools exposed | 138 | 7 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.neon/mcp` | `in.reqres/reqres` |\n| Last release | 2026-11-05 | none |\n| Terms last updated | 2026-10-14 | not read yet |\n| Privacy policy last updated | 2026-01-09 | 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| Popularity | 663 stars | none |\n\n## Verdicts\n\n**Neon MCP Server.** OAuth with read or write scopes, per-project and per-role grants, read-only SQL in READ ONLY transactions, and migrations tried on temporary branches. With no grant it lists 138 tools, the README advises against production use, and it sends account name and email to Segment with no opt-out for hosted users.\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### Neon MCP Server\n\n1. Connect with ?category=querying\u0026category=schema\u0026projectId=... or untick Allow writes at consent to cut 138 tools to a handful\n2. Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing\n3. Pass branch IDs (br-...), not names; call list_branches to resolve a name\n4. On 429 back off exponentially, and on 423 Locked wait for the running operation to finish\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, Neon MCP Server or ReqRes MCP server?\n\nNeon MCP Server scores 72.5 (BB) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 6 of 7 scored categories. ReqRes MCP server leads on payments \u0026 pricing.\n\n### Do Neon MCP Server and ReqRes MCP server need an API key?\n\nNeon MCP Server uses an OAuth sign-in. ReqRes MCP server needs no key.\n\n### Can an agent call Neon MCP Server and ReqRes MCP server without installing anything?\n\nYes. Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp 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/neon-mcp-vs-reqres-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"neon-mcp\", \"b\": \"reqres-mcp\"}`. From a terminal: `anchor compare neon-mcp reqres-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/neon-mcp.json and https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json\n\n## Other comparisons with Neon MCP Server or ReqRes MCP server\n\n- [ClickHouse MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.md)\n- [DBHub vs Neon MCP Server](https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.md)\n- [MCP Toolbox for Databases vs Neon MCP Server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.md)\n- [Neon MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.md)\n- [Neon MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.md)\n- [Neon MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.md)\n- [Neon MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.md)\n- [Neon MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md)\n- [Neon MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/neon-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 Neon MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp.md)\n- [Neon MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.md)\n- [ObsessionDB vs ReqRes MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md)\n- [PlanetScale MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-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": "Neon MCP Server vs ReqRes MCP server", "url": "" } ], "description": "Neon scores 72.5 (BB) to ReqRes's 48.8 (D) for databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Neon MCP Server BB 72.5", "ReqRes MCP server D 48.8", "scores" ], "h1": "Neon MCP Server vs ReqRes MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/neon-mcp-vs-reqres-mcp", "published": "2026-10-01", "section": "tools", "title": "Neon vs ReqRes for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp" }, "tokens": { "markdown": 3800, "slim": 2130 }, "version": 1 }