{ "data": { "a": { "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", "dns": "redis-mcp.grade.anchorterminal.com", "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": null, "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": 54.9, "grade": "C", "agentReady": false, "rank": 893, "ranked": true, "rankOf": 1510, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 39, "maintenance": 47, "payments": 60, "reliability": 52, "schema": 64, "security": 54, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": 0, "verdict": "Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a CI workflow that tests five Python versions against a live Redis. It has no read-only mode, tool annotations or changelog file, no release has followed 0.5.1 of 4 August 2026, and PyPI installs failed to start from 28 July to 5 August.", "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` per the 9 October check", "CI runs pytest on pushes, pull requests and nightly across Python 3.10 to 3.14 against a live Redis, with 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`, still true on main on 3 November 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.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 54.9 } ], "editorialScores": { "ergonomics": 39, "maintenance": 47, "payments": 60, "reliability": 52, "schema": 64, "security": 54, "transparency": 65 }, "provenanceScore": 89, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "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": 89 }, "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-11-07T00:00:37.586801547Z" }, { "registry": "mcp-registry", "name": "io.github.redis/mcp-redis", "version": "0.5.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "redis-mcp-server", "version": "0.5.1", "released": "2026-08-05", "seenAt": "2026-11-07T00:00:37.365630293Z" } ], "githubStars": 641, "pypiWeekly": 2895, "securityTxt": { "url": "https://redis.io/.well-known/security.txt", "state": "valid", "expires": "2030-12-19T00:00:00Z", "checkedAt": "2026-11-07T16:00:27.489844353Z" }, "llmsTxt": { "url": "https://redis.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:43.940804068Z" }, "domain": { "domain": "redis.io", "checkedAt": "2026-11-01T14:21:23.110601118Z" }, "github": { "repo": "redis/mcp-redis", "checkedAt": "2026-11-02T09:20:36.173885498Z", "stars": 641, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-26T16:33:56Z", "openIssues": 7, "openPRs": 7, "issuesOpened90d": 7, "issuesClosed90d": 10, "prsMerged90d": 14, "ci": { "branch": "main", "runs": 50, "success": 49, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-10-26T16:35:29Z" }, "replies": { "sampled": 25, "unanswered": 4, "medianDays": 1.9 } }, "updatedAt": "2026-11-07T18:16:28.95801333Z" } }, "answer": "Redis MCP scores 54.9 (C) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on agent ergonomics.", "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": 37, "category": "ergonomics", "leads": "reqres-mcp", "name": "Agent ergonomics", "reasons": { "a": "53 tools load at once, about 15,700 characters of descriptions, with no toolsets, dynamic loading or read-only subset. Pull request #161 for an allowlist has been open since 28 July 2026 (5 of 25). `scan_keys` pages with a cursor, `lrange` and `zrange` take ranges, `xrange` and `xreadgroup` take a count, `read_messages` caps at 100 and the vector tools take `k`. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything with no limit (12 of 20). Failures come back as ordinary results, a string starting `Error` or a dictionary with an `error` key, carrying the Redis error text. Input checks return clear messages, such as the refusal of `block_ms=0`. Nothing marks a result as an MCP error and no error list is documented (9 of 20). No tool declares `readOnlyHint`, `destructiveHint` or `idempotentHint`, and pull request #181 adding them was opened on 8 October 2026. No retry guidance was found, and `lpush`, `xadd` and `publish` are not safe to repeat (3 of 20). Most tools need one or two arguments and defaults are stated in the descriptions. The server is a Python package only (10 of 15).", "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": 39, "b": 76 } }, { "by": 30, "category": "transparency", "leads": "redis-mcp", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT (30). Local software that connects to the configured Redis. `search_redis_documents` sends each question to redis.io, which the README mentions through `MCP_DOCS_SEARCH_URL` without saying what is sent or kept. The Redis Privacy Policy, last updated 29 November 2024, does not address this software, and no telemetry code was found in the 0.5.1 source (18 of 30). No deprecation policy. The README warns that the main branch may contain breaking changes, and the `unsubscribe` change in 0.5.1 came with no notice (4 of 20). No usage statistics on the evidence of the source. The docs search call can be redirected or switched off with an empty `MCP_DOCS_SEARCH_URL`, which the README does not present as an opt-out (13 of 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": 22, "category": "reliability", "leads": "redis-mcp", "name": "Reliability", "reasons": { "a": "Scored as local software, since the owner runs it over stdio. Official PyPI package `redis-mcp-server` with Python 3.10 to 3.14 stated in the metadata, though the README badge says 3.14 and later (20). The CI workflow runs on pushes, pull requests and nightly, on a five-version Python matrix against a live Redis with pytest and an 80 per cent coverage floor, but its run results couldn't be read on 4 November 2026 (GitHub's pages and API answered 403), so 15 under this run's reading for test CI with an unreadable result. Fresh PyPI installs failed to start from 28 July to 5 August 2026 after `mcp` 2.0.0 removed the module the server imports, fixed in 0.5.1 (issues #163 and #169). Issue #156, where the console command ignores `REDIS_HOST` and `REDIS_PORT`, was open with two unmerged fixes per the 9 October check (13 of 25). Tagged releases with numbers in semantic form, but no changelog file, release notes that are lists of pull request titles, and a patch release (0.5.1) that changed the `unsubscribe` input and added six tools. Issue #137 asking for semver tags had no reply (4 of 15). Version 0.5.1 with the classifier `Development Status :: 4 - Beta` (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": 52, "b": 30 } }, { "by": 21, "category": "security", "leads": "redis-mcp", "name": "Security \u0026 auth", "reasons": { "a": "The server holds one Redis username and password, which Redis ACL rules can scope to keys and command categories and an admin can revoke, or Entra ID credentials for Azure Managed Redis with token renewal. TLS certificate checks are required by default. The README's main example passes the password inside `--url` on the command line, and every caller shares the one user (22 of 30). The server has no read-only mode, no allowlist and no confirmation before `delete`, `json_del`, `xdel` or `xgroup_destroy`. The README gives an ACL example for a read-only user, and no tool runs an arbitrary command, so `FLUSHALL`, `CONFIG` and `EVAL` are out of reach (9 of 20). Stored values, pub/sub messages and docs search results reach the model as they are. No injection guidance was found in the README or the docs pages read (2 of 15). Logging goes to stderr at WARNING by default, so calls are not recorded unless the level is lowered. The connection names itself `redis-py(mcp-server_v0.5.1)`, which Redis shows in `CLIENT LIST` (6 of 15). Redis has a valid security.txt, a HackerOne disclosure programme, and SOC 2 Type 2 and ISO/IEC 27001 on its trust centre. CI runs Bandit and hardened runners, and Dependabot updates are merged within days. The repository has no SECURITY.md and no published advisories (15 of 20).", "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": 54, "b": 33 } }, { "by": 10, "category": "payments", "leads": "redis-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "Read with the self-hosted rule. The server is free under the MIT licence and needs no signup of its own, so 20 + 20 + 20. No x402, MPP or L402 (0). It needs a Redis database, which can be free Redis Open Source on the owner's machine. Redis Cloud prices were not checked. No hosted version of this server was found on the pages read.", "b": "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." }, "scores": { "a": 60, "b": 50 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Redis", "b": "ReqRes", "name": "Vendor" }, { "a": "no (local only)", "b": "https://reqres.in/mcp", "name": "Hosted endpoint" }, { "a": "stdio", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "none", "name": "Licence" }, { "a": "53", "b": "7", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.redis/mcp-redis", "b": "in.reqres/reqres", "name": "MCP registry" }, { "a": "2026-08-04", "b": "none", "name": "Last release" }, { "a": "no document linked", "b": "not read yet", "name": "Terms last updated" }, { "a": "no document linked", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "633 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Redis MCP scores 54.9 (C) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on agent ergonomics.", "question": "Which is better for AI agents, Redis MCP or ReqRes MCP server?" }, { "answer": "Redis MCP takes an API key or an OAuth sign-in. ReqRes MCP server needs no key.", "question": "Do Redis MCP and ReqRes MCP server need an API key?" }, { "answer": "Redis MCP 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 Redis MCP and ReqRes MCP server without installing anything?" }, { "answer": "Redis MCP is open source (MIT). No open-source release is listed for ReqRes MCP server.", "question": "Are Redis MCP and ReqRes MCP server open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 52 against 30", "Security \u0026 auth, 54 against 33", "Payments \u0026 pricing, 60 against 50", "Transparency \u0026 trust, 77 against 47" ], "also": [ "Runs on your own machine", "Open source" ], "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" }, { "aheadOn": [ "Agent ergonomics, 76 against 39" ], "also": [ "No key needed to call it", "A hosted endpoint, with nothing to install" ], "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": { "redis-mcp": [ { "causes": [ "evidence", "method", "time" ], "date": "2026-11-04", "delta": -0.9, "from": 55.8, "fromGrade": "C", "to": 54.9, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 55.7, "fromGrade": "C", "to": 55.8, "toGrade": "C" } ], "reqres-mcp": null }, "job": { "capability": "db.document", "name": "Document 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-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/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-redis-mcp.json", "title": "DBHub vs Redis MCP", "url": "https://www.anchorterminal.com/compare/dbhub-vs-redis-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/neon-mcp-vs-redis-mcp.json", "title": "Neon MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp" }, { "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-redis-mcp.json", "title": "ObsessionDB vs Redis MCP", "url": "https://www.anchorterminal.com/compare/obsessiondb-vs-redis-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-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/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-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/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/postgres-reference-server-archived-vs-reqres-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs ReqRes MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-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/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-redis-mcp.json", "title": "MCP Toolbox for Databases vs Redis MCP", "url": "https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-redis-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-redis-mcp.json", "title": "MongoDB MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-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" } ], "panel": null, "scores": [ { "by": 22, "edge": "redis-mcp", "key": "reliability", "name": "Reliability", "redis-mcp": 52, "reqres-mcp": 30, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "redis-mcp", "key": "schema", "name": "Schema \u0026 documentation", "redis-mcp": 64, "reqres-mcp": 61, "weight": 13 }, { "by": 37, "edge": "reqres-mcp", "key": "ergonomics", "name": "Agent ergonomics", "redis-mcp": 39, "reqres-mcp": 76, "weight": 13 }, { "by": 21, "edge": "redis-mcp", "key": "security", "name": "Security \u0026 auth", "redis-mcp": 54, "reqres-mcp": 33, "weight": 14 }, { "by": 10, "edge": "redis-mcp", "key": "payments", "name": "Payments \u0026 pricing", "redis-mcp": 60, "reqres-mcp": 50, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "reqres-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "redis-mcp": 47, "reqres-mcp": 50, "weight": 7 }, { "by": 30, "edge": "redis-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "redis-mcp": 77, "reqres-mcp": 47, "weight": 7 } ], "summary": "Redis MCP scores 54.9 (C) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on agent ergonomics. Both do document databases.", "tasks": null, "tutorials": [], "verdicts": { "redis-mcp": "Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a CI workflow that tests five Python versions against a live Redis. It has no read-only mode, tool annotations or changelog file, no release has followed 0.5.1 of 4 August 2026, and PyPI installs failed to start from 28 July to 5 August.", "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/redis-mcp-vs-reqres-mcp", "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.min.md" }, "markdown": "Redis MCP scores 54.9 (C) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on agent ergonomics. Both do document databases.\n\n- Redis MCP: grade C, 54.9/100, rank #893 of 1510. Markdown https://www.anchorterminal.com/tools/redis-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/redis-mcp.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### 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, 52 against 30\n- Security \u0026 auth, 54 against 33\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: 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### 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- Agent ergonomics, 76 against 39\n\nAlso in its favour:\n- No key needed to call it\n- A hosted endpoint, with nothing to install\n\nWatch for: A sponsored line in every successful result unless ?sponsor=0\n\n\n## Why the edge\n\n### Agent ergonomics: ReqRes MCP server +37\n\n- Redis MCP (39): 53 tools load at once, about 15,700 characters of descriptions, with no toolsets, dynamic loading or read-only subset. Pull request #161 for an allowlist has been open since 28 July 2026 (5 of 25). `scan_keys` pages with a cursor, `lrange` and `zrange` take ranges, `xrange` and `xreadgroup` take a count, `read_messages` caps at 100 and the vector tools take `k`. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything with no limit (12 of 20). Failures come back as ordinary results, a string starting `Error` or a dictionary with an `error` key, carrying the Redis error text. Input checks return clear messages, such as the refusal of `block_ms=0`. Nothing marks a result as an MCP error and no error list is documented (9 of 20). No tool declares `readOnlyHint`, `destructiveHint` or `idempotentHint`, and pull request #181 adding them was opened on 8 October 2026. No retry guidance was found, and `lpush`, `xadd` and `publish` are not safe to repeat (3 of 20). Most tools need one or two arguments and defaults are stated in the descriptions. The server is a Python package only (10 of 15).\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### Transparency \u0026 trust: Redis MCP +30\n\n- Redis MCP (77): MIT (30). Local software that connects to the configured Redis. `search_redis_documents` sends each question to redis.io, which the README mentions through `MCP_DOCS_SEARCH_URL` without saying what is sent or kept. The Redis Privacy Policy, last updated 29 November 2024, does not address this software, and no telemetry code was found in the 0.5.1 source (18 of 30). No deprecation policy. The README warns that the main branch may contain breaking changes, and the `unsubscribe` change in 0.5.1 came with no notice (4 of 20). No usage statistics on the evidence of the source. The docs search call can be redirected or switched off with an empty `MCP_DOCS_SEARCH_URL`, which the README does not present as an opt-out (13 of 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### Reliability: Redis MCP +22\n\n- Redis MCP (52): Scored as local software, since the owner runs it over stdio. Official PyPI package `redis-mcp-server` with Python 3.10 to 3.14 stated in the metadata, though the README badge says 3.14 and later (20). The CI workflow runs on pushes, pull requests and nightly, on a five-version Python matrix against a live Redis with pytest and an 80 per cent coverage floor, but its run results couldn't be read on 4 November 2026 (GitHub's pages and API answered 403), so 15 under this run's reading for test CI with an unreadable result. Fresh PyPI installs failed to start from 28 July to 5 August 2026 after `mcp` 2.0.0 removed the module the server imports, fixed in 0.5.1 (issues #163 and #169). Issue #156, where the console command ignores `REDIS_HOST` and `REDIS_PORT`, was open with two unmerged fixes per the 9 October check (13 of 25). Tagged releases with numbers in semantic form, but no changelog file, release notes that are lists of pull request titles, and a patch release (0.5.1) that changed the `unsubscribe` input and added six tools. Issue #137 asking for semver tags had no reply (4 of 15). Version 0.5.1 with the classifier `Development Status :: 4 - Beta` (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### Security \u0026 auth: Redis MCP +21\n\n- Redis MCP (54): The server holds one Redis username and password, which Redis ACL rules can scope to keys and command categories and an admin can revoke, or Entra ID credentials for Azure Managed Redis with token renewal. TLS certificate checks are required by default. The README's main example passes the password inside `--url` on the command line, and every caller shares the one user (22 of 30). The server has no read-only mode, no allowlist and no confirmation before `delete`, `json_del`, `xdel` or `xgroup_destroy`. The README gives an ACL example for a read-only user, and no tool runs an arbitrary command, so `FLUSHALL`, `CONFIG` and `EVAL` are out of reach (9 of 20). Stored values, pub/sub messages and docs search results reach the model as they are. No injection guidance was found in the README or the docs pages read (2 of 15). Logging goes to stderr at WARNING by default, so calls are not recorded unless the level is lowered. The connection names itself `redis-py(mcp-server_v0.5.1)`, which Redis shows in `CLIENT LIST` (6 of 15). Redis has a valid security.txt, a HackerOne disclosure programme, and SOC 2 Type 2 and ISO/IEC 27001 on its trust centre. CI runs Bandit and hardened runners, and Dependabot updates are merged within days. The repository has no SECURITY.md and no published advisories (15 of 20).\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### Payments \u0026 pricing: Redis MCP +10\n\n- Redis MCP (60): Read with the self-hosted rule. The server is free under the MIT licence and needs no signup of its own, so 20 + 20 + 20. No x402, MPP or L402 (0). It needs a Redis database, which can be free Redis Open Source on the owner's machine. Redis Cloud prices were not checked. No hosted version of this server was found on the pages read.\n- 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.\n\n## Score by category\n\n| Category | Weight | Redis MCP | ReqRes MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 52 | 30 | Redis MCP +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 61 | Redis MCP +3 |\n| Agent ergonomics | 13% (16.2 this run) | 39 | 76 | ReqRes MCP server +37 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 33 | Redis MCP +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 50 | Redis MCP +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 47 | 50 | ReqRes MCP server +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 47 | Redis MCP +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.9 · C** | **48.8 · D** | |\n\n## Facts side by side\n\n| Fact | Redis MCP | ReqRes MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Redis | ReqRes |\n| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |\n| Transports | stdio | Streamable HTTP |\n| Auth | OAuth or key | None |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | MIT | none |\n| Tools exposed | 53 | 7 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.redis/mcp-redis` | `in.reqres/reqres` |\n| Last release | 2026-08-04 | none |\n| Terms last updated | no document linked | not read yet |\n| Privacy policy last updated | no document linked | not read yet |\n| Popularity | 633 stars | none |\n\n## How the scores have moved\n\n### Redis MCP\n\n- -0.9 on 4 November 2026: new evidence, checklist, time\n- +0.1 on 27 October 2026: checklist\n\n### ReqRes MCP server\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Redis MCP.** Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a CI workflow that tests five Python versions against a live Redis. It has no read-only mode, tool annotations or changelog file, no release has followed 0.5.1 of 4 August 2026, and PyPI installs failed to start from 28 July to 5 August.\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### 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### 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, Redis MCP or ReqRes MCP server?\n\nRedis MCP scores 54.9 (C) on agent readiness against ReqRes MCP server's 48.8 (D), and leads in 5 of 7 scored categories. ReqRes MCP server leads on agent ergonomics.\n\n### Do Redis MCP and ReqRes MCP server need an API key?\n\nRedis MCP takes an API key or an OAuth sign-in. ReqRes MCP server needs no key.\n\n### Can an agent call Redis MCP and ReqRes MCP server without installing anything?\n\nRedis MCP 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 Redis MCP and ReqRes MCP server open source?\n\nRedis MCP 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/redis-mcp-vs-reqres-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"redis-mcp\", \"b\": \"reqres-mcp\"}`. From a terminal: `anchor compare redis-mcp reqres-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/redis-mcp.json and https://www.anchorterminal.com/api/v1/tools/reqres-mcp.json\n\n## Other comparisons with Redis MCP or ReqRes MCP server\n\n- [Redis MCP vs Supabase API + MCP](https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp.md)\n- [ClickHouse MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-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 Redis MCP](https://www.anchorterminal.com/compare/dbhub-vs-redis-mcp.md)\n- [DBHub vs ReqRes MCP server](https://www.anchorterminal.com/compare/dbhub-vs-reqres-mcp.md)\n- [Neon MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/neon-mcp-vs-redis-mcp.md)\n- [Neon MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/neon-mcp-vs-reqres-mcp.md)\n- [ObsessionDB vs Redis MCP](https://www.anchorterminal.com/compare/obsessiondb-vs-redis-mcp.md)\n- [ObsessionDB vs ReqRes MCP server](https://www.anchorterminal.com/compare/obsessiondb-vs-reqres-mcp.md)\n- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-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 Redis MCP](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-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- [PostgreSQL (archived MCP reference server) vs ReqRes MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-reqres-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.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 Redis MCP](https://www.anchorterminal.com/compare/mcp-toolbox-databases-vs-redis-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 Redis MCP](https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-mcp.md)\n- [MongoDB MCP Server vs ReqRes MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-reqres-mcp.md)\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": "Redis MCP vs ReqRes MCP server", "url": "" } ], "description": "Redis MCP scores 54.9 (C) to ReqRes's 48.8 (D) for document databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Redis MCP C 54.9", "ReqRes MCP server D 48.8", "scores" ], "h1": "Redis MCP vs ReqRes MCP server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/redis-mcp-vs-reqres-mcp", "published": "2026-10-01", "section": "tools", "title": "Redis MCP vs ReqRes for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-reqres-mcp" }, "tokens": { "markdown": 4050, "slim": 2230 }, "version": 1 }