# Postgres MCP Pro vs ReqRes MCP server (slim)

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

- Full: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.md (~3,950 tokens) · this version ~2,180 tokens · JSON https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp.json · canonical https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-reqres-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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: F 37, rank #1379 of 1510 · https://www.anchorterminal.com/tools/postgres-mcp-pro.min.md
- ReqRes MCP server: D 48.8, rank #1114 of 1510 · https://www.anchorterminal.com/tools/reqres-mcp.min.md
- Postgres MCP Pro, 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 Runs on your own machine; Open source.
- ReqRes MCP server, 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 A hosted endpoint, with nothing to install; No incidents deducted, where Postgres MCP Pro loses 8 points for them.

| Category | Postgres MCP Pro | ReqRes MCP server |
| --- | --- | --- |
| Reliability (16%) | 41 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 56 | 61 |
| Agent ergonomics (13%) | 57 | 76 |
| Security & auth (14%) | 26 | 33 |
| Payments & pricing (10%) | 60 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 8 | 50 |
| Transparency & trust (7%) | 65 | 47 |

| Fact (where they differ) | Postgres MCP Pro | ReqRes MCP server |
| --- | --- | --- |
| Vendor | Crystal DBA | ReqRes |
| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |
| Transports | stdio, SSE (legacy) | Streamable HTTP |
| Pricing | Free | Freemium |
| 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 |

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