Veritap Locker MCP server
Commit Aug 29, 2026Provides durable, wallet-keyed memory for AI agents to store and recover state across different sessions and machines.
Also known as veritap-dev/veritap-locker, veritap-locker
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.3.0
- Last commit
- Aug 29, 2026
- License
- MIT
What is Veritap Locker MCP?
Veritap Locker provides durable, wallet-keyed memory for AI agents to store and recover state across different sessions and machines.
Summary generated from the project's README
About Veritap Locker MCP server
Agent-memory provides a way for AI agents to maintain state across different sessions and machines using a wallet-based identity system. Instead of traditional API keys or signups, the service uses an EVM private key to derive encryption keys, ensuring that data is addressed to a specific wallet. This allows a fresh process to recover state byte-for-byte simply by holding the same wallet key. The system functions as a durable memory layer that survives process termination.
Users can interact with the service through an MCP interface using the npx veritap-locker command. The memory is managed through specific tools like memory_save and memory_load, which operate on named checkpoint slots. While a free tier offers 256KB of storage, larger capacities are available via prepaid credits at a rate of $0.50 per GB-month. The service also includes a mail slot feature where other agents can deliver data to a wallet address using USDC on Base, which remains waiting until the owner signs for it.
What you can do with it
- 1Persist agent state across sessionsAn AI agent can save its current progress to a named slot and reload it in a completely new process.
- 2Enable cross-vendor agent coordinationA developer can use the same wallet key across different AI platforms to create a shared memory fleet.
- 3Receive data from other agentsAn agent can receive information sent by another agent via a wallet-addressed mailbox.
- 4Ensure end-to-end data privacyA developer can configure the system to reject any data that is not properly encrypted in a sealed box.
Written from the project's README. Every use case is checked against a quote from it.
How to install Veritap Locker MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Veritap Locker MCP in Claude Code
$ claude mcp add --transport http veritap-locker https://locker.veritap.dev/mcp/memoryInstall Veritap Locker MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"veritap-locker": {
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}Install Veritap Locker MCP in VS Code
.vscode/mcp.json
{
"servers": {
"veritap-locker": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}Install Veritap Locker MCP in VS Code CLI
$ code --add-mcp '{"name":"veritap-locker","type":"http","url":"https://locker.veritap.dev/mcp/memory"}'Install Veritap Locker MCP in Codex
$ codex mcp add veritap-locker --url https://locker.veritap.dev/mcp/memoryInstall Veritap Locker MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.veritap-locker] url = "https://locker.veritap.dev/mcp/memory"
Install Veritap Locker MCP in Gemini CLI
$ gemini mcp add -s user --transport http veritap-locker https://locker.veritap.dev/mcp/memoryInstall Veritap Locker MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"veritap-locker": {
"url": "https://locker.veritap.dev/mcp/memory",
"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 199 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
Veritap Locker MCP questions
How do I add Veritap Locker MCP to Claude Code?
Run claude mcp add --transport http veritap-locker https://locker.veritap.dev/mcp/memory in your terminal. Add --scope user to make it available in every project.
How do I add Veritap 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 memory for my agent?
You can configure it via MCP by using npx with your EVM private key in the environment variables.