{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-redis","slug":"redis","name":"Redis","type":"mcp","url":"https://github.com/modelcontextprotocol/servers-archived/tree/main/src/redis","page_url":"https://unfragile.ai/redis","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-redis__cap_0","uri":"capability://tool.use.integration.redis.key.value.store.connection.and.session.management","name":"redis key-value store connection and session management","description":"Establishes and maintains persistent connections to Redis instances through the Model Context Protocol transport layer, handling authentication via connection strings and managing socket lifecycle. The MCP server implements the standard server pattern with stdio or HTTP transport, routing client requests to Redis command handlers while maintaining connection pooling and error recovery for network interruptions.","intents":["Connect an LLM agent to a Redis instance for persistent state management","Enable Claude or other MCP clients to authenticate and communicate with Redis without manual connection handling","Maintain session state across multiple tool invocations in an agentic workflow"],"best_for":["AI agents requiring persistent key-value storage for session state","Teams building LLM-powered applications with Redis backends","Developers integrating Claude Desktop with existing Redis infrastructure"],"limitations":["Archived and unmaintained — no security updates or bug fixes since archival","No built-in connection pooling optimization for high-concurrency scenarios","Single-instance support only — no cluster or sentinel failover handling","Transport limited to stdio or HTTP; no native WebSocket support for long-lived connections"],"requires":["Redis server 4.0+ running and accessible on network","MCP client implementation (Claude Desktop, VS Code extension, or custom SDK)","Node.js 14+ or Python 3.8+ depending on server implementation language","Valid Redis connection string (redis://host:port or redis+unix:///path/to/socket)"],"input_types":["connection string","Redis command parameters","key names and values"],"output_types":["Redis command results (strings, lists, sets, hashes)","status responses","error messages"],"categories":["tool-use-integration","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_1","uri":"capability://tool.use.integration.redis.get.set.del.command.execution.with.type.aware.responses","name":"redis get/set/del command execution with type-aware responses","description":"Executes fundamental Redis commands (GET, SET, DEL, EXISTS, INCR, APPEND, etc.) through MCP tool handlers, parsing command parameters from LLM tool calls and returning type-aware responses that preserve Redis data types (strings, integers, nil). The implementation maps LLM-friendly parameter schemas to Redis command syntax, handling type coercion and serialization for complex values.","intents":["Store and retrieve simple key-value pairs from Redis via LLM tool calls","Increment counters or append to strings without manual Redis client code","Delete keys and check existence as part of agentic workflows","Build LLM-driven state machines using Redis as the backing store"],"best_for":["Solo developers building LLM agents with minimal infrastructure","Rapid prototyping of stateful AI applications","Teams migrating from in-memory state to persistent Redis storage"],"limitations":["No transaction support (MULTI/EXEC) — each command executes independently","No Lua scripting — complex multi-step operations require multiple tool calls","Limited to basic string operations; no native support for Redis Streams or HyperLogLog","No automatic type inference — LLM must specify value types explicitly"],"requires":["Redis server with basic string command support (any version 2.0+)","MCP client with tool-calling capability","Network connectivity to Redis instance"],"input_types":["key name (string)","value (string, integer, or JSON-serialized)","expiration time in seconds (optional)","command flags (NX, XX, EX, PX)"],"output_types":["string value","integer (for INCR, STRLEN, etc.)","boolean (for EXISTS, SET with NX/XX)","nil/null for missing keys"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_2","uri":"capability://tool.use.integration.redis.list.operations.lpush.rpush.lpop.rpop.lrange.with.queue.semantics","name":"redis list operations (lpush, rpush, lpop, rpop, lrange) with queue semantics","description":"Implements Redis list commands through MCP tools, enabling LLM agents to push/pop elements and retrieve ranges from lists. The server translates list operation parameters into Redis commands, handling list indexing, range queries, and blocking operations, with responses formatted as JSON arrays for LLM consumption.","intents":["Implement task queues or job processing pipelines driven by LLM agents","Maintain ordered sequences of events or messages for agentic workflows","Retrieve historical data or conversation context from Redis lists","Build FIFO or LIFO data structures for agent state management"],"best_for":["Agents managing task queues or work pipelines","Applications requiring ordered event logs or message histories","Teams building multi-step workflows with Redis as the coordination layer"],"limitations":["No blocking operations (BLPOP, BRPOP) — agent must poll for new items","No list trimming or rotation — LTRIM requires separate tool call","Limited to sequential access; no random element access (LINDEX requires separate call)","No atomic list-to-list operations (RPOPLPUSH) in single command"],"requires":["Redis server with list command support (any version 2.0+)","MCP client with tool-calling capability","Network connectivity to Redis instance"],"input_types":["list key name (string)","element value (string or JSON-serialized)","start and stop indices for LRANGE","count parameter for LPOP/RPOP (Redis 6.2+)"],"output_types":["JSON array of list elements","integer (count of elements pushed/popped)","single element (for LPOP/RPOP)","nil for empty lists"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_3","uri":"capability://tool.use.integration.redis.hash.operations.hset.hget.hgetall.hdel.with.structured.data.support","name":"redis hash operations (hset, hget, hgetall, hdel) with structured data support","description":"Implements Redis hash commands through MCP tools, allowing LLM agents to store and retrieve structured data as field-value pairs within a single key. The server maps hash operations to JSON objects for LLM consumption, handling field-level access, bulk updates, and nested data serialization through JSON encoding.","intents":["Store structured agent state (e.g., user profiles, session metadata) in Redis","Retrieve and update specific fields of complex objects without full serialization","Implement entity-attribute-value patterns for flexible data models","Build configuration stores or feature flags accessible to multiple agents"],"best_for":["Applications with complex, semi-structured state requirements","Multi-agent systems sharing configuration or metadata","Teams building user profile or session management systems"],"limitations":["No nested hash support — only flat field-value pairs (nested data requires JSON serialization)","No atomic field updates with conditions — HSETNX requires separate call","No field expiration — entire hash expires together or not at all","Limited to string field values; numeric operations require separate HINCRBY call"],"requires":["Redis server with hash command support (any version 2.0+)","MCP client with tool-calling capability","Network connectivity to Redis instance"],"input_types":["hash key name (string)","field name (string)","field value (string or JSON-serialized object)","multiple field-value pairs for HMSET/HSET"],"output_types":["JSON object representing hash (for HGETALL)","string value (for HGET)","integer (for HLEN, HEXISTS)","array of field names or values (for HKEYS, HVALS)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_4","uri":"capability://tool.use.integration.redis.set.operations.sadd.smembers.sismember.sinter.sunion.with.membership.queries","name":"redis set operations (sadd, smembers, sismember, sinter, sunion) with membership queries","description":"Implements Redis set commands through MCP tools, enabling LLM agents to manage unordered collections of unique values and perform set algebra (intersection, union, difference). The server translates set operations to JSON arrays, handling membership tests, bulk additions, and set-to-set operations with automatic deduplication.","intents":["Track unique items (e.g., user IDs, tags, permissions) without duplicates","Compute intersections of sets for recommendation or filtering workflows","Implement role-based access control using set membership","Build tag systems or category management for LLM-driven applications"],"best_for":["Applications requiring membership queries and set operations","Permission or role management systems","Recommendation engines using collaborative filtering patterns"],"limitations":["No ordered sets — use Redis sorted sets (ZSET) for ranked data instead","Set operations (SINTER, SUNION) return results as unordered arrays","No atomic set-to-set moves (SMOVE) in single operation","Limited to string members; numeric comparisons require separate logic"],"requires":["Redis server with set command support (any version 2.0+)","MCP client with tool-calling capability","Network connectivity to Redis instance"],"input_types":["set key name (string)","member value (string)","multiple set keys for SINTER/SUNION/SDIFF","count parameter for SRANDMEMBER"],"output_types":["JSON array of set members (for SMEMBERS, SINTER, SUNION)","boolean (for SISMEMBER)","integer (for SCARD, SINTERCARD)","random member (for SRANDMEMBER)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_5","uri":"capability://tool.use.integration.redis.key.expiration.and.ttl.management.expire.ttl.pexpire.persist","name":"redis key expiration and ttl management (expire, ttl, pexpire, persist)","description":"Implements Redis expiration commands through MCP tools, enabling LLM agents to set time-to-live (TTL) on keys, check remaining expiration time, and remove expiration. The server translates expiration parameters (seconds or milliseconds) into Redis commands, handling absolute and relative expiration times for cache invalidation and session timeout patterns.","intents":["Implement session timeouts or temporary state that auto-cleans without manual deletion","Build cache layers with automatic expiration for LLM-driven applications","Manage rate-limiting buckets or temporary locks with automatic cleanup","Implement sliding-window expiration for activity tracking"],"best_for":["Applications requiring automatic data cleanup or session management","Cache layers with time-based invalidation","Rate-limiting or throttling implementations"],"limitations":["No sub-second precision for expiration (millisecond precision available but not sub-millisecond)","No conditional expiration — cannot expire based on value or access patterns","Expiration is approximate — Redis may delay cleanup by up to 1 second","No expiration callbacks — agent must poll to detect expired keys"],"requires":["Redis server with expiration support (any version 1.2+)","MCP client with tool-calling capability","Network connectivity to Redis instance","System clock synchronization between client and Redis server"],"input_types":["key name (string)","TTL in seconds (integer) or milliseconds (integer)","absolute Unix timestamp (for EXPIREAT/PEXPIREAT)"],"output_types":["integer (remaining TTL in seconds or milliseconds)","boolean (success of EXPIRE/PERSIST operation)","-1 for keys with no expiration","-2 for non-existent keys"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_6","uri":"capability://tool.use.integration.redis.sorted.set.operations.zadd.zrange.zrank.zscore.with.scoring.and.ranking","name":"redis sorted set operations (zadd, zrange, zrank, zscore) with scoring and ranking","description":"Implements Redis sorted set (ZSET) commands through MCP tools, enabling LLM agents to maintain ranked collections with numeric scores. The server translates sorted set operations to JSON arrays with score metadata, handling range queries by score or rank, and score updates, enabling leaderboards and priority queue patterns.","intents":["Build leaderboards or ranking systems for LLM-driven games or competitions","Implement priority queues where agents process items by score","Track time-series data with timestamps as scores (e.g., event logs)","Maintain sorted recommendations or search results with relevance scores"],"best_for":["Applications requiring ranked or scored data","Leaderboard or competitive gaming systems","Priority queue implementations with dynamic scoring"],"limitations":["Scores are floating-point; precision limited to IEEE 754 double precision","No multi-field sorting — only single numeric score per member","Range queries by score (ZRANGEBYSCORE) require separate tool call","No atomic score-based operations (e.g., increment and get rank in one call)"],"requires":["Redis server with sorted set support (any version 1.2+)","MCP client with tool-calling capability","Network connectivity to Redis instance"],"input_types":["sorted set key name (string)","member value (string)","numeric score (float or integer)","start and stop indices for ZRANGE","min and max scores for ZRANGEBYSCORE"],"output_types":["JSON array of members with scores (for ZRANGE with WITHSCORES)","integer (rank or count)","float (score value)","boolean (success of ZADD/ZREM)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_7","uri":"capability://tool.use.integration.redis.pattern.based.key.scanning.keys.scan.with.glob.pattern.matching","name":"redis pattern-based key scanning (keys, scan) with glob pattern matching","description":"Implements Redis key discovery commands through MCP tools, enabling LLM agents to find keys matching glob patterns (KEYS) or iterate through keyspace with cursor-based scanning (SCAN). The server translates pattern parameters to Redis commands, returning matching key names as JSON arrays, with SCAN providing non-blocking iteration for large keyspaces.","intents":["Discover keys matching a pattern (e.g., all session keys for a user)","Iterate through Redis keyspace without blocking the server","Implement key cleanup or migration workflows based on naming patterns","Build key introspection tools for debugging or monitoring"],"best_for":["Applications requiring key discovery or pattern-based operations","Debugging and monitoring tools for Redis instances","Data migration or cleanup workflows"],"limitations":["KEYS command blocks Redis server — unsafe for production with large keyspaces (use SCAN instead)","SCAN cursor is opaque and server-specific — cannot be reused across server restarts","Pattern matching limited to glob syntax (*, ?, [abc]) — no regex support","No atomic key discovery with filtering — pattern matching happens server-side but results may change between calls"],"requires":["Redis server with KEYS or SCAN support (SCAN added in Redis 2.8+)","MCP client with tool-calling capability","Network connectivity to Redis instance"],"input_types":["glob pattern (string, e.g., 'user:*', 'session:*:data')","cursor for SCAN (string, starting with '0')","count hint for SCAN (integer, default 10)"],"output_types":["JSON array of matching key names (for KEYS)","cursor and array of keys (for SCAN)","empty array if no matches"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-redis__cap_8","uri":"capability://tool.use.integration.redis.database.selection.and.namespace.isolation.select.flushdb.dbsize","name":"redis database selection and namespace isolation (select, flushdb, dbsize)","description":"Implements Redis database selection and management commands through MCP tools, enabling LLM agents to switch between Redis logical databases (0-15 by default) and manage database-level operations. The server translates database commands to Redis, handling namespace isolation for multi-tenant or multi-environment scenarios, with DBSIZE providing database statistics.","intents":["Isolate agent state across different environments (dev, staging, prod) using separate databases","Implement multi-tenant systems where each tenant has a dedicated Redis database","Clear test data or reset state by flushing entire databases","Monitor database size and key counts for capacity planning"],"best_for":["Multi-tenant applications requiring logical isolation","Development workflows with separate test/staging/prod databases","Teams managing multiple Redis environments"],"limitations":["Database isolation is logical only — no encryption or access control between databases","FLUSHDB is destructive and non-recoverable — no undo or backup integration","Limited to 16 databases by default (configurable in Redis but not via MCP tool)","No atomic cross-database operations — transactions cannot span multiple databases"],"requires":["Redis server with multiple databases enabled (default configuration)","MCP client with tool-calling capability","Network connectivity to Redis instance","Administrative privileges for FLUSHDB operations"],"input_types":["database index (integer 0-15)","no parameters for DBSIZE or FLUSHDB"],"output_types":["integer (database index for SELECT, key count for DBSIZE)","status message (for FLUSHDB)","boolean (success of SELECT)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":29,"verified":false,"data_access_risk":"high","permissions":["Redis server 4.0+ running and accessible on network","MCP client implementation (Claude Desktop, VS Code extension, or custom SDK)","Node.js 14+ or Python 3.8+ depending on server implementation language","Valid Redis connection string (redis://host:port or redis+unix:///path/to/socket)","Redis server with basic string command support (any version 2.0+)","MCP client with tool-calling capability","Network connectivity to Redis instance","Redis server with list command support (any version 2.0+)","Redis server with hash command support (any version 2.0+)","Redis server with set command support (any version 2.0+)"],"failure_modes":["Archived and unmaintained — no security updates or bug fixes since archival","No built-in connection pooling optimization for high-concurrency scenarios","Single-instance support only — no cluster or sentinel failover handling","Transport limited to stdio or HTTP; no native WebSocket support for long-lived connections","No transaction support (MULTI/EXEC) — each command executes independently","No Lua scripting — complex multi-step operations require multiple tool calls","Limited to basic string operations; no native support for Redis Streams or HyperLogLog","No automatic type inference — LLM must specify value types explicitly","No blocking operations (BLPOP, BRPOP) — agent must poll for new items","No list trimming or rotation — LTRIM requires separate tool call","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.28,"ecosystem":0.3,"match_graph":0.25,"freshness":0.9,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:21.011Z","last_scraped_at":"2026-05-03T14:00:18.053Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=redis","compare_url":"https://unfragile.ai/compare?artifact=redis"}},"signature":"4Mn4GGHD5an6u09/Q4i3bjtulL6DpJgfypH+RTNZld0BjEyuCJaEv0iJCYKUHTRPJJiOhEIU69VYOSdozcnOCQ==","signedAt":"2026-06-17T01:09:00.526Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/redis","artifact":"https://unfragile.ai/redis","verify":"https://unfragile.ai/api/v1/verify?slug=redis","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}