io.github.upstash/redis-mcp
NPM · @UPSTASH/REDIS-MCP
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.
Available components
Last scanned (7 hours ago)
Scores higher than 92% of npm servers
Category Databases
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 → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 97 dependencies flagged as unhealthy. 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 120 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.90 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 20 Oct 26 0
- Stability: pass → 0.97 functional
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 6 Nov 2026 · Analysed npm/@upstash/redis-mcp@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| 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 | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0f06e20f937ff648e3832d86841793b6686419f05e1a7aa431f36c6ebb2faa8c0fb087f2f3eb24213b2caef013ae2cd36115fe0af17a61b8ee38a59f0 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
How do I install the io.github.upstash/redis-mcp server?
io.github.upstash/redis-mcp runs locally as an npm package, launched with npx -y @upstash/redis-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @upstash/redis-mcp
claude mcp add upstash-redis-mcp -- npx -y @upstash/redis-mcp
What is the io.github.upstash/redis-mcp server?
io.github.upstash/redis-mcp is listed in the public MCP registry as io.github.upstash/redis-mcp. Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP. This page covers its npm package (@upstash/redis-mcp).
Is the io.github.upstash/redis-mcp server safe to use?
io.github.upstash/redis-mcp scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.upstash/redis-mcp server expose?
io.github.upstash/redis-mcp exposes 2 tools: redis_run_commands, redis_search_docs. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.
Is the io.github.upstash/redis-mcp server still maintained?
io.github.upstash/redis-mcp is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.upstash/redis-mcp server under?
io.github.upstash/redis-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.upstash/redis-mcp server?
VerifyMCP ran 15 checks on io.github.upstash/redis-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.upstash/redis-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.