mcp-redis-cloud
The Redis Cloud API MCP Server provides an MCP Server for Redis Cloud's API, allowing you to manage your Redis Cloud resources using natural language.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
redis
Source: ModelScope
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 →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get-current-accountGet the current Cloud Redis account
get-current-payment-methodsGet the current payment methods for the current Cloud Redis account
get-database-modulesLookup list of database modules supported in current account (support may differ based on subscription and database settings). These modules are also called capabilities.
get-pro-plans-regionsLookup list of regions for cloud provider. These regions include the providers too.
create-pro-subscriptionCreate a new pro subscription. Returns a TASK ID that can be used to track the status of the subscription creation. Prerequisites: 1) Verify payment method by checking get-current-payment-methods. 2) For database modules, validate against get-database-modules list. 3) Validate regions using get-pro-…
get-pro-subscriptionsGet the pro subscriptions for the current Cloud Redis account
get-pro-subscriptionGet pro subscription by ID. The payload must match the input schema.
get-essential-subscriptionsGet the essential subscriptions for the current Cloud Redis account. A paginated response is returned, and to get all the essential subscriptions, the page and size parameters must be used until all the essential subscriptions are retrieved.
get-essential-subscription-by-idGet an essential subscription by ID for the current Cloud Redis account
create-essential-subscriptionCreate a new essential subscription. Returns a TASK ID that can be used to track the status of the subscription creation
delete-essential-subscriptionDelete an essential subscription by ID
get-essentials-plansGet the available plans for essential subscriptions. Always ask for which provider the plans are want to be retrieved. A paginated response is returned, and to get all the plans, the page and size parameters must be used until all the plans are retrieved.
get-tasksGet the current tasks for the current Cloud Redis account
get-task-by-idGet a task by ID for the current Cloud Redis account
get-pro-databasesGet the pro databases for the provided subscription Id
create-pro-databaseCreate a new database inside the specified subscription ID. Returns a TASK ID that can be used to track the status of the database creationPrerequisites: 1) For database modules, validate against get-database-modules list. 2) Validate regions using get-pro-plans-regions. The payload must match the i…
get-essential-databasesGet the essential databases for the provided subscription Id
create-essential-databaseCreate a new essential database inside the specified subscription ID. Returns a TASK ID that can be used to track the status of the database creation. IMPORTANT GUIDELINES: 1) DO NOT set optional parameters unless explicitly requested. 2) Modules can only be selected if protocol is 'redis'. 3) When …
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
When Vitest UI server is listening, arbitrary file can be read and executed
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
vite: `server.fs.deny` bypass on Windows alternate paths
Vite has an `server.fs.deny` bypass with an invalid `request-target`
API_KEYEnsure that the required environment variables (, SECRET_KEY) are set correctly.BASE_URLSECRET_KEYEnsure that the required environment variables (API_KEY, ) are set correctly.Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 2 high severity in production deps — @modelcontextprotocol/sdk@1.8.0 (high), @modelcontextprotocol/sdk@1.8.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dev dependencies
2 critical/high in dev-only deps (does not ship to users)
Upgrade dev dependencies when convenient.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/redis/mcp-redis-cloud)?variant=verified from the URL.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