# Neon MCP Server vs ReqRes MCP server

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

- Canonical: https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp
- Markdown: https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md (~3,800 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

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 & pricing. Both do databases.

- 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
- 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
- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md
- All 111 databases comparisons: https://www.anchorterminal.com/compare/data/index.md

## Which one, for what

### Neon MCP Server (BB)

Good 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.

Ahead on:
- Reliability, 72 against 30
- Schema & documentation, 90 against 61
- Security & auth, 69 against 33
- Maintenance & community, 80 against 50
- Transparency & trust, 75 against 47

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: 138 tools listed when no category or project is set

### ReqRes MCP server (D)

Good for: Coding agents that need a throwaway or starter backend for a prototype, with no account to set up.

Ahead on:
- Payments & pricing, 50 against 40

Also in its favour:
- No key needed to call it

Watch for: A sponsored line in every successful result unless ?sponsor=0


## Why the edge

### Reliability: Neon MCP Server +42

- 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.
- 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.

### Security & auth: Neon MCP Server +36

- 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.
- 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.

### Maintenance & community: Neon MCP Server +30

- 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.
- 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.

### Schema & documentation: Neon MCP Server +29

- 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.
- 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.

### Transparency & trust: Neon MCP Server +28

- 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.
- 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.

### Payments & pricing: ReqRes MCP server +10

- 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.
- 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.

## Score by category

| Category | Weight | Neon MCP Server | ReqRes MCP server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 72 | 30 | Neon MCP Server +42 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 90 | 61 | Neon MCP Server +29 |
| Agent ergonomics | 13% (16.2 this run) | 79 | 76 | Neon MCP Server +3 |
| Security & auth | 14% (17.5 this run) | 69 | 33 | Neon MCP Server +36 |
| Payments & pricing | 10% (12.5 this run) | 40 | 50 | ReqRes MCP server +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 80 | 50 | Neon MCP Server +30 |
| Transparency & trust | 7% (8.8 this run) | 75 | 47 | Neon MCP Server +28 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **72.5 · BB** | **48.8 · D** | |

## Facts side by side

| Fact | Neon MCP Server | ReqRes MCP server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Neon (Databricks) | ReqRes |
| Hosted endpoint | `https://mcp.neon.tech/mcp` | `https://reqres.in/mcp` |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth | None |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 138 | 7 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `com.neon/mcp` | `in.reqres/reqres` |
| Last release | 2026-11-05 | none |
| Terms last updated | 2026-10-14 | not read yet |
| Privacy policy last updated | 2026-01-09 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 663 stars | none |

## Verdicts

**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.

**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.

## Before you call either

### Neon MCP Server

1. Connect with ?category=querying&category=schema&projectId=... or untick Allow writes at consent to cut 138 tools to a handful
2. Use prepare_database_migration and complete_database_migration for schema changes, and ask the user before completing
3. Pass branch IDs (br-...), not names; call list_branches to resolve a name
4. On 429 back off exponentially, and on 423 Locked wait for the running operation to finish

### ReqRes MCP server

1. Add ?sponsor=0 to the server URL to keep ads out of context
2. Give the user the claim link so the project survives 72 hours
3. Use the public key in frontend code and keep the manage key server-side

## Questions

### Which is better for AI agents, Neon MCP Server or ReqRes MCP server?

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 & pricing.

### Do Neon MCP Server and ReqRes MCP server need an API key?

Neon MCP Server uses an OAuth sign-in. ReqRes MCP server needs no key.

### Can an agent call Neon MCP Server and ReqRes MCP server without installing anything?

Yes. Neon MCP Server has a hosted endpoint at https://mcp.neon.tech/mcp and ReqRes MCP server at https://reqres.in/mcp.


## For agents

- 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
- 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`
- 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

## Other comparisons with Neon MCP Server or ReqRes MCP server

- [ClickHouse MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-neon-mcp.md)
- [DBHub vs Neon MCP Server](https://www.anchorterminal.com/compare/dbhub-vs-neon-mcp.md)
- [MCP Toolbox for Databases vs Neon MCP Server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-neon-mcp.md)
- [Neon MCP Server vs ObsessionDB](https://www.anchorterminal.com/compare/neon-mcp-vs-obsessiondb.md)
- [Neon MCP Server vs PlanetScale MCP Server](https://www.anchorterminal.com/compare/neon-mcp-vs-planetscale-mcp.md)
- [Neon MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-mcp-pro.md)
- [Neon MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/neon-mcp-vs-postgres-reference-server-archived.md)
- [Neon MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-snowflake-managed.md)
- [Neon MCP Server vs Supabase API + MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-supabase-mcp.md)
- [ClickHouse MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-reqres-mcp.md)
- [DBHub vs ReqRes MCP server](https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.md)
- [MongoDB MCP Server vs Neon MCP Server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-neon-mcp.md)
- [Neon MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.md)
- [ObsessionDB vs ReqRes MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md)
- [PlanetScale MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-reqres-mcp.md)
- [Postgres MCP Pro vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.md)
- [PostgreSQL (archived MCP reference server) vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.md)
- [ReqRes MCP server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/reqres-mcp-vs-snowflake-managed.md)
- [ReqRes MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/reqres-mcp-vs-supabase-mcp.md)
- [MCP Toolbox for Databases vs ReqRes MCP server](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-reqres-mcp.md)
- [MongoDB MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.md)
- [Redis MCP vs ReqRes MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp