RedisNexus (rajkumar-madhu/mcp) is an MCP server listed on the M8ven Trust Index. It scores 39 out of 100, grade F. It declares 169 tools. No publisher has claimed this listing.

F
Warning
39/100

RedisNexus

RedisNexus is an AI-powered operations intelligence platform that provides 16 enterprise-grade tools for managing Redis data, health monitoring, and cache strategy. It enables AI assistants to perform secure, multi-tenant Redis operations and real-time intelligence analysis within production-ready Kubernetes environments.

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

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

rajkumar-madhu

Source: Glama

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 →

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.

// key findings
⚠️
Tool annotations don’t match behaviour
1 read-only tool performs write/delete/exec — nginx_test_config (line 211: os.unlink(f.name))
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 6 credentials: RABBITMQ_PASS, ARGOCD_AUTH_TOKEN, JIRA_API_TOKEN, VAULT_TOKEN, NEXUS_API_KEY, NEXUS_JWT_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.
configRABBITMQ_HOST
configRABBITMQ_MANAGEMENT_PORT
configRABBITMQ_USER
🔐 secretRABBITMQ_PASS
configMCP_PORT
configARGOCD_SERVER
🔐 secretARGOCD_AUTH_TOKEN
configAWS_DEFAULT_REGION
configAZURE_RESOURCE_GROUP
configAZURE_SUBSCRIPTION_ID
configELASTICSEARCH_URL
configGCP_PROJECT
configGCP_REGION
configGITHUB_REPO
configGITLAB_REPO
configJIRA_URL
configJIRA_EMAIL
🔐 secretJIRA_API_TOKEN
configNGINX_CONF_DIR
configPROMETHEUS_URL
configVAULT_ADDR
🔐 secretVAULT_TOKEN
🔐 secretNEXUS_API_KEY
configNEXUS_CORS_ORIGINS
configNEXUS_PUBLIC_DOMAIN
🔐 secretNEXUS_JWT_SECRET
configNEXUS_DB_PATH
configNEXUS_ALLOW_SIGNUP
configNEXUS_BASE_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployREDIS_URL
deployMONGO_URI
deployDATABASE_URL
// quality suggestions

Tool annotations match behaviour

1 read-only tool performs write/delete/exec — nginx_test_config (line 211: os.unlink(f.name))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — nginx_test_config deletes at line 211 (os.unlink(f.name))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool handlers catch errors

156/169 tool handlers wrap calls in try/catch (92%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

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.

// 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. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 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 Verified](https://m8ven.ai/badge/mcp/rajkumar-madhu/mcp?variant=verified)](https://m8ven.ai/mcp/rajkumar-madhu/mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 0cbfb5024463b119f5bcbd1127455d8687d8dcc2
code hash: 90b616e43edab5e8bf2292056c34a9b150372c53eaee0aa3f3758e5492bdcdd2
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