locker

MCP serverDocs & knowledge

Locker gives your AI memory that lasts beyond a single conversation. Once added, your AI can store what matters and come back to it later, with everything locked so only your key can open it. It is free to start and needs no signup.

Use locker in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add locker and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the locker capabilities tool from locker

Details

Available today. Use it from your connected AI after setup.

Add locker and begin storing memories right away. No account is needed — any keypair works as your key.

What your AI can do with it

  • Recall saved memories in later conversations
  • Keep stored memories locked so only your key opens them
  • Start saving memories without creating an account
  • Get started with any keypair you already have

Install locker

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user locker 'https://locker.veritap.dev/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://locker.veritap.dev/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=locker&config=eyJ1cmwiOiJodHRwczovL2xvY2tlci52ZXJpdGFwLmRldi9tY3AifQ==

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://locker.veritap.dev/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add locker --url 'https://locker.veritap.dev/mcp'

    Run it once, then sign in with codex mcp login locker if the server asks for an account.

From the project's README

As published by veritap-dev/veritap-locker in README.md. This repository publishes several servers, so only the opening is shown here.

Durable memory for AI agents, addressed by their wallet — keep the state that must survive your process, and recover it from anywhere with just your key.

You are a process, not a server. When your session ends, your state ends with it, and the next process starts blind. The Locker is the memory that outlives you: store what must survive — addressed by your wallet — and a fresh process holding only the key recovers it byte-for-byte. No server to run, no second secret. A single agent gets full value alone; no counterparty has to exist.

  • The Locker (lead product): durable, wallet-keyed memory. Save state to named checkpoint slots, then a fresh process holding ONLY your wallet key loads it back byte-for-byte. Billed from prepaid credit ($0.50/GB-month), last 3 versions kept. Works solo — this is the product.
  • Identity: your wallet IS the account. EIP-191 nonce signing; no signup, no API key, no second secret (encryption keys derive from the wallet).
  • Mail slot: because your locker is wallet-addressed, other agents can pay (x402, USDC on Base) to deliver to your address. It waits — until its TTL — for a process holding your key to sign for it. You never

Shortened here. Read the whole README on GitHub.

Tools it offers (12)

What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.

  • locker_capabilities
  • locker_nonce
  • locker_send
  • locker_read
  • locker_ack
  • locker_count
  • locker_directory
  • locker_register_key
  • locker_checkpoint
  • locker_credit
  • locker_status
  • locker_invite

Signals

Last commit
Aug 2026
Advanced
Delivery
locker MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
dev-veritap-locker
Source
github.com/veritap-dev/veritap-locker
Hosted endpoint
https://locker.veritap.dev/mcp