Redis MCP Server

redis-mcp-server PyPI v0.5.1

Published by redis — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Redis MCP Server - Model Context Protocol server for Redis

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 53

Each tool and what it can reach — statically extracted from the published source.

  • read_messagesingests untrusted input
  • client_listno sensitive capability
  • create_vector_index_hashno sensitive capability
  • dbsizeno sensitive capability
  • deleteno sensitive capability
  • expireno sensitive capability
  • getno sensitive capability
  • get_index_infono sensitive capability
  • get_indexed_keys_numberno sensitive capability
  • get_indexesno sensitive capability
Show 43 more tools ↓
  • get_vector_from_hashno sensitive capability
  • hdelno sensitive capability
  • hexistsno sensitive capability
  • hgetno sensitive capability
  • hgetallno sensitive capability
  • hsetno sensitive capability
  • hybrid_searchno sensitive capability
  • infono sensitive capability
  • json_delno sensitive capability
  • json_getno sensitive capability
  • json_setno sensitive capability
  • llenno sensitive capability
  • lpopno sensitive capability
  • lpushno sensitive capability
  • lrangeno sensitive capability
  • lremno sensitive capability
  • psubscribeno sensitive capability
  • publishno sensitive capability
  • renameno sensitive capability
  • rpopno sensitive capability
  • rpushno sensitive capability
  • saddno sensitive capability
  • scan_all_keysno sensitive capability
  • scan_keysno sensitive capability
  • search_redis_documentsno sensitive capability
  • setno sensitive capability
  • set_vector_in_hashno sensitive capability
  • smembersno sensitive capability
  • sremno sensitive capability
  • subscribeno sensitive capability
  • typeno sensitive capability
  • unsubscribeno sensitive capability
  • vector_search_hashno sensitive capability
  • xackno sensitive capability
  • xaddno sensitive capability
  • xdelno sensitive capability
  • xgroup_createno sensitive capability
  • xgroup_destroyno sensitive capability
  • xrangeno sensitive capability
  • xreadgroupno sensitive capability
  • zaddno sensitive capability
  • zrangeno sensitive capability
  • zremno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.1 latest A 96/100 0 1.13.0 2026-08-25
v0.5.0 A 99/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/redis-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/redis-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/redis-mcp-server"><img src="https://mcptrustchecker.com/registry/redis-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/redis-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan redis-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Redis 9

Independent packages implementing the same tool, scanned with the same engine. Compare all 10 side by side →

More in Databases