Think inside your AI world.

Redis through Unl

Redis's MCP server will read back a key's value and exactly how long it has left to live. Whether that lifetime is one you would sign off on is a different question - a key that still resolves isn't the same as a key that should still exist.

Redis through Unl reads a key's value and its live expiration against the session-lifetime ceiling you have ratified, so 'should this session token still be valid?' comes back set-or-short with the condition it hasn't met.

What Redis holds

Redis's MCP server, read against a key, returns:

  • key values with their live time-to-live
  • hash, list, set, and sorted-set contents
  • JSON document contents via path-based access
  • stream entries and consumer-group state
  • database information and statistics from server management tools

What the naked read gives you

Redis's MCP server fetches the key, the hash, the sorted set, the JSON document - and, for strings, the time-to-live sitting alongside the value. It reads out exactly what is stored and for how much longer it will last, leaving the question of whether that lifetime is appropriate entirely open.

The frame judges the data it is given; it does not verify the source’s accuracy.

What changes when Redis is read measured

A platform engineer at a subscription app ratified a session rule in Unl: no authentication token key may carry a time-to-live longer than twenty-four hours, because a support incident once traced a fraudulent login back to a session token that had silently lived for a fortnight.

'Should this session token still be valid?' returns, measured: no - the key read shows session:usr_4471 with a TTL of six days and eleven hours remaining, well past the twenty-four-hour ceiling. Redis supplied the live expiration; your ratified rule supplied the ceiling.

And back again

Reissue the token with the correct expiry; Redis through Unl sees the shortened TTL the next time it looks, and the ratified ceiling reads the session as sound - nothing new gets created, this page just shifts.

The answer comes back measured against what you already decided, and why.

The lane is live and open to this tool today: one box, paste anything. If it speaks MCP, Unl can reach it. Readings arrive unprompted, the data beside the criterion; Unl is a courier, not a warehouse, and keeps only your keys and the frame.

Questions people ask

What would flip this token back to valid?

Reissuing the session key with a TTL under twenty-four hours, or letting the old key expire outright. The same ratified ceiling reads the new TTL and clears the token.

How do I connect Redis to Claude?

Run the official Redis MCP server (redis/mcp-redis) against your Redis instance or Redis Cloud endpoint, then register it in Claude's MCP configuration with the connection URL - Unl's reads follow whatever that server exposes.

Does Unl write to my database?

No. Unl calls Redis's get-style read tools to see key values and TTLs; it does not set, expire, or delete keys. Any token reissue, you run yourself.

What this is

Think inside your AI world — you stay in command

Unlimitless (Unl to friends) holds what you've settled, reads what your tools are showing, and catches what's changed out in the world — and hands your AI whatever bears on the work, the moment it's needed, without you asking. The right thing, in front of the model, unprompted, with you in command of the call. So you keep moving toward what you set out to build, on top of everything you've already decided.

It plugs into Claude, Claude Code, ChatGPT and Cursor as an MCP connector. Quick to connect, in a couple of steps.

Unlimitless is open now to invited Alpha. Apply for the Beta waitlist to come in ahead of the full launch:

Alpha is invite-only · free at launch.