io.github.upstash/redis-mcp
NPM · @UPSTASH/REDIS-MCP · SCANNED AUG 3
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (99 of 103), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to upstash/redis-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 743 tokens (~371/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @upstash/redis-mcp
claude mcp add upstash-redis-mcp -- npx -y @upstash/redis-mcp
codex mcp add upstash-redis-mcp -- npx -y @upstash/redis-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"upstash-redis-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@upstash/redis-mcp"
],
"enabled": true
}
}
} openclaw mcp add upstash-redis-mcp --command npx --arg -y --arg @upstash/redis-mcp
mcp_servers:
upstash-redis-mcp:
command: "npx"
args: ["-y", "@upstash/redis-mcp"] {
"mcpServers": {
"upstash-redis-mcp": {
"command": "npx",
"args": [
"-y",
"@upstash/redis-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +58
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: upstash/redis-mcp security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 42
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/@upstash/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- upstash/redis-mcp
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/upstash/redis-mcp/.github/workflows/release.yaml@refs/tags/v0.1.1
- Rekor log index:
- 2116831130
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:0f06e20f937ff648e3832d86841793b6686419f05e1a7aa431f36c6ebb2faa8c0fb087f2f3eb24213b2caef013ae2cd36115fe0af17a61b8ee38a59f0
- Discovery method:
- attestation_endpoint
Dependencies 99 packages
99 packages in the resolved dependency tree · 99 deprecated · 30 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
redis_run_commands ~537
Run one or more Redis commands against an Upstash Redis database (this server is ONLY for Upstash Redis). Commands are sent over HTTP/REST or native TCP depending on how the target database is configured — you don't choose the transport. By default multiple commands run as a pipeline: each returns its own result/error, and one failure does not abort the others. Set transaction:true to run them atomically (MULTI/EXEC). For discovery prefer SCAN over KEYS, and use TYPE to inspect a key. A valid command that fails (e.g. WRONGTYPE) returns a per-command error while the rest of the pipeline still runs; a malformed/unknown command can cause the whole request to be rejected. Upstash Redis Search runs through THIS tool via SEARCH.* commands (SEARCH.LISTINDEXES/CREATE/QUERY/AGGREGATE/COUNT/DESCRIBE) — NOT RediSearch's FT.*; filters/aggregations are JSON strings. If you don't know the index name, run SEARCH.LISTINDEXES first; then SEARCH.DESCRIBE <index> for field names/types, and call redis_search_docs for syntax. Three gotchas: (1) a filter applies to ALL indexed documents unless you scope it, e.g. {"type":"story"} — an empty {} counts every type; (2) a plain text value like {"title":"x"} does fuzzy/smart matching, so for an exact word or adjacent phrase use {"title":{"$phrase":"x"}}; (3) add SELECT <n> field... to a query to return only the fields you need instead of whole documents.
| Name | Type | Req | Description |
|---|---|---|---|
| commands | array | yes | Redis commands; each is an array of args. Single: [["SET","foo","bar"]]. Multiple: [["SET","foo","bar"],["GET","foo"]]. Numbers are accepted and coerced to strings, so ["EXPIRE","k",60], ["ZADD","z",… |
| connection_string | string | — | Raw TCP credential override: rediss:// connection string. |
| rest_token | string | — | Raw HTTP credential override: Upstash REST token (must be paired with rest_url). |
| rest_url | string | — | Raw HTTP credential override: Upstash REST URL (must be paired with rest_token). |
| transaction | boolean | — | Run all commands in one MULTI/EXEC transaction (queued, executed together, no interleaving). Like standard Redis, a runtime error in one command does NOT roll back the others. Default false (pipeline… |
No output schema declared.
No examples provided.
redis_search_docs ~206
Look up **Upstash Redis** documentation — any command, feature, option, or syntax. Covers the whole Upstash Redis surface: core Redis commands, the REST API, pipelines/transactions, and Upstash-specific features. This INCLUDES Upstash Redis Search — the SEARCH.* full-text family (SEARCH.CREATE / SEARCH.QUERY / SEARCH.AGGREGATE / SEARCH.COUNT / ...), whose JSON-based index schema and query syntax are Upstash-specific and DIFFER from Redis Labs' RediSearch FT.*, so they are unlikely to be in your training data — verify them here. Reach for this whenever you're unsure about a command, option, or syntax, and ALWAYS before writing a SEARCH.* command. Pass a natural-language query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look up, in natural language, e.g. "SET with TTL and NX", "pipeline REST API", "ZADD options", "SEARCH.AGGREGATE date histogram", "define index schema". |
No output schema declared.
No examples provided.