redis-mcp-server@0.5.1
VERIFIED· not startedPublisher claims: "Redis MCP Server - Model Context Protocol server for Redis" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
REDIS_ENTRAID_AUTH_FLOWREDIS_ENTRAID_CLIENT_SECRETREDIS_ENTRAID_TOKEN_EXPIRATION_REFRESH_RATIOREDIS_ENTRAID_TOKEN_REQUEST_EXECUTION_TIMEOUT_MSor--entraid-auth-flow/--entraid-client-secret/--entraid-token-refresh-ratioConfiguration, not credentials: MCP_DOCS_SEARCH_URL, MCP_REDIS_LOG_LEVEL, REDIS_CLUSTER_MODE, REDIS_DB, REDIS_ENTRAID_CLIENT_ID, REDIS_ENTRAID_IDENTITY_TYPE, REDIS_ENTRAID_LOWER_REFRESH_BOUND_MILLIS, REDIS_ENTRAID_RESOURCE, REDIS_ENTRAID_RETRY_DELAY_MS, REDIS_ENTRAID_RETRY_MAX_ATTEMPTS, REDIS_ENTRAID_SCOPES, REDIS_ENTRAID_TENANT_ID, REDIS_ENTRAID_USER_ASSIGNED_CLIENT_ID, REDIS_HOST, REDIS_PORT, REDIS_PWD, REDIS_SSL, REDIS_SSL_CA_CERTS, REDIS_SSL_CA_PATH, REDIS_SSL_CERT_REQS, REDIS_SSL_CERTFILE, REDIS_SSL_KEYFILE, REDIS_USERNAME- Where it talks to
- redis.io (its own)Also azure.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names azure.com as well as its own vendor. The guard injects REDIS_ENTRAID_AUTH_FLOW, REDIS_ENTRAID_CLIENT_SECRET, REDIS_ENTRAID_TOKEN_EXPIRATION_REFRESH_RATIO, REDIS_ENTRAID_TOKEN_REQUEST_EXECUTION_TIMEOUT_MS only into requests to redis.io (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 95/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 4,129 lines in 26 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.