{ "data": { "a": { "slug": "postgres-reference-server-archived", "name": "PostgreSQL (archived MCP reference server)", "vendor": "Model Context Protocol (archived)", "vendorUrl": "https://github.com/modelcontextprotocol/servers-archived", "kind": "mcp", "category": "data", "summary": "Archived PostgreSQL reference MCP server for SQL queries. Its read-only transaction wrapper has a documented bypass.", "url": "https://www.anchorterminal.com/tools/postgres-reference-server-archived", "markdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json", "dns": "postgres-reference-server-archived.grade.anchorterminal.com", "repo": "https://github.com/modelcontextprotocol/servers-archived", "license": "MIT", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres" } ], "auth": "none", "authNotes": "Connection string, password included, passed as a CLI argument. Queries run inside a read-only transaction that a query starting with `COMMIT;` can escape, so the database role is the only real limit.", "pricing": "free", "pricingNotes": "Open source; unmaintained.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "Archived reference server, no payments.", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": 294, "npmWeekly": 118589, "pypiWeekly": null, "asOf": "2026-10-01" }, "docsUrl": "https://github.com/modelcontextprotocol/servers-archived/tree/main/src/postgres", "capabilities": [ "db.sql" ], "tags": [ "reference", "archived", "local", "open-source", "superseded" ], "lastRelease": "2024-12-04", "graded": true, "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "anchor": { "graded": true, "score": 18.6, "grade": "F", "agentReady": false, "rank": 0, "ranked": false, "notRankedWhy": "Shut down 2025-05-29, so out of the ranking", "rankOf": 1510, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-10-01" }, "negative": -10, "negativeNotes": [ "-8: 2026-09-30, the read-only bypass Datadog Security Labs published on 21 August 2025 (SQL injection that escapes the read-only transaction and runs arbitrary SQL) is still unfixed, with no advisory, and the package drew 118,589 npm downloads in the week to 30 September 2026. We date it by that week, not by the disclosure, because the exposure is current. Every new install still gets the hole, and the fix that would let the deduction decay never came (https://securitylabs.datadoghq.com/articles/mcp-vulnerability-case-study-SQL-injection-in-the-postgresql-mcp-server/; https://api.npmjs.org/downloads/point/2026-09-24:2026-09-30/@modelcontextprotocol/server-postgres).", "-2: the tool description (\"Run a read-only SQL query\") and the main repository's README (\"Read-only database access\") still promise a guarantee the code doesn't keep, a misleading claim since the August 2025 disclosure (https://github.com/modelcontextprotocol/servers-archived/blob/main/src/postgres/index.ts; https://github.com/modelcontextprotocol/servers#archived)." ], "verdict": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.", "bestFor": "Nothing new.", "disclosure": "MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.", "strengths": [ "One tool of about 180 characters, cheap to load into context", "Table column lists exposed as MCP resources", "MIT and about 150 lines, easy to audit or fork" ], "weaknesses": [ "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed", "Archived on 29 May 2025 with no security guarantees, and pinned to MCP SDK 1.0.1", "Connection string and password passed on the command line, visible in process lists", "No row limit, pagination or tool annotations", "The npm deprecation message names no successor, so installs keep coming" ], "agentNotes": [ "Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server", "If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes", "Add `LIMIT` to every query. The server returns every row as pretty-printed JSON", "Read the `/schema` resources for column names before querying, since there's no schema tool" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 1.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 18.6 } ], "editorialScores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 80 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-10-01", "maintenance": "2026-10-01", "payments": "2026-10-01", "reliability": "2026-10-01", "schema": "2026-10-01", "security": "2026-10-01", "transparency": "2026-10-01" }, "last": "2026-10-01", "lastMoved": "2026-10-27", "oldest": "2026-10-01", "stale": false, "staleAfterDays": 90 } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/postgres-reference-server-archived" }, "supersededBy": [ "postgres-mcp-pro", "supabase-mcp" ], "sameCompany": [ "fetch-reference-server", "git-reference-server", "puppeteer-reference-server-archived", "filesystem-reference-server", "memory-reference-server", "sequential-thinking-reference-server" ], "area": "developer", "retired": "2025-05-29", "provenance": { "legalEntity": "Model Context Protocol, a Series of LF Projects, LLC", "domain": "modelcontextprotocol.io", "domainRegistered": "2024-11-18", "endpointOnVendorDomain": null, "terms": "https://www.lfprojects.org/policies/terms-of-use/", "privacy": "https://www.lfprojects.org/policies/privacy-policy/", "statusPage": "", "changelog": "https://github.com/modelcontextprotocol/servers/releases", "securityTxt": "valid", "checked": "2026-09-26", "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/postgres-reference-server-archived.json", "live": { "slug": "postgres-reference-server-archived", "versions": [ { "registry": "npm", "name": "@modelcontextprotocol/server-postgres", "version": "0.6.2", "seenAt": "2026-10-27T11:25:18.729591057Z" } ], "githubStars": 305, "npmWeekly": 92427, "securityTxt": { "url": "https://modelcontextprotocol.io/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-27T15:31:28.926342547Z" }, "domain": { "domain": "modelcontextprotocol.io", "checkedAt": "2026-10-25T14:02:39.415294808Z" }, "github": { "repo": "modelcontextprotocol/servers-archived", "checkedAt": "2026-10-26T07:47:38.025006615Z", "stars": 306, "archived": true, "issuesEnabled": true, "pushedAt": "2025-05-28T17:57:12Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0 }, "updatedAt": "2026-10-27T15:31:28.926342547Z" } }, "answer": "ReqRes MCP server scores 48.8 (D) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.6 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.", "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": 50, "category": "maintenance", "leads": "reqres-mcp", "name": "Maintenance \u0026 community", "reasons": { "a": "Last release 0.6.2 on 4 December 2024 (0). No releases in the last 90 days (0). The repository was archived on 29 May 2025 and is read-only (0). Not in the official MCP registry (0). Pinned to MCP SDK 1.0.1 and deprecated on npm (0).", "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": 0, "b": 50 } }, { "by": 38, "category": "ergonomics", "leads": "reqres-mcp", "name": "Agent ergonomics", "reasons": { "a": "One tool of about 180 characters (25). No row limit, no pagination and no output cap. Every row comes back as pretty-printed JSON (0). Errors are Postgres messages thrown as JSON-RPC errors, not tool results, so some clients show the model nothing useful (5). No annotations, so no `readOnlyHint` (0). One parameter, Node only (8). Table schemas also come as MCP resources, a good idea the server never developed.", "b": "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." }, "scores": { "a": 38, "b": 76 } }, { "by": 32, "category": "schema", "leads": "reqres-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "One tool, `query`, with an input schema typed as an object holding a string `sql`, but `sql` isn't marked required and has no description (15). The README is Markdown on GitHub. No llms.txt (5). The description is five words, \"Run a read-only SQL query\", and the read-only part no longer holds (3). No constraints, no length limit, no enum (3). The README has client configs only. Database errors are rethrown raw as protocol errors (3). No changelog or versioning beyond three 0.6.x releases (0).", "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": 29, "b": 61 } }, { "by": 30, "category": "transparency", "leads": "postgres-reference-server-archived", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT, an OSI licence (30). Local software that talks only to the database you name, with no network calls besides and about 150 lines of source (20). The GitHub banner dates the archive to 29 May 2025 and the archive README says no security updates will follow. Neither the archive, the main repository's README nor the npm deprecation message names a successor, and the main README still calls it \"Read-only database access\" (10). No telemetry (20).", "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": 77, "b": 47 } }, { "by": 28, "category": "security", "leads": "reqres-mcp", "name": "Security \u0026 auth", "reasons": { "a": "The connection string, password included, is a command-line argument and shows in process lists. Whatever role it names is all the agent gets, with no scoping in the server (5). Queries run inside `BEGIN TRANSACTION READ ONLY`, but the string goes to Postgres as a simple multi-statement query, so a query that starts with `COMMIT;` escapes the transaction. Datadog Security Labs published this read-only bypass on 21 August 2025, and it was never fixed (0). Table rows reach the model unmarked, with no injection guidance (0). No call log (0). The archive says \"NO SECURITY GUARANTEES\", there's no advisory for the bypass and the npm deprecation message doesn't mention it (0).", "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": 5, "b": 33 } }, { "by": 17, "category": "reliability", "leads": "reqres-mcp", "name": "Reliability", "reasons": { "a": "Archived and superseded, so we scored what's left. Scored as a local stdio package. @modelcontextprotocol/server-postgres 0.6.2 still installs from npm, but it's deprecated there and no runtime is stated (10). No tests. package.json has no test script, and the archive has no CI for it (0). The repository is read-only, so nobody can file or fix a crash. The code releases the connection without waiting for its ROLLBACK (0). Versions 0.6.0 to 0.6.2 shipped in December 2024 with no changelog (3). Pre-1.0 and archived (0).", "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": 13, "b": 30 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Model Context Protocol (archived)", "b": "ReqRes", "name": "Vendor" }, { "a": "no (local only)", "b": "https://reqres.in/mcp", "name": "Hosted endpoint" }, { "a": "stdio", "b": "Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "None", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "none", "name": "Licence" }, { "a": "1", "b": "7", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "in.reqres/reqres", "name": "MCP registry" }, { "a": "2024-12-04", "b": "none", "name": "Last release" }, { "a": "2021-09-08", "b": "not read yet", "name": "Terms last updated" }, { "a": "2023-03-15", "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": "294 stars, 119k npm/wk", "b": "none", "name": "Popularity" }, { "a": "1.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "ReqRes MCP server scores 48.8 (D) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.6 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, PostgreSQL (archived MCP reference server) or ReqRes MCP server?" }, { "answer": "Neither needs a key.", "question": "Do PostgreSQL (archived MCP reference server) and ReqRes MCP server need an API key?" }, { "answer": "PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. ReqRes MCP server has a hosted endpoint at https://reqres.in/mcp.", "question": "Can an agent call PostgreSQL (archived MCP reference server) and ReqRes MCP server without installing anything?" }, { "answer": "PostgreSQL (archived MCP reference server) is open source (MIT). No open-source release is listed for ReqRes MCP server.", "question": "Are PostgreSQL (archived MCP reference server) and ReqRes MCP server open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 60 against 50", "Transparency \u0026 trust, 77 against 47" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "Nothing new. It shut down on 2025-05-29.", "slug": "postgres-reference-server-archived", "watchFor": "The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed" }, { "aheadOn": [ "Reliability, 30 against 13", "Schema \u0026 documentation, 61 against 29", "Agent ergonomics, 76 against 38", "Security \u0026 auth, 33 against 5", "Maintenance \u0026 community, 50 against 0" ], "also": [ "Still running. PostgreSQL (archived MCP reference server) has shut down", "A hosted endpoint, with nothing to install", "No incidents deducted, where PostgreSQL (archived MCP reference server) loses 10 points for them" ], "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": { "postgres-reference-server-archived": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.2, "from": 18.4, "fromGrade": "F", "to": 18.6, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 18.6, "fromGrade": "F", "to": 18.4, "toGrade": "F" } ], "reqres-mcp": null }, "job": { "capability": "db.database", "name": "Databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.json", "title": "ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/dbhub-vs-postgres-reference-server-archived.json", "title": "DBHub vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/dbhub-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-postgres-reference-server-archived.json", "title": "MCP Toolbox for Databases vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-postgres-reference-server-archived" }, { "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/obsessiondb-vs-postgres-reference-server-archived.json", "title": "ObsessionDB vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived" }, { "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/postgres-mcp-pro-vs-postgres-reference-server-archived.json", "title": "Postgres MCP Pro vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.json", "title": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-supabase-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-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-postgres-reference-server-archived.json", "title": "MongoDB MCP Server vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived" }, { "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-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-redis-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-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": 17, "edge": "reqres-mcp", "key": "reliability", "name": "Reliability", "postgres-reference-server-archived": 13, "reqres-mcp": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 32, "edge": "reqres-mcp", "key": "schema", "name": "Schema \u0026 documentation", "postgres-reference-server-archived": 29, "reqres-mcp": 61, "weight": 13 }, { "by": 38, "edge": "reqres-mcp", "key": "ergonomics", "name": "Agent ergonomics", "postgres-reference-server-archived": 38, "reqres-mcp": 76, "weight": 13 }, { "by": 28, "edge": "reqres-mcp", "key": "security", "name": "Security \u0026 auth", "postgres-reference-server-archived": 5, "reqres-mcp": 33, "weight": 14 }, { "by": 10, "edge": "postgres-reference-server-archived", "key": "payments", "name": "Payments \u0026 pricing", "postgres-reference-server-archived": 60, "reqres-mcp": 50, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 50, "edge": "reqres-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "postgres-reference-server-archived": 0, "reqres-mcp": 50, "weight": 7 }, { "by": 30, "edge": "postgres-reference-server-archived", "key": "transparency", "name": "Transparency \u0026 trust", "postgres-reference-server-archived": 77, "reqres-mcp": 47, "weight": 7 } ], "summary": "PostgreSQL (archived MCP reference server) shut down on 2025-05-29. ReqRes MCP server scores 48.8 (D) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.6 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust. Both do databases.", "tasks": null, "tutorials": [], "verdicts": { "postgres-reference-server-archived": "The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.", "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/postgres-reference-server-archived-vs-reqres-mcp", "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.min.md" }, "markdown": "PostgreSQL (archived MCP reference server) shut down on 2025-05-29. ReqRes MCP server scores 48.8 (D) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.6 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust. Both do databases.\n\n- PostgreSQL (archived MCP reference server): grade F, 18.6/100, rank retired, not ranked. Markdown https://www.anchorterminal.com/tools/postgres-reference-server-archived.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.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### PostgreSQL (archived MCP reference server) (F)\n\nGood for: Nothing new. It shut down on 2025-05-29.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 50\n- Transparency \u0026 trust, 77 against 47\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed\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- Reliability, 30 against 13\n- Schema \u0026 documentation, 61 against 29\n- Agent ergonomics, 76 against 38\n- Security \u0026 auth, 33 against 5\n- Maintenance \u0026 community, 50 against 0\n\nAlso in its favour:\n- Still running. PostgreSQL (archived MCP reference server) has shut down\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where PostgreSQL (archived MCP reference server) loses 10 points for them\n\nWatch for: A sponsored line in every successful result unless ?sponsor=0\n\n\n## Why the edge\n\n### Maintenance \u0026 community: ReqRes MCP server +50\n\n- PostgreSQL (archived MCP reference server) (0): Last release 0.6.2 on 4 December 2024 (0). No releases in the last 90 days (0). The repository was archived on 29 May 2025 and is read-only (0). Not in the official MCP registry (0). Pinned to MCP SDK 1.0.1 and deprecated on npm (0).\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### Agent ergonomics: ReqRes MCP server +38\n\n- PostgreSQL (archived MCP reference server) (38): One tool of about 180 characters (25). No row limit, no pagination and no output cap. Every row comes back as pretty-printed JSON (0). Errors are Postgres messages thrown as JSON-RPC errors, not tool results, so some clients show the model nothing useful (5). No annotations, so no `readOnlyHint` (0). One parameter, Node only (8). Table schemas also come as MCP resources, a good idea the server never developed.\n- 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.\n\n### Schema \u0026 documentation: ReqRes MCP server +32\n\n- PostgreSQL (archived MCP reference server) (29): One tool, `query`, with an input schema typed as an object holding a string `sql`, but `sql` isn't marked required and has no description (15). The README is Markdown on GitHub. No llms.txt (5). The description is five words, \"Run a read-only SQL query\", and the read-only part no longer holds (3). No constraints, no length limit, no enum (3). The README has client configs only. Database errors are rethrown raw as protocol errors (3). No changelog or versioning beyond three 0.6.x releases (0).\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: PostgreSQL (archived MCP reference server) +30\n\n- PostgreSQL (archived MCP reference server) (77): MIT, an OSI licence (30). Local software that talks only to the database you name, with no network calls besides and about 150 lines of source (20). The GitHub banner dates the archive to 29 May 2025 and the archive README says no security updates will follow. Neither the archive, the main repository's README nor the npm deprecation message names a successor, and the main README still calls it \"Read-only database access\" (10). No telemetry (20).\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### Security \u0026 auth: ReqRes MCP server +28\n\n- PostgreSQL (archived MCP reference server) (5): The connection string, password included, is a command-line argument and shows in process lists. Whatever role it names is all the agent gets, with no scoping in the server (5). Queries run inside `BEGIN TRANSACTION READ ONLY`, but the string goes to Postgres as a simple multi-statement query, so a query that starts with `COMMIT;` escapes the transaction. Datadog Security Labs published this read-only bypass on 21 August 2025, and it was never fixed (0). Table rows reach the model unmarked, with no injection guidance (0). No call log (0). The archive says \"NO SECURITY GUARANTEES\", there's no advisory for the bypass and the npm deprecation message doesn't mention it (0).\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### Reliability: ReqRes MCP server +17\n\n- PostgreSQL (archived MCP reference server) (13): Archived and superseded, so we scored what's left. Scored as a local stdio package. @modelcontextprotocol/server-postgres 0.6.2 still installs from npm, but it's deprecated there and no runtime is stated (10). No tests. package.json has no test script, and the archive has no CI for it (0). The repository is read-only, so nobody can file or fix a crash. The code releases the connection without waiting for its ROLLBACK (0). Versions 0.6.0 to 0.6.2 shipped in December 2024 with no changelog (3). Pre-1.0 and archived (0).\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## Score by category\n\n| Category | Weight | PostgreSQL (archived MCP reference server) | ReqRes MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 13 | 30 | ReqRes MCP server +17 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 29 | 61 | ReqRes MCP server +32 |\n| Agent ergonomics | 13% (16.2 this run) | 38 | 76 | ReqRes MCP server +38 |\n| Security \u0026 auth | 14% (17.5 this run) | 5 | 33 | ReqRes MCP server +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 50 | PostgreSQL (archived MCP reference server) +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 0 | 50 | ReqRes MCP server +50 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 47 | PostgreSQL (archived MCP reference server) +30 |\n| Negative events | ≤15 | -10 | 0 | |\n| **Total** | | **18.6 · F** | **48.8 · D** | |\n\n## Facts side by side\n\n| Fact | PostgreSQL (archived MCP reference server) | ReqRes MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Model Context Protocol (archived) | ReqRes |\n| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |\n| Transports | stdio | Streamable HTTP |\n| Auth | None | None |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | MIT | none |\n| Tools exposed | 1 | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| MCP registry | not listed | `in.reqres/reqres` |\n| Last release | 2024-12-04 | none |\n| Terms last updated | 2021-09-08 | not read yet |\n| Privacy policy last updated | 2023-03-15 | 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 | 294 stars, 119k npm/wk | none |\n| Agent reviews | 1.5/5 (2) | none |\n\n## How the scores have moved\n\n### PostgreSQL (archived MCP reference server)\n\n- +0.2 on 27 October 2026: checklist\n- -0.2 on 8 October 2026: checklist\n\n### ReqRes MCP server\n\nNo score change since it was listed.\n\n## Verdicts\n\n**PostgreSQL (archived MCP reference server).** The server exposes one small query tool. Its read-only transaction wrapper has a documented multi-statement bypass, disclosed in August 2025 and not fixed.\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### PostgreSQL (archived MCP reference server)\n\n1. Don't use for new work. Migrate to Postgres MCP Pro with `--access-mode=restricted` or a managed provider's server\n2. If you inherit it, connect with a database role that can only SELECT. The transaction won't stop writes\n3. Add `LIMIT` to every query. The server returns every row as pretty-printed JSON\n4. Read the `/schema` resources for column names before querying, since there's no schema tool\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, PostgreSQL (archived MCP reference server) or ReqRes MCP server?\n\nReqRes MCP server scores 48.8 (D) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.6 (F), and leads in 5 of 7 scored categories. PostgreSQL (archived MCP reference server) leads on payments \u0026 pricing and transparency \u0026 trust.\n\n### Do PostgreSQL (archived MCP reference server) and ReqRes MCP server need an API key?\n\nNeither needs a key.\n\n### Can an agent call PostgreSQL (archived MCP reference server) and ReqRes MCP server without installing anything?\n\nPostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. ReqRes MCP server has a hosted endpoint at https://reqres.in/mcp.\n\n### Are PostgreSQL (archived MCP reference server) and ReqRes MCP server open source?\n\nPostgreSQL (archived MCP reference server) is open source (MIT). No open-source release is listed for ReqRes MCP server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"postgres-reference-server-archived\", \"b\": \"reqres-mcp\"}`. From a terminal: `anchor compare postgres-reference-server-archived reqres-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/postgres-reference-server-archived.json and https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json\n\n## Other comparisons with PostgreSQL (archived MCP reference server) or ReqRes MCP server\n\n- [ClickHouse MCP Server vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-reference-server-archived.md)\n- [DBHub vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/dbhub-vs-postgres-reference-server-archived.md)\n- [MCP Toolbox for Databases vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-postgres-reference-server-archived.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- [ObsessionDB vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/obsessiondb-vs-postgres-reference-server-archived.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- [Postgres MCP Pro vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.md)\n- [PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Supabase API + MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-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 PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-reference-server-archived.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 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 Redis MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-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\n## Disclosure\n\n- MCP started at Anthropic, which makes the Claude models our research agents and review panel run on (Anthropic donated it to the Agentic AI Foundation, a directed fund under the Linux Foundation, in December 2025), and this server is graded by the same checklist as every other listing.\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": "PostgreSQL (archived MCP reference server) vs ReqRes MCP server", "url": "" } ], "description": "ReqRes scores 48.8 (D) to PostgreSQL's 18.6 (F) for databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "PostgreSQL (archived MCP reference server) F 18.6", "ReqRes MCP server D 48.8", "scores" ], "h1": "PostgreSQL (archived MCP reference server) vs ReqRes MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/postgres-reference-server-archived-vs-reqres-mcp", "published": "2026-10-01", "section": "tools", "title": "PostgreSQL vs ReqRes for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp" }, "tokens": { "markdown": 4250, "slim": 2180 }, "version": 1 }