Field-by-field comparison
Compare the evidence before choosing an MCP.
Each signal stays separate, missing facts remain visible, and the column order follows your selection.
| Evidence field | Neon MCPWatchlist candidate | Redis MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | First-party MCP Neon · Publisher source ↗ | First-party MCP Redis · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 13, 2026 Package: Sep 16, 2025 | Repo: Aug 5, 2026 Package: Aug 5, 2026 |
| Popularity evidence | ||
| GitHub stars | 624 GitHub stars · checked 2026-08-14T18:46:26.000Z | 568 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 6,433 30-day package downloads · checked 2026-07-29T17:30:00.000Z | 22,058 PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| Client coverage | ||
| Client coverage details | Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP | Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio |
| Client coverage note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Authentication follows the publisher's documented endpoint or local-server configuration. OAuth scopes, API-key handling, and revocation behavior remain review items. | Supports Redis username/password URLs, individual credential options, TLS through `rediss://`, CA certificate verification, cluster mode, and Microsoft Entra ID authentication for Azure Managed Redis. |
| Cost | No MCP100 cost conclusion is published yet. The publisher's account plan, API usage, infrastructure, or per-action charges may apply. | The first-party server is open source and the PyPI package documents no MCP usage fee. Redis Cloud, infrastructure, network, container, and AI-client costs remain separate. |
| Permissions | Exact permissions and the read/write boundary have not yet completed MCP100 independent review; consult the linked publisher sources and use the narrowest available scope. | The server can read and write Redis keys and data structures, operate streams and pub/sub, manage search indexes, and inspect server information according to the connected Redis user's ACL. Redis ACL configuration is the effective permission boundary. |
| Data handling | Publisher-accessible account or application data may be returned to the MCP client and its selected model. Retention and subprocess behavior require candidate-specific review. | The stdio server runs locally and sends Redis query inputs and returned key values to the connected MCP client. It connects directly to the configured Redis deployment. Credentials can be supplied in a URI, CLI arguments, or environment variables; avoid embedding them in shareable config and logs. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Use a test workspace or non-production account, least privilege, read-only controls where available, explicit approval for mutations, and credential revocation after evaluation. | A broad Redis tool set can expose or mutate application state, sessions, queues, cached records, and vector data. Use a dedicated database, a narrowly scoped ACL user, verified TLS, pinned releases, and backups. This review does not claim MCP100 execution testing. |
| Evidence date | ||
| Editorial review | 2026-07-24 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →