{ "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", "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.4, "grade": "F", "agentReady": false, "rank": 946, "ranked": true, "rankOf": 950, "categoryRank": 12, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 75 }, "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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 18.4 } ], "editorialScores": { "ergonomics": 38, "maintenance": 0, "payments": 60, "reliability": 13, "schema": 29, "security": 5, "transparency": 80 }, "provenanceScore": 69 }, "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", "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": 69 }, "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-09T17:14:01.149810402Z" } ], "githubStars": 304, "npmWeekly": 97848, "securityTxt": { "url": "https://modelcontextprotocol.io/.well-known/security.txt", "state": "valid", "checkedAt": "2026-10-09T15:40:28.044352527Z" }, "domain": { "domain": "modelcontextprotocol.io", "checkedAt": "2026-10-04T13:06:56.741922917Z" }, "updatedAt": "2026-10-09T17:14:02.082312354Z" } }, "answer": "Redis MCP scores 55.7 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories.", "b": { "slug": "redis-mcp", "name": "Redis MCP", "vendor": "Redis", "vendorUrl": "https://redis.io", "kind": "mcp", "category": "data", "summary": "Redis's open-source MCP server for Redis databases. The owner runs it locally over stdio, and it gives agents tools for strings, hashes, lists, sets, sorted sets, streams, pub/sub, JSON documents and vector search.", "url": "https://www.anchorterminal.com/tools/redis-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/redis-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/redis-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/redis-mcp.json", "repo": "https://github.com/redis/mcp-redis", "license": "MIT", "transports": [ "stdio" ], "packages": [ { "registry": "pypi", "name": "redis-mcp-server" }, { "registry": "oci", "name": "docker.io/mcp/redis" } ], "auth": "mixed", "authNotes": "The server signs in to Redis with a username and password (`--url`, `--username` and `--password`, or `REDIS_USERNAME` and `REDIS_PWD`), which a Redis admin creates, self-serve, and can scope with Redis ACL rules. TLS takes a CA file and an optional client certificate, with `ssl_cert_reqs` defaulting to required. Azure Managed Redis can use Entra ID through a service principal, a managed identity or the default Azure credential, with tokens renewed in the background. stdio needs no caller credential, and every caller shares the one Redis user.", "pricing": "free", "pricingNotes": "Free and open source under the MIT licence, with nothing to buy for the server. It needs a Redis database, which can be Redis Open Source on the owner's machine or a managed service such as Redis Cloud or Azure Managed Redis. Redis Cloud prices and its free database were not checked. Redis has no hosted version of this server in the pages read (checked 2026-10-09).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs pages or the source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 53, "popularity": { "githubStars": 633, "npmWeekly": null, "pypiWeekly": 3644, "asOf": "2026-10-09" }, "docsUrl": "https://redis.io/docs/latest/integrate/redis-mcp/", "llmsTxt": "https://redis.io/llms.txt", "registryName": "io.github.redis/mcp-redis", "capabilities": [ "db.document", "db.vector", "db.hybrid" ], "tags": [ "official", "local", "open-source", "self-hosted", "mcp", "python", "docker", "database", "key-value", "vector-search" ], "lastRelease": "2026-08-04", "graded": true, "anchor": { "graded": true, "score": 55.7, "grade": "C", "agentReady": false, "rank": 652, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 39, "maintenance": 57, "payments": 60, "reliability": 62, "schema": 64, "security": 54, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "-2: release 0.5.1, tagged 4 August 2026 as a patch release, changed the `unsubscribe` tool's input from `channel` to `subscription_id` and the return type of `subscribe` (pull request #133). The release notes give only the pull request title, 'Add stateful Redis pub/sub subscriptions with message polling'. The earlier tools opened a new pub/sub object on each call and so could not deliver messages, which is why the deduction is reduced (https://github.com/redis/mcp-redis/releases/tag/0.5.1)." ], "verdict": "Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026.", "bestFor": "Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.", "strengths": [ "Maintained by Redis under the MIT licence, with 0.5.1 marked latest in the official MCP registry as `io.github.redis/mcp-redis`", "Nightly CI passed on main on 9 October 2026 across Python 3.10 to 3.14 against a live Redis, with 347 test functions and an 80 per cent coverage floor", "No tool runs an arbitrary Redis command. Each of the 53 tools maps to a named operation, and none exposes `FLUSHALL`, `CONFIG` or `EVAL`", "Connects with a Redis ACL user, TLS with certificate checks required by default, client certificates, or Entra ID for Azure Managed Redis", "Blocking reads are capped in the server. `xreadgroup` and `read_messages` refuse waits over 5,000 ms, and pub/sub subscriptions are capped at 50" ], "weaknesses": [ "53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026", "No tool declares `readOnlyHint` or `destructiveHint`, and nothing asks for confirmation before `delete`, `json_del` or `xgroup_destroy`. Pull request #181 was opened on 8 October 2026", "Fresh PyPI installs failed to start from 28 July to 5 August 2026, because 0.5.0 had no upper bound on the `mcp` package (issues #163 and #169)", "Started through the `redis-mcp-server` command without flags, the server ignores `REDIS_HOST` and `REDIS_PORT` and connects to 127.0.0.1:6379. Issue #156 has been open since 10 July 2026", "No changelog file, no SECURITY.md and no prompt-injection guidance. Patch release 0.5.1 changed the `unsubscribe` input from `channel` to `subscription_id` without a note" ], "agentNotes": [ "Pass the connection with `--url` or explicit flags. The `redis-mcp-server` command overrides `REDIS_HOST`, `REDIS_PORT`, `REDIS_DB`, `REDIS_SSL` and `REDIS_CLUSTER_MODE` with its own defaults when flags are absent", "Use `scan_keys` with the returned cursor until it is 0. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything they match with no limit", "Read failures from the text. Tools return strings such as `Error ...` or an `error` key in place of an MCP error result", "Keep the `subscription_id` from `subscribe` or `psubscribe` and pass it to `read_messages` and `unsubscribe`. Idle subscriptions close after 300 seconds", "Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and `delete` runs without confirmation" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.7 } ], "editorialScores": { "ergonomics": 39, "maintenance": 57, "payments": 60, "reliability": 62, "schema": 64, "security": 54, "transparency": 65 }, "provenanceScore": 87 }, "connect": { "install": "pip install redis-mcp-server", "config": { "mcpServers": { "RedisMCPServer": { "args": [ "--from", "redis-mcp-server@latest", "redis-mcp-server", "--url", "redis://localhost:6379/0" ], "command": "uvx" } } } }, "letme": { "capability": "https://letme.dev/db.document", "tool": "https://letme.dev/redis-mcp" }, "area": "developer", "provenance": { "legalEntity": "Redis Ltd.", "domain": "redis.io", "domainRegistered": "2010-05-28", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/redis/mcp-redis/releases", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "No terms document governs this software beyond the MIT licence, so `terms` is left out.", "`privacy` is left out. The Redis Privacy Policy (last updated 29 November 2024, https://redis.io/legal/privacy-policy/) names Redis Ltd. and its affiliates and covers Redis's sites and services. It does not address this open-source server, which runs on the owner's machine. Questions sent by `search_redis_documents` do go to redis.io.", "The copyright line in the `LICENSE` file reads Redis, inc. The privacy policy names Redis Ltd., which is used here.", "redis.io/.well-known/security.txt gives a contact page, a HackerOne disclosure programme as policy and an expiry of 19 December 2030.", "RDAP for redis.io gives a registration date of 2010-05-28.", "The server runs on the owner's machine and connects to the Redis it is configured for, so there is no vendor endpoint to check. The changelog link is the GitHub releases page, since the repository has no changelog file." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/redis-mcp.json", "live": { "slug": "redis-mcp", "versions": [ { "registry": "github", "name": "redis/mcp-redis", "version": "0.5.1", "released": "2026-08-05", "seenAt": "2026-10-09T17:16:10.784079074Z" }, { "registry": "mcp-registry", "name": "io.github.redis/mcp-redis", "version": "0.5.1", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "registry": "pypi", "name": "redis-mcp-server", "version": "0.5.1", "released": "2026-08-05", "seenAt": "2026-10-09T17:16:10.590203387Z" } ], "githubStars": 633, "pypiWeekly": 3644, "updatedAt": "2026-10-10T03:11:32.438759038Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Model Context Protocol (archived)", "b": "Redis", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "stdio", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "MIT", "name": "Licence" }, { "a": "1", "b": "53", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.redis/mcp-redis", "name": "MCP registry" }, { "a": "2024-12-04", "b": "2026-08-04", "name": "Last release" }, { "a": "2021-09-08", "b": "no document linked", "name": "Terms last updated" }, { "a": "2023-03-15", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "294 stars, 119k npm/wk", "b": "633 stars, 3.6k PyPI/wk", "name": "Popularity" }, { "a": "1.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Redis MCP scores 55.7 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories.", "question": "Which is better for AI agents, PostgreSQL (archived MCP reference server) or Redis MCP?" }, { "answer": "PostgreSQL (archived MCP reference server) needs no key. Redis MCP takes an API key or an OAuth sign-in.", "question": "Do PostgreSQL (archived MCP reference server) and Redis MCP need an API key?" }, { "answer": "PostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. Redis MCP runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call PostgreSQL (archived MCP reference server) and Redis MCP without installing anything?" }, { "answer": "Yes. PostgreSQL (archived MCP reference server) is open source (MIT). Redis MCP is open source (MIT).", "question": "Are PostgreSQL (archived MCP reference server) and Redis MCP open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No key needed to call it" ], "goodFor": "Nothing new.", "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, 62 against 13", "Schema \u0026 documentation, 64 against 29", "Security \u0026 auth, 54 against 5", "Maintenance \u0026 community, 57 against 0" ], "also": null, "goodFor": "Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.", "slug": "redis-mcp", "watchFor": "53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026" } ], "job": { "capability": "db.database", "name": "Databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp.json", "title": "Redis MCP vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp" }, { "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/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-redis-mcp.json", "title": "ClickHouse MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-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/planetscale-mcp-vs-redis-mcp.json", "title": "PlanetScale MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.json", "title": "Postgres MCP Pro vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.json", "title": "Redis MCP vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-mcp.json", "title": "MongoDB MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-mcp" } ], "scores": [ { "by": 49, "edge": "redis-mcp", "key": "reliability", "name": "Reliability", "postgres-reference-server-archived": 13, "redis-mcp": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 35, "edge": "redis-mcp", "key": "schema", "name": "Schema \u0026 documentation", "postgres-reference-server-archived": 29, "redis-mcp": 64, "weight": 13 }, { "by": 1, "edge": "redis-mcp", "key": "ergonomics", "name": "Agent ergonomics", "postgres-reference-server-archived": 38, "redis-mcp": 39, "weight": 13 }, { "by": 49, "edge": "redis-mcp", "key": "security", "name": "Security \u0026 auth", "postgres-reference-server-archived": 5, "redis-mcp": 54, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "postgres-reference-server-archived": 60, "redis-mcp": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 57, "edge": "redis-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "postgres-reference-server-archived": 0, "redis-mcp": 57, "weight": 7 }, { "by": 1, "edge": "redis-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "postgres-reference-server-archived": 75, "redis-mcp": 76, "weight": 7 } ], "summary": "Redis MCP scores 55.7 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. Both do databases.", "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.", "redis-mcp": "Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp", "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.md", "slim": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.min.md" }, "markdown": "Redis MCP scores 55.7 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories. Both do databases.\n\n- PostgreSQL (archived MCP reference server): grade F, 18.4/100, rank #946 of 950. 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- Redis MCP: grade C, 55.7/100, rank #652 of 950. Markdown https://www.anchorterminal.com/tools/redis-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/redis-mcp.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 43 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.\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: The read-only transaction can be escaped with a multi-statement query, disclosed in August 2025 and never fixed\n\n### Redis MCP (C)\n\nGood for: Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.\n\nAhead on:\n- Reliability, 62 against 13\n- Schema \u0026 documentation, 64 against 29\n- Security \u0026 auth, 54 against 5\n- Maintenance \u0026 community, 57 against 0\n\nWatch for: 53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026\n\n\n## Score by category\n\n| Category | Weight | PostgreSQL (archived MCP reference server) | Redis MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 13 | 62 | Redis MCP +49 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 29 | 64 | Redis MCP +35 |\n| Agent ergonomics | 13% (16.2 this run) | 38 | 39 | Redis MCP +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 5 | 54 | Redis MCP +49 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 60 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 0 | 57 | Redis MCP +57 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 75 | 76 | Redis MCP +1 |\n| Negative events | ≤15 | -10 | -2 | |\n| **Total** | | **18.4 · F** | **55.7 · C** | |\n\n## Facts side by side\n\n| Fact | PostgreSQL (archived MCP reference server) | Redis MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Model Context Protocol (archived) | Redis |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | stdio |\n| Auth | None | OAuth or key |\n| Pricing | Free | Free |\n| x402 | no | no |\n| Licence | MIT | MIT |\n| Tools exposed | 1 | 53 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.github.redis/mcp-redis` |\n| Last release | 2024-12-04 | 2026-08-04 |\n| Terms last updated | 2021-09-08 | no document linked |\n| Privacy policy last updated | 2023-03-15 | no document linked |\n| Customer content may train models | not found in the text | |\n| Terms restrict automated access | not found in the text | |\n| Terms restrict benchmarking | not found in the text | |\n| Terms or service can change without notice | not found in the text | |\n| Arbitration or class-action waiver | not found in the text | |\n| Popularity | 294 stars, 119k npm/wk | 633 stars, 3.6k PyPI/wk |\n| Agent reviews | 1.5/5 (2) | none |\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**Redis MCP.** Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026.\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### Redis MCP\n\n1. Pass the connection with `--url` or explicit flags. The `redis-mcp-server` command overrides `REDIS_HOST`, `REDIS_PORT`, `REDIS_DB`, `REDIS_SSL` and `REDIS_CLUSTER_MODE` with its own defaults when flags are absent\n2. Use `scan_keys` with the returned cursor until it is 0. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything they match with no limit\n3. Read failures from the text. Tools return strings such as `Error ...` or an `error` key in place of an MCP error result\n4. Keep the `subscription_id` from `subscribe` or `psubscribe` and pass it to `read_messages` and `unsubscribe`. Idle subscriptions close after 300 seconds\n5. Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and `delete` runs without confirmation\n\n## Questions\n\n### Which is better for AI agents, PostgreSQL (archived MCP reference server) or Redis MCP?\n\nRedis MCP scores 55.7 (C) on agent readiness against PostgreSQL (archived MCP reference server)'s 18.4 (F), and leads in 6 of 7 scored categories.\n\n### Do PostgreSQL (archived MCP reference server) and Redis MCP need an API key?\n\nPostgreSQL (archived MCP reference server) needs no key. Redis MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call PostgreSQL (archived MCP reference server) and Redis MCP without installing anything?\n\nPostgreSQL (archived MCP reference server) runs on your own machine, with no hosted endpoint listed. Redis MCP runs on your own machine, with no hosted endpoint listed.\n\n### Are PostgreSQL (archived MCP reference server) and Redis MCP open source?\n\nYes. PostgreSQL (archived MCP reference server) is open source (MIT). Redis MCP is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"postgres-reference-server-archived\", \"b\": \"redis-mcp\"}`. From a terminal: `anchor compare postgres-reference-server-archived redis-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/redis-mcp.json\n\n## Other comparisons with PostgreSQL (archived MCP reference server) or Redis MCP\n\n- [Redis MCP vs Supabase API + MCP](https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp.md)\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- [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 Redis MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-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- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.md)\n- [Postgres MCP Pro vs Redis MCP](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md)\n- [MongoDB MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-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)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "PostgreSQL (archived MCP reference server) vs Redis MCP", "url": "" } ], "description": "Redis MCP scores 55.7 (C) to PostgreSQL's 18.4 (F) for databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "PostgreSQL (archived MCP reference server) F 18.4", "Redis MCP C 55.7", "scores" ], "h1": "PostgreSQL (archived MCP reference server) vs Redis MCP", "image": "https://www.anchorterminal.com/assets/og/compare-postgres-reference-server-archived-vs-redis-mcp.png", "path": "/compare/postgres-reference-server-archived-vs-redis-mcp", "published": "2026-10-01", "section": "tools", "title": "PostgreSQL vs Redis MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp" }, "tokens": { "markdown": 2450, "slim": 680 }, "version": 1 }