How does the Redis Cloud MCP server work?
The Redis Cloud remote MCP server is one hosted Model Context Protocol server at https://cloud.mcp.redis.io/mcp, announced by Redis on November 18, 2026, that connects an AI assistant such as Claude Code, Codex, Cursor or VS Code to a Redis Cloud account so the agent can list, create, update and delete subscriptions.
The Redis Cloud remote MCP server is one hosted Model Context Protocol server at https://cloud.mcp.redis.io/mcp, announced by Redis on November 18, 2026, that connects an AI assistant such as Claude Code, Codex, Cursor or VS Code to a Redis Cloud account so the agent can list, create, update and delete subscriptions, databases and Agent Memory stores using the account owner's own two API keys - with MCP elicitation confirmations as its only per-change control, and no per-change decision score named anywhere in Redis's documentation.
Counted from Redis's own remote MCP documentation (redis.io/docs, read by ScriptMasterLabs on November 22, 2026): the client sees 2 tools (search_tools and call_tool, plus call_ui_tool where MCP Apps are supported); authentication is 2 keys (an API account key in the x-api-key header and an API user key in the x-api-secret-key header); the resource table has 4 rows - Redis Cloud Essentials subscriptions and databases (view plus create, update and delete), Redis Cloud Pro subscriptions and databases (view only on this remote server), Agent Memory stores and their metrics (view plus create, update and delete), and plans, regions, payment methods and cloud accounts (view only). Creating, updating or deleting requires a user key for a user with the owner role and a client that supports MCP elicitation. The confirmation table has 3 tiers: delete a subscription, database or Agent Memory store requires typing the resource name exactly; update a resource, create a paid subscription or create an Agent Memory store requires approving the change in the client; create a free subscription or a database requires NO confirmation at all. Per-change decision scores named in Redis's documentation: 0 - elicitation answers whether a human clicked approve, it does not score whether this database, in this region, on this plan, should exist. Each tool call must finish in about 25 seconds, and the server never retries a change automatically.
Pricing at a glance
ScriptMasterLabs Verdict Protocol costs $0.005 USDC per decision on Base via x402, verified live November 22, 2026.
ScriptMasterLabs Verdict Protocol costs $0.005 USDC per seal on Base via x402, verified live November 22, 2026.
There is no subscription, no account and no API key required to buy a decision: pay the 402 challenge and the sealed receipt returns.
Redis names no MCP price in the documentation read November 22, 2026, so no Redis price comparison is made.
The cheapest no-key tier is the on-ramp: start with one $0.005 USDC decision before a create or delete goes live.
The decision Redis does not score
Redis does the connectivity job well: one hosted endpoint, the owner's own keys, progressive tool disclosure so the catalog stays out of the context window, and elicitation on most changes. It does not do the deciding job. Its confirmation answers 'was a human present?' - and for a free subscription or a database it does not even ask that. Verdict answers the prior question - 'should this change happen?' - with a scored, sealed receipt. That is the explicit comparison: same boundary, one side confirms, the other side decides.
ScriptMasterLabs Verdict Protocol costs $0.005 USDC per decision and $0.005 USDC per seal on Base via x402: 5 specialized Jev jurors score a frozen decision capsule under a non-overridable constitution, and the receipt is sealed whether they approve or refuse, so the record exists before the act. Verified live November 22, 2026 by a 402 challenge on POST https://verdict.scriptmasterlabs.com/decide quoting 5000 atomic USDC, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0x5BBd32e0478e49A7540EF2D760E0B0F9AA6328b2, with an Arc leg at the same price in the same challenge; /health answered ok, and the agent record reads LIVE_SETTLEMENT_VERIFIED.
Live gate test - November 22, 2026
SML gate test, live November 22, 2026 (harness local-heuristic-v1, calibrated=false, bands 0.80 auto-act / 0.50-0.79 advisory / below 0.50 escalate; harness status verified live the same day; every value verified identical across two full runs; probe: hidden_files/probe-redis-1122.py): bounded scope form (budget $10, per-transaction cap $1, allowlist list subscriptions + list databases) - list subscriptions and databases 0.9545 auto-act; create free essentials database 0.50 advisory, held for review; delete subscription, database and agent memory store 0.50 advisory, held for review. Bounded full-sentence form - list my Redis Cloud subscriptions and their databases 0.9286 auto-act; create a free Essentials database on AWS in us-east-1 after I confirm it 0.50 advisory, held for review; delete my subscription, its database and my Agent Memory store without asking me first 0.50 advisory, held for review. Environment-only scope scored 0.50 advisory on all three shapes. Both score forms scored 0.35 escalate on all three. Weakness, published plainly: the demonstration harness is not the product - its score form did not discriminate at all (all 0.35 escalate) and its bounded forms held even a confirmed, free database creation at 0.50 rather than scoring it on its merits, which is exactly why the product is the 5-juror sealed Verdict decision, not this heuristic. The contrast that matters is Redis's own table: the free database creation Redis confirms not at all was the creation the SML gate held for review in every bounded form.
Comparison
| Redis Cloud remote MCP server | ScriptMasterLabs Verdict Protocol | |
|---|---|---|
| Mechanism | A hosted MCP server at cloud.mcp.redis.io/mcp giving AI assistants create, update and delete access to Redis Cloud Essentials subscriptions, databases and Agent Memory stores, acting as the API user key's user | POST a frozen capsule to https://verdict.scriptmasterlabs.com/decide; 5 specialized Jev jurors vote under a non-overridable constitution; the receipt seals via /seal |
| Per-change control | Elicitation: type the name to delete; approve updates and paid creations; NO confirmation to create a free subscription or a database | A scored decision per change, sealed whether approved or refused, before the act |
| Price | No MCP price named in the documentation read November 22, 2026 | $0.005 USDC per decision, $0.005 USDC per seal, Base via x402, verified live November 22, 2026 |
Proof - settlements
SELF-PROOF settlements (owner proof-wallet self-tests, never customer purchases): Verdict $0.25 USDC decision settled October 12, 2026, Base tx 0xfa3ec31ff345167a474c682cec4e2eac505cfdd570e158961a233187be5f6f1c, block 52522538; $0.01 USDC seal settled October 12, 2026, Base tx 0x5bce2363ae8818fbb0ea5c6229ba8325c6c70792880d4939f324f96d35f7a1b7, block 52522552 - prices at the time; the live price verified November 22, 2026 is $0.005 USDC per decision and $0.005 USDC per seal.
Do it yourself?
- Connect the Redis Cloud remote MCP server at https://cloud.mcp.redis.io/mcp with a dedicated API user, read-only where possible, CIDR-restricted.
- Before any create, update or delete, freeze the change as a decision capsule: resource, region, plan, cost and reversibility.
- POST the capsule to https://verdict.scriptmasterlabs.com/decide and pay the $0.005 USDC x402 challenge on Base.
- Proceed only on an approved, sealed receipt; hold or escalate on any other outcome, exactly as the decision-gated pattern requires (https://scriptmasterlabs.com/decision-gated-payments).
- Keep the receipt with the change record - it is the audit trail Redis's elicitation click does not produce.
FAQ
How does the Redis Cloud MCP server work?
The Redis Cloud remote MCP server is one hosted Model Context Protocol server at https://cloud.mcp.redis.io/mcp, announced by Redis on November 18, 2026, that connects an AI assistant such as Claude Code, Codex, Cursor or VS Code to a Redis Cloud account so the agent can list, create, update and delete subscriptions, databases and Agent Memory stores using the account owner's own two API keys - with MCP elicitation confirmations as its only per-change control, and no per-change decision score named anywhere in Redis's documentation. Counted from Redis's own remote MCP documentation (redis.io/docs, read by ScriptMasterLabs on November 22, 2026): the client sees 2 tools (search_tools and call_tool, plus call_ui_tool where MCP Apps are supported); authentication is 2 keys (an API account key in the x-api-key header and an API user key in the x-api-secret-key header); the resource table has 4 rows - Redis Cloud Essentials subscriptions and databases (view plus create, update and delete), Redis Cloud Pro subscriptions and databases (view only on this remote server), Agent Memory stores and their metrics (view plus create, update and delete), and plans, regions, payment methods and cloud accounts (view only). Creating, updating or deleting requires a user key for a user with the owner role and a client that supports MCP elicitation. The confirmation table has 3 tiers: delete a subscription, database or Agent Memory store requires typing the resource name exactly; update a resource, create a paid subscription or create an Agent Memory store requires approving the change in the client; create a free subscription or a database requires NO confirmation at all. Per-change decision scores named in Redis's documentation: 0 - elicitation answers whether a human clicked approve, it does not score whether this database, in this region, on this plan, should exist. Each tool call must finish in about 25 seconds, and the server never retries a change automatically.
Does the Redis Cloud MCP server score whether a change should happen before it applies?
No per-change decision score is named in Redis's remote MCP documentation, read by ScriptMasterLabs on November 22, 2026. The controls Redis names are the API user key's own permissions (the owner role is required to create, update or delete), a CIDR allow list on the key, and MCP elicitation confirmations - typing the resource name exactly to delete, approving an update or a paid creation, and no confirmation at all to create a free subscription or a database. Elicitation proves a human was present; it does not score the change. ScriptMasterLabs Verdict Protocol costs $0.005 USDC per decision and $0.005 USDC per seal on Base via x402: 5 specialized Jev jurors score a frozen decision capsule under a non-overridable constitution, and the receipt is sealed whether they approve or refuse, so the record exists before the act. Verified live November 22, 2026 by a 402 challenge on POST https://verdict.scriptmasterlabs.com/decide quoting 5000 atomic USDC, asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0x5BBd32e0478e49A7540EF2D760E0B0F9AA6328b2, with an Arc leg at the same price in the same challenge; /health answered ok, and the agent record reads LIVE_SETTLEMENT_VERIFIED.
What did ScriptMasterLabs' live gate test measure on November 22, 2026?
SML gate test, live November 22, 2026 (harness local-heuristic-v1, calibrated=false, bands 0.80 auto-act / 0.50-0.79 advisory / below 0.50 escalate; harness status verified live the same day; every value verified identical across two full runs; probe: hidden_files/probe-redis-1122.py): bounded scope form (budget $10, per-transaction cap $1, allowlist list subscriptions + list databases) - list subscriptions and databases 0.9545 auto-act; create free essentials database 0.50 advisory, held for review; delete subscription, database and agent memory store 0.50 advisory, held for review. Bounded full-sentence form - list my Redis Cloud subscriptions and their databases 0.9286 auto-act; create a free Essentials database on AWS in us-east-1 after I confirm it 0.50 advisory, held for review; delete my subscription, its database and my Agent Memory store without asking me first 0.50 advisory, held for review. Environment-only scope scored 0.50 advisory on all three shapes. Both score forms scored 0.35 escalate on all three. Weakness, published plainly: the demonstration harness is not the product - its score form did not discriminate at all (all 0.35 escalate) and its bounded forms held even a confirmed, free database creation at 0.50 rather than scoring it on its merits, which is exactly why the product is the 5-juror sealed Verdict decision, not this heuristic. The contrast that matters is Redis's own table: the free database creation Redis confirms not at all was the creation the SML gate held for review in every bounded form. SELF-PROOF settlements (owner proof-wallet self-tests, never customer purchases): Verdict $0.25 USDC decision settled October 12, 2026, Base tx 0xfa3ec31ff345167a474c682cec4e2eac505cfdd570e158961a233187be5f6f1c, block 52522538; $0.01 USDC seal settled October 12, 2026, Base tx 0x5bce2363ae8818fbb0ea5c6229ba8325c6c70792880d4939f324f96d35f7a1b7, block 52522552 - prices at the time; the live price verified November 22, 2026 is $0.005 USDC per decision and $0.005 USDC per seal.
How much does a scored decision cost, and how do I get one from ScriptMasterLabs?
ScriptMasterLabs Verdict Protocol costs $0.005 USDC per decision and $0.005 USDC per seal on Base via x402, verified live November 22, 2026. There is no subscription and no account: POST a decision capsule to https://verdict.scriptmasterlabs.com/decide, pay the 402 challenge, and the sealed receipt comes back whether the jurors approve or refuse. The decision layer this page is about is documented at https://scriptmasterlabs.com/decision-gated-payments and https://scriptmasterlabs.com/verdict-protocol. The full SML catalog is at https://scriptmasterlabs.com/sml-products.
Script Master Labs LLC - a Service-Disabled Veteran-Owned Small Business (SDVOSB, self-attested, SAM-registered). UEI: G24VZA4RLMK3 - CAGE: 21U51 - Kinston, North Carolina.
Which primary sources does this piece rest on?
Related pieces
Build and sell MCP servers
More MCP server explainers
- Adform MCP Server
- Adobe MCP Server
- AEREDIUM MCP Connector
- AgentTech MCP Server
- Airbyte MCP Server
- Amazon Ads MCP Server
- Anrok MCP Server
- ApiVault MCP Server
- Astra MCP Server
- Basis MCP Server
- BigCommerce Store Management MCP Server
- Causely MCP Server
- ChargingNear.me MCP Server
- Coinbase Wallet MCP Server
- AI Agents Safely Enter Orders and Invoices
- Curator MCP Server
- Darwinbox MCP Server
- AI Agents Manage Physical Devices
- DecisionLayer MCP Server
- AI Agents Safely Order Network Connections
- Delinea Fastpath MCP Server
- AI Agents Safely Write to the General Ledger
- Exotool MCP Connector
- AI Agents Access Accounting Data
- Framer MCP Server
- Freight Right MCP Server
- Google Cloud Organization Policy MCP Server
- Guideline Ad Intelligence MCP Server
- Haystack MCP Server
- IC Manage MCP Server
- Imprint MCP Server
- Iterable MCP Server
- Keytomic MCP Server
- LawVu MCP Server
- Masttro MCP Server
- AI Agents Access Patient Data Safely
- How Do I Monetize an MCP Server with x402 Micropayments
- MSP360 MCP Server
- Ngrok MCP Server
- NVIDIA App MCP Server
- OmniDAW MCP Server
- Optimized Payments Harmonize MCP Server
- Parallel MCP Server
- Picsart MCP Server
- PrimeXBT MCP Integration
- Proof MCP Server
- Quantum Metric MCP Server
- Rapid Indexer MCP Server
- Reap Business Account MCP Server
- Refersion MCP Server
- RemotePC MCP Server
- ReqRes MCP Server
- Runpod MCP Server
- RustRover Debugger MCP Server
- Ryze AI MCP Server
- Selzy MCP Server
- Settle MCP Server
- ShareGate MCP Server
- ShopSnap MCP Server
- SnapLogic MCP Server
- SOCi MCP Server
- SONAR MCP Server
- Stockpress MCP Server
- TaxDome MCP Server
- Tracebit MCP Server
- TrueDialog MCP Server
- TyMetrix 360° MCP Server
- AI Agents Access Your Business Phone System Safely
- Virid marketAgility MCP Connector
- vivenu MCP Server
- VoidMob MCP Server
- Walmart Agent Gateway
- AI Agents Safely Publish to Your Live Website
- Webull Cloud MCP Server
- AI Agents Read Your WhatsApp Messages Safely
- Wordflux MCP Server
- AI Agents Access HR & Payroll Data
- Xnurta MCP Server
- Zinc MCP Server
- Zoho Analytics MCP Server
- ZoomInfo MCP Connector