Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/upstash/redis-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/upstash/redis-mcp/redis-mcp)<a href="https://agentmods.dev/mcp/upstash/redis-mcp/redis-mcp"><img src="https://agentmods.dev/badge/mcp/upstash/redis-mcp/redis-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/upstash/redis-mcp/redis-mcp"><img src="https://agentmods.dev/badge/mcp/upstash/redis-mcp/redis-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
redis-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"redis-mcp": {
"command": "npx",
"args": [
"-y",
"@upstash/redis-mcp"
],
"env": {
"UPSTASH_REDIS_REST_URL": "",
"UPSTASH_REDIS_REST_TOKEN": "",
"UPSTASH_REDIS_TCP_URL": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 14 lines scan A 9be93f007372
redis-mcp is an MCP server published in the GitHub repository upstash/redis-mcp (0 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
acmi-mcp
Persistent agent memory via ACMI — Profile/Signals/Timeline. 16 tools on Upstash Redis. Runs locally from the @madezmedia/acmi-mcp npm package. Needs 2 environment variables to run.
queue-aiops
Governed AI-ops for redis + rabbitmq: memory-pressure/latency/queue-backlog/connection-churn RCAs, slowlog and SCAN-budgeted big-key sampling, queues/policies/nodes, and governed writes (config set, client kill, purge/delete queue, policies) with a built-in governance harness (audit, budget, undo, risk tiers). Runs…
wredis-mcp
MCP Server for WRedis Architecting. Runs locally from the wredis-mcp Python package.
redis-channel
MCP server "redis-channel" as configured in infiquetra/infiquetra-claude-plugins. Launched with /bin/sh -c cd "$CLAUDE_PLUGIN_ROOT" || exit 1; if [ -r "$HOME/.claude/channels/r.
qdrant
MCP server for retrieving context from a Qdrant vector database. Runs locally from the mcp-server-qdrant Python package. Needs 3 environment variables to run.
mcp-java-backend-suite
Complete MCP suite for Java backend developers — database analysis, JVM diagnostics, migration risk, Spring Boot actuator analysis, and Redis diagnostics. Runs locally from the mcp-java-backend-suite npm package.