# Redis MCP vs ReqRes MCP server (slim)

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

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

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.

- Redis MCP: C 54.9, rank #893 of 1510 · https://www.anchorterminal.com/tools/redis-mcp.min.md
- ReqRes MCP server: D 48.8, rank #1114 of 1510 · https://www.anchorterminal.com/tools/reqres-mcp.min.md
- Redis MCP, good 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. Ahead on Reliability, 52 against 30; Security & auth, 54 against 33; Payments & pricing, 60 against 50; Transparency & trust, 77 against 47. Also Runs on your own machine; Open source.
- ReqRes MCP server, good for Coding agents that need a throwaway or starter backend for a prototype, with no account to set up. Ahead on Agent ergonomics, 76 against 39. Also No key needed to call it; A hosted endpoint, with nothing to install.

| Category | Redis MCP | ReqRes MCP server |
| --- | --- | --- |
| Reliability (16%) | 52 | 30 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 64 | 61 |
| Agent ergonomics (13%) | 39 | 76 |
| Security & auth (14%) | 54 | 33 |
| Payments & pricing (10%) | 60 | 50 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 47 | 50 |
| Transparency & trust (7%) | 77 | 47 |

| Fact (where they differ) | Redis MCP | ReqRes MCP server |
| --- | --- | --- |
| Vendor | Redis | ReqRes |
| Hosted endpoint | no (local only) | `https://reqres.in/mcp` |
| Transports | stdio | Streamable HTTP |
| Auth | OAuth or key | None |
| Pricing | Free | Freemium |
| Licence | MIT | none |
| Tools exposed | 53 | 7 |
| Read-only variant documented | yes | no |
| MCP registry | `io.github.redis/mcp-redis` | `in.reqres/reqres` |
| Last release | 2026-08-04 | none |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | not read yet |
| Popularity | 633 stars | none |

Why the edge:
- Agent ergonomics, ReqRes MCP server +37: 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).); ReqRes MCP server 76 (Seven compact tools (25). list_records is paginated (15 of 20). No documented errors (3 of 20). Annotated, two read-only, and delete_record marked (18 of 20). No key needed and a plain REST API behind it (15). 25 + 15 + 3 + 18 + 15 = 76.)
- Transparency & trust, Redis MCP +30: 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).); ReqRes MCP server 47 (Closed service under readable terms; operating company not named in the parts read (10 of 30). You own your data, unclaimed agent projects are deleted after 72 hours, and the terms say the free service can end with reasonable notice (22 of 30). That notice clause and the 72-hour rule are dated commitments (10 of 20). Subprocessors not found (5 of 20). 10 + 22 + 10 + 5 = 47.)
- Reliability, Redis MCP +22: 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).); 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.)
- Security & auth, Redis MCP +21: 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).); 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.)
- Payments & pricing, Redis MCP +10: 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.); 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.)