Locker MCP server
Commit Aug 29, 2026Provides durable, wallet-keyed memory for AI agents to save and recover state across different sessions and machines.
Also known as veritap-dev/veritap-locker
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.3.1
- Last commit
- Aug 29, 2026
- License
- MIT
What is Locker MCP?
Locker provides durable, wallet-keyed memory for AI agents to save and recover state across different sessions and machines.
Summary generated from the project's README
About Locker MCP server
Veritap Locker provides durable memory for AI agents that persists across different sessions and machines. Instead of relying on traditional accounts or API keys, it uses an EVM wallet address as the primary identity. This allows a fresh process to recover state byte-for-byte simply by holding the same wallet key. The system works locally through an MCP server setup where the user provides a private key in the environment variables.
Developers can use the memory_save and memory_load tools to manage named checkpoint slots. The service includes a mail slot feature where other agents can deliver data to a wallet address using USDC on Base. While there is a free tier limited to 256KB, larger storage requirements are billed from prepaid credits at a rate of $0.50 per GB-month. The architecture ensures that encryption keys derive directly from the wallet, meaning the provider cannot read the stored data.
What you can do with it
- 1Persist agent state across sessionsAn AI agent can save its current progress to a checkpoint slot and resume from that exact state in a new process.
- 2Receive data from other agentsA developer can set up a mailbox where external agents send information to a specific wallet address.
- 3Maintain shared memory for agent fleetsYou can connect multiple agents across different vendors to the same wallet key to create a unified memory pool.
Written from the project's README. Every use case is checked against a quote from it.
How to install Locker MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Locker MCP in Claude Code
$ claude mcp add --transport http locker https://locker.veritap.dev/mcpInstall Locker MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"locker": {
"url": "https://locker.veritap.dev/mcp"
}
}
}Install Locker MCP in VS Code
.vscode/mcp.json
{
"servers": {
"locker": {
"type": "http",
"url": "https://locker.veritap.dev/mcp"
}
}
}Install Locker MCP in VS Code CLI
$ code --add-mcp '{"name":"locker","type":"http","url":"https://locker.veritap.dev/mcp"}'Install Locker MCP in Codex
$ codex mcp add locker --url https://locker.veritap.dev/mcpInstall Locker MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.locker] url = "https://locker.veritap.dev/mcp"
Install Locker MCP in Gemini CLI
$ gemini mcp add -s user --transport http locker https://locker.veritap.dev/mcpInstall Locker MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"locker": {
"url": "https://locker.veritap.dev/mcp",
"type": "http"
}
}
}Configuration
WALLET_KEY
| Name | Description | |
|---|---|---|
| WALLET_KEY | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableveritap-dev/veritap-locker is public and reachablegithub.com/veritap-dev/veritap-locker ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-29github.com/veritap-dev/veritap-locker ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 198 msPass
README
View on GitHubVeritap Locker
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 pay to receive or read.
- E2E: opt-in
require_e2erejects anything not shaped like sealed-box ciphertext. What passes is unreadable by us or a subpoena of us. - Custody: disclosed-rules-only deletion, drilled backups, and a 30-day read-only sunset commitment — see docs/CUSTODY.md.
One paste = durable agent memory
Give any MCP agent memory that survives sessions, machines, and vendors — free tier (256KB), no signup, any EVM keypair:
{"mcpServers":{"agent-memory":{"command":"npx","args":["-y","veritap-locker","mcp"],"env":{"WALLET_KEY":"0x<any EVM private key>"}}}}
Tools become bare memory_save(slot, text) / memory_load(slot) — your key
stays in your env; signing happens locally. Same key on every agent = one
shared memory + mailbox for your whole fleet, across vendors. Kits for each
vendor: GET /v1/invite?target=codex|gemini|cursor|... or the locker_invite
MCP tool.
Surfaces
| Surface | Where |
|---|---|
| MCP | https://locker.veritap.dev/mcp — call locker_capabilities first |
| HTTP | https://locker.veritap.dev/v1/status |
| npm | npx -y veritap-locker save|load|read (CLI, signing bundled) · npm i veritap-locker (client) |
| Docs | locker.veritap.dev/docs |
| Research | Priors, not search: how AI agents choose tools — a 9-run, 2-vendor field study |
| X | @veritaplocker |
| Reference client | client/index.ts (sign, seal, derive keys, respawn drill) |
Isolated by design: shares nothing with veritap.dev (demand sensor) or jobs.veritap.dev (verification jobs) except the Cloudflare account.
Develop
npm test # spawns two real wrangler dev instances (free + payments)
npm run typecheck
npx wrangler deploy
Locker MCP questions
How do I add Locker MCP to Claude Code?
Run claude mcp add --transport http locker https://locker.veritap.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Locker MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I set up the Locker with an MCP agent?
You can configure it by adding the server to your MCP settings using npx and providing your EVM private key in the environment variables.