ToolsMCP
redis-mcp
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- upstash (GitHub)
- Prerequisites
- Install @upstash/redis-mcp from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.1 · updated
- Official links
Publisher’s description
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.1, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- upstash (GitHub)
- Version observed
- 0.1.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.upstash%2Fredis-mcp/versions/0.1.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Find the official reference for a CLI command | Publisher description mentions “commands”, “docs”, “look up”, “search”. | No connection check or task run. Capability is as described by the publisher. | Rule cli-reference matched: “commands”, “docs”, “look up”, “search”. Rule cli-reference. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
@upstash/redis-mcp(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.upstash/redis-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.