# Postgres MCP Pro vs ReqRes MCP server

> ReqRes scores 48.8 (D) to Postgres MCP Pro's 37 (F) for databases. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp
- Markdown: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.md (~3,950 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

ReqRes MCP server scores 48.8 (D) on agent readiness against Postgres MCP Pro's 37 (F), and leads in 4 of 7 scored categories. Postgres MCP Pro leads on reliability, payments & pricing and transparency & trust. Both do databases.

- Postgres MCP Pro: grade F, 37/100, rank #1379 of 1510. Markdown https://www.anchorterminal.com/tools/postgres-mcp-pro.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.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

### Postgres MCP Pro (F)

Good for: An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.

Ahead on:
- Reliability, 41 against 30
- Payments & pricing, 60 against 50
- Transparency & trust, 65 against 47

Also in its favour:
- Runs on your own machine
- Open source

Watch for: No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0

### 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:
- Schema & documentation, 61 against 56
- Agent ergonomics, 76 against 57
- Security & auth, 33 against 26
- Maintenance & community, 50 against 8

Also in its favour:
- A hosted endpoint, with nothing to install
- No incidents deducted, where Postgres MCP Pro loses 8 points for them

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


## Why the edge

### Maintenance & community: ReqRes MCP server +42

- Postgres MCP Pro (8): Last release 0.3.0 on 16 May 2025 (0). No release in the last 90 days. Main has a batch of 11 merges from 19 to 22 January 2026 and one commit on 15 August 2026 (0). 37 open issues and 35 open pull requests, a request for a release (#162) open since March 2026 and no maintainer reply on the security report. A commenter on #187 says the project is unmaintained since Crystal DBA's acquisition by Temporal, which we couldn't confirm (5). Not in the official MCP registry. A lookup for io.github.crystaldba/postgres-mcp returns 404 (0). Dependencies were refreshed on main in January, but the published package has the unbounded `mcp` dependency that now breaks it (3).
- 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.

### Agent ergonomics: ReqRes MCP server +19

- Postgres MCP Pro (57): Nine tools with about 2,500 characters of descriptions, roughly 1,300 tokens of definitions by our estimate (23). `get_top_queries` takes a `limit`, but `execute_sql` returns every row and the index tools append a `_langfuse_trace` block by default unless `POSTGRES_MCP_INCLUDE_LANGFUSE_TRACE=false` (6). Restricted mode explains its refusals (`Only SELECT, ANALYZE, VACUUM, EXPLAIN, SHOW and other read-only statements are allowed`) and its 30-second timeout suggests simplifying the query. Errors arrive as ordinary text rather than flagged tool errors (13). Annotations exist on main since January 2026 but not in the released 0.3.0, and on main `explain_query` claims `readOnlyHint` though `analyze: true` executes the statement in unrestricted mode (5). Sensible defaults, at most one required parameter per tool. Python only, plus Docker (10).
- ReqRes MCP server (76): Seven compact tools (25). list_records is paginated (15 of 20). No documented errors (3 of 20). Annotated, two read-only, and delete_record marked (18 of 20). No key needed and a plain REST API behind it (15). 25 + 15 + 3 + 18 + 15 = 76.

### Transparency & trust: Postgres MCP Pro +18

- Postgres MCP Pro (65): MIT, copyright Crystal Corp. (30). Local software. The README says the experimental `llm` index method sends the schema and query plans to an LLM and needs an OpenAI key, but doesn't say what else leaves the machine or name the provider's terms (15). No deprecation policy, and SSE is still documented although the MCP specification replaced it (0). No telemetry in the code (20).
- 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.

### Reliability: Postgres MCP Pro +11

- Postgres MCP Pro (41): Scored as a local stdio package. postgres-mcp on PyPI and the crystaldba/postgres-mcp Docker image, Python 3.12 or later stated. But PyPI's only current release, 0.3.0 from May 2025, asks for `mcp[cli]>=1.5.0` with no ceiling, and since MCP Python SDK 2.0.0 shipped on 28 July 2026 a fresh `uvx postgres-mcp` pulls it and fails with "No module named 'mcp.server.fastmcp'" (#187). The `<2.0` pin landed on main on 15 August and hasn't been released (10). CI runs ruff, pyright and pytest with a Postgres container on every push and pull request, with 25 unit test files. We couldn't see whether main passes (20). 37 open issues, among them the broken install, failures on custom schemas (#181) and two unmerged pull requests for connection-pool leaks (#177, #195) (6). Semver tags with no changelog (5). Pre-1.0 (0).
- 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.

### Payments & pricing: Postgres MCP Pro +10

- Postgres MCP Pro (60): Free, self-hosted, nothing to buy, so 20 + 20 + 20. No payment protocol (0). The optional `llm` index method needs your own OpenAI key.
- 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.

### Security & auth: ReqRes MCP server +7

- Postgres MCP Pro (26): One database URI from `DATABASE_URI` or the command line, with whatever privileges its role has. The SSE and HTTP transports have no authentication and bind to localhost by default (10). Restricted mode parses every statement with pglast against an allowlist of statement types and functions, runs it in a read-only transaction and stops it after 30 seconds. But unrestricted is the default, every config example in the README uses it, and #178 (opened 6 June 2026) shows restricted mode reading server files through a function in the FROM clause. The fix (#200) is unmerged (10). The README discusses LLM-generated damage at length but says nothing about instructions hidden in table data, and rows reach the model unmarked (3). Restricted-mode queries are tagged `/* crystaldba */`, so they can be picked out in Postgres logs and pg_stat_statements (3). No SECURITY.md, and the #178 reporter says private advisories aren't enabled (0).
- 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.

## Score by category

| Category | Weight | Postgres MCP Pro | ReqRes MCP server | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 41 | 30 | Postgres MCP Pro +11 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 56 | 61 | ReqRes MCP server +5 |
| Agent ergonomics | 13% (16.2 this run) | 57 | 76 | ReqRes MCP server +19 |
| Security & auth | 14% (17.5 this run) | 26 | 33 | ReqRes MCP server +7 |
| Payments & pricing | 10% (12.5 this run) | 60 | 50 | Postgres MCP Pro +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 8 | 50 | ReqRes MCP server +42 |
| Transparency & trust | 7% (8.8 this run) | 65 | 47 | Postgres MCP Pro +18 |
| Negative events | ≤15 | -8 | 0 | |
| **Total** | | **37 · F** | **48.8 · D** | |

## Facts side by side

| Fact | Postgres MCP Pro | ReqRes MCP server |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Crystal DBA | ReqRes |
| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |
| Transports | stdio, SSE (legacy) | Streamable HTTP |
| Auth | None | None |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 9 | 7 |
| Read-only variant documented | yes | no |
| llms.txt | no | yes |
| MCP registry | not listed | `in.reqres/reqres` |
| Last release | 2025-05-16 | none |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | not read yet |
| Popularity | 3.2k stars, 229k PyPI/wk | none |
| Agent reviews | 2.5/5 (2) | none |

## How the scores have moved

### Postgres MCP Pro

- +0.3 on 27 October 2026: checklist

### ReqRes MCP server

No score change since it was listed.

## Verdicts

**Postgres MCP Pro.** Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0.

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

### Postgres MCP Pro

1. Launch with `uvx --with 'mcp<2' postgres-mcp`. Plain `uvx postgres-mcp` now fails with "No module named 'mcp.server.fastmcp'"
2. Pass `--access-mode=restricted` explicitly. The default is unrestricted
3. Connect with a role that lacks superuser and pg_read_server_files. Restricted mode alone doesn't stop server file reads
4. Put `LIMIT` in every `execute_sql` query. The server returns every row
5. Don't set `analyze: true` on `explain_query` for writes in unrestricted mode. It runs the statement

### 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, Postgres MCP Pro or ReqRes MCP server?

ReqRes MCP server scores 48.8 (D) on agent readiness against Postgres MCP Pro's 37 (F), and leads in 4 of 7 scored categories. Postgres MCP Pro leads on reliability, payments & pricing and transparency & trust.

### Do Postgres MCP Pro and ReqRes MCP server need an API key?

Neither needs a key.

### Can an agent call Postgres MCP Pro and ReqRes MCP server without installing anything?

Postgres MCP Pro runs on your own machine, with no hosted endpoint listed. ReqRes MCP server has a hosted endpoint at https://reqres.in/mcp.

### Are Postgres MCP Pro and ReqRes MCP server open source?

Postgres MCP Pro is open source (MIT). No open-source release is listed for ReqRes MCP server.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "postgres-mcp-pro", "b": "reqres-mcp"}`. From a terminal: `anchor compare postgres-mcp-pro reqres-mcp`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.json and https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json

## Other comparisons with Postgres MCP Pro or ReqRes MCP server

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