Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldUpstash MCPShortlist candidateCodebase Memory MCPMCP100 Recommended
Task fit
Best for
  • Upstash Redis, QStash and Workflow diagnostics and administration
  • Use for Upstash resource operations rather than Context7 documentation.
  • Repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages
Not ideal for
  • Some tools can create/delete resources and interact with data; credentials may be sensitive.
  • Tiny repositories, one-off text searches, or semantic questions unsupported by the indexed parsers
Avoid when
  • Some tools can create/delete resources and interact with data; credentials may be sensitive.
  • The source tree cannot be indexed locally or persistent cache files are prohibited
Provenance
Provenance details

First-party MCP

Upstash · Publisher source ↗

First-party MCP

DeusData · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Aug 14, 2026

Popularity evidence
GitHub stars

60

GitHub stars · checked 2026-10-20

44,904

GitHub stars · checked 2026-09-25T18:35:00Z

Package downloads / 30 days

7,264

package downloads / 30 days · checked 2026-10-20

28,000

package downloads / 30 days · checked 2026-08-14T00:00:00.000Z

External adoption evidenceNot documented
  • npm: package downloads: 28,015Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage detailsNot documented
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationThe local package uses Upstash account email plus an API key. Read-only API keys are supported. Upstash also documents hosted/remote connection paths in the current product ecosystem.local stdio; no remote auth needed
CostNo separate MCP fee is documented. Underlying Upstash services have their own free/paid usage models; the MCP also exposes a temporary free Redis database workflow that expires after 72 hours if not claimed.none beyond local resources
PermissionsWith a read-only API key, state-modifying tools are disabled while read/query tools remain available.reads indexed source/project data; installer writes supported agent/editor configs/hooks
Data handlingThe server sends anonymous diagnostic information such as SDK/runtime/OS details with requests, but Upstash states it does not collect account data, tool arguments, or tool results through this telemetry. Telemetry can be disabled.local processing; current docs state no source/index/query/env/telemetry upload
Limitations
Tradeoffs
  • Read-only key hides mutating tools; Box uses separate credentials
  • Persistent indexing can reduce repeated reads, but consumes local storage and graph results can become stale until the repository is re-indexed.
  • Version 0.10.8 includes correctness and reliability fixes affecting graph/search results and Windows behavior.
Risk contextFull-access credentials can create/delete resources and interact with stored data. The read-only credential mode materially reduces mutation risk.latest 0.10.x supported; SLSA/Sigstore/checksums/VirusTotal/security policy
Evidence date
Editorial review2026-10-192026-09-23
Candidate evidence2026-10-192026-09-25T18:35:00Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →