Limited view

81/100

2 months ago

Redis MCP Server

Item: Redis MCP Server
Rating: 81
Author: M8ven

The official Redis MCP Server is a natural language interface designed for agentic applications to manage and search data in Redis efficiently

→ redis/mcp-redis · listed on mcp_so

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

redis

Source: mcp.so · also listed on modelscope, github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

mcp.so modelscope GitHub mcp.so

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings

✅

No credential exfiltration, no sensitive file access, no obfuscation

Static analysis found nothing flowing your secrets to unexpected places.

✅

Open source with a license and README

Anyone can audit the code, the license is declared, and the publisher documents what it does.

🔐

You'll be asked for 1 credential: REDIS_ENTRAID_CLIENT_SECRET

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

configREDIS_HOST"": "<your_redis_database_hostname>",

configREDIS_PORT"": "<your_redis_database_port>",

configREDIS_USERNAME"-e", "=<redis_username>",

configREDIS_PWD"": "<your_redis_database_password>",

configREDIS_SSL"": TrueFalse,

configREDIS_SSL_CA_PATH"": "<your_redis_ca_path>",

configREDIS_SSL_KEYFILEClient's private key file for client authentication None

configREDIS_SSL_CERTFILEClient's certificate file for client authentication None

configREDIS_SSL_CERT_REQSWhether the client should verify the server's certificate "required"

configREDIS_SSL_CA_CERTSPath to the trusted CA certificates file None

configREDIS_CLUSTER_MODE"": TrueFalse

configREDIS_DBDatabase 0

configREDIS_ENTRAID_CLIENT_IDexport =your-client-id

🔐 secretREDIS_ENTRAID_CLIENT_SECRETexport =your-client-secret

configREDIS_ENTRAID_TENANT_IDexport =your-tenant-id

configREDIS_ENTRAID_SCOPESexport =https://redis.azure.com/.default

configREDIS_ENTRAID_RETRY_MAX_ATTEMPTS

configREDIS_ENTRAID_RETRY_DELAY_MS

configREDIS_ENTRAID_RESOURCEAzure Redis resource identifier "https://redis.azure.com/"

configMCP_REDIS_LOG_LEVELThe server uses Python's standard logging and is configured at startup. By default it logs at WARNING and above. You can change verbosity with the environment variable.

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

53/53 tools missing one or more hints — hset (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hget (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); hdel (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +50 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

50/53 tool handlers declare input schemas (94%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Your fixes are re-checked automatically. Claim the listing and we tell you when the grade moves, and reach you directly if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands.

// improvement guidance — verified publishers only

We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Score](https://m8ven.ai/badge/mcp/redis-mcp-redis-b69trg)](https://m8ven.ai/mcp/redis-mcp-redis-b69trg)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: 49920d7d0daf509e0fbc35d4a5a0e36909f3420e

code hash: 4504a1bdccb1c959bc4920ded2e3318fd12223ea388c86e8a50e5f1f77bb9ea3

verified: 6/16/2026, 12:20:59 PM

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client