{"id":"jumpserver-redis","name":"redis","homepage":"https://hub.docker.com/r/jumpserver/redis","repo_url":"https://hub.docker.com/r/jumpserver/redis","category":"databases","subcategories":[],"tags":["databases","storage","caching","messaging","infrastructure","key-value","pubsub","redis"],"what_it_does":"Redis is an in-memory data store and key-value database that also supports data structures (e.g., strings, hashes, lists, sets, sorted sets), persistence options, pub/sub, and common caching/queue patterns. It can be used standalone or as part of larger architectures.","use_cases":["Caching (application/session caches)","Message brokering via pub/sub","Queues and background job coordination (e.g., lists/streams patterns)","Rate limiting / throttling state","Real-time leaderboards and counters (sorted sets)","Session storage","Distributed locks and coordination (set-based primitives)"],"not_for":["Serving as a primary relational database for complex queries/joins","Long-term archival storage without persistence/replication planning","Workloads requiring strict ACID transactions across multiple keys (Redis provides limited transactional semantics)","Highly regulated workloads without proper configuration of auth/TLS and network controls"],"best_when":"You need low-latency reads/writes and flexible data structures for caching, coordination, or real-time features, and you can manage persistence, replication, and operational risk appropriately.","avoid_when":"You cannot ensure network isolation and secure configuration (auth/TLS), or you need strict transactional guarantees and relational query capabilities.","alternatives":["Memcached (simple in-memory cache)","KeyDB (Redis-compatible fork)","Apache Ignite (in-memory computing)","Aerospike (high-performance key-value store)","PostgreSQL/SQLite (when relational needs dominate and latency is acceptable)","Cloud managed Redis offerings (e.g., AWS ElastiCache Redis, Azure Cache for Redis)"],"af_score":44.8,"security_score":58.5,"reliability_score":46.2,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:34:10.954267+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":true,"sdk_languages":["Client libraries available broadly across many languages (e.g., Node.js, Python, Java, Go, Rust, .NET)"],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Redis AUTH (password)","TLS client authentication (mTLS) if configured at the server/proxy layer","Network-level controls (VPC/security groups, allowlists)"],"oauth":false,"scopes":false,"notes":"Redis authentication is typically configured on the server (password and/or ACLs depending on Redis version/config). Exact scope model depends on server configuration (ACL users/commands)."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"Self-hosted Redis has infrastructure costs (compute/storage/network). Managed Redis services are typically billed per instance size and throughput."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":44.8,"security_score":58.5,"reliability_score":46.2,"mcp_server_quality":0.0,"documentation_accuracy":40.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":0.0,"tls_enforcement":50.0,"auth_strength":60.0,"scope_granularity":70.0,"dependency_hygiene":50.0,"secret_handling":60.0,"security_notes":"Security depends heavily on configuration. Redis supports AUTH and (in newer versions) ACLs, but agents must not assume secure defaults. TLS may be enabled; without it, credentials can be exposed in transit. Ensure network isolation, disable public access, use strong passwords/ACLs, and avoid logging secrets.","uptime_documented":0.0,"version_stability":70.0,"breaking_changes_history":70.0,"error_recovery":45.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Redis is not an HTTP API; agent integrations often assume REST semantics (status codes, retries) that do not directly apply.","Idempotency varies by command; many write commands are not inherently idempotent.","Operational issues (timeouts, connection drops) need command-level retry/backoff policies managed by the client.","Misconfiguration can expose Redis publicly; ensure auth/TLS and network restrictions."]}}