io.github.YawLabs/redis-mcp
Redis MCP Server
Is the Redis MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-12.
Read-first Redis MCP: SCAN key explorer, keyspace/TTL/memory/slowlog stats, DBA advisor
alive probed 2026-11-15 · unchanged since 2026-11-12
- Run it
- npx -y @yawlabs/redis-mcp@0.5.7 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- @yawlabs/redis-mcp 0.5.7
- Capabilities
- tools
- Instructions
- 855 characters
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 3.4k tokens in Claude Opus 5.5, exact, measured 2026-11-12. With the Claude Code prefix mcp__…__ on each tool name: 3.5k. The o200k_base estimate is 2.0k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/YawLabs/redis-mcp
- Website
- https://yaw.sh/mcp-servers/redis-mcp/
- Registry
- active, updated 2026-11-12 · registry entry
- Changes
- 3 recorded, reachable in 3 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.69×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| redis_advisor | 976 | 576 | 29 % |
| redis_scan | 646 | 381 | 19 % |
| redis_get | 471 | 278 | 14 % |
| redis_command | 466 | 275 | 14 % |
| redis_health | 302 | 178 | 9 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.YawLabs/mcph · needs env
- io.github.YawLabs/nol-mcp · not found
- npm Registry MCP Server io.github.YawLabs/npmjs-mcp · alive
- PostgreSQL MCP Server io.github.YawLabs/postgres-mcp · alive
- SSH MCP Server io.github.YawLabs/ssh-mcp · alive
- Tailscale MCP Server io.github.YawLabs/tailscale-mcp · alive
- Terraform CWD MCP Server io.github.YawLabs/terraform-cwd-mcp · alive
- io.github.YawLabs/vew-mcp · alive
Servers that mention redis.
- ai.getvda/elasticsearch-mongodb-redis-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/elasticsearch-redis-mysql-stack-generator · newer protocol
- ai.getvda/elasticsearch-redis-stack-generator · newer protocol
- ai.getvda/elasticsearch-redis-stack-generator-elasticsearch-elasticsearch · newer protocol
- ai.getvda/kafka-minio-redis-stack-generator · newer protocol
- ai.getvda/kafka-redis-minio-stack-generator · newer protocol
- ai.getvda/memcached-mongodb-redis-compose-generator · newer protocol
- ai.getvda/minio-and-redis-storage-stack · newer protocol
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-12 09:02 | alive | 232 ms | 7 | 3.4k | 2.0k |
| 2026-10-27 07:02 | alive | 183 ms | 7 | 3.4k | 2.0k |
| 2026-10-20 06:47 | alive | 303 ms | 7 | 2.0k |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers initialize and tools/list. Nothing to fix.