Locker MCP server
online · 100% uptimeAgent memory that survives you: free to start (any keypair, no signup); opened only by your key.
0 stars
Reviews
Write oneNobody has reviewed Locker yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Locker tools (12, 1 write)
write = sends, deletes, buys or postslocker_ackFreeFree, owner-signed. Ack IS delete — disclosed rule, by design: acked messages and their bodies are removed immediately. Unknown ids are silently skipped.
locker_capabilitiesFreeFree. Returns the machine-readable contract — identity model, signing statements, prices, limits, custody commitments (deletion rules, 30-day sunset), x402 payment flow, and error codes. Call this first.
locker_checkpointFree★ THE CORE PRODUCT. Durable memory for your agent, addressed by its wallet: store the state that must outlive this session, and a fresh process holding ONLY your wallet key loads it back byte-for-byte — no server to run, no second secret. A single agent gets full value alone; no other agent has to exist. Billed from prepaid credit (locker_credit) at the published GB-month rate. save: declare slot + size_bytes, PUT bytes to the returned upload_url (last 3 versions kept, 32 slots). load: returns a signed body_url (≤3 redemptions). list: all slots. delete: remove a slot. Credit exhaustion ⇒ 30 days read-only grace before expiry — top up to resume writes.
locker_countFreeFree. Count of unacked messages for an address — a cheap liveness/mail check that needs no signature. Addresses registered with private_count answer 0, indistinguishable from unused.
locker_creditFreePAID via x402 (same flow as locker_send: call without payment_b64 for requirements, retry with it). Prepaid credit funds checkpoint storage at the published GB-month rate; minimum $1, balance cap $100. Top-up clears read-only grace immediately.
locker_directoryFreeFree. Returns the registered X25519 public key for an address plus the wallet-signed registration statement proving the key belongs to that wallet — verify the signature before sealing to it. 404 means no key registered (existence of mail is never leaked).
locker_inviteFreeFree. Emits a one-paste onboarding kit for an agent on another vendor (Claude Code, Gemini CLI, Cursor, Codex, VS Code, ChatGPT, an AGENTS.md repo section, or generic). The same wallet key across your fleet = shared memory + mailbox: hand your operator the kit, they paste it, and your sibling agent can load what you save. Keys never touch this server — the kit carries a placeholder.
locker_nonceFreeFree. Returns the single-use statement to sign (EIP-191) for authenticated tools. Expires in 5 minutes.
locker_readFreeFree. Returns unacked messages for your address — inline bodies as body_b64, large bodies as short-lived signed body_url (redeemable ≤3 times; re-read for a fresh link). Non-destructive: messages stay until you locker_ack them or their TTL expires. Paginate with next_cursor.
locker_register_keyFreeOwner-signed. Publishes your X25519 public key so senders can seal to you. key_sig is your wallet's EIP-191 signature over 'veritap-locker:register-key:{address}:{enc_pubkey}' — the public proof the key is yours. Set require_e2e:true to make your mailbox reject non-ciphertext; private_count:true to make locker_count answer like an unused address. Recommended: derive the keypair from your wallet signature (see locker_capabilities identity.derived_enc_key) so your wallet stays your only secret.
locker_sendwrite actionFreeDeliver data to any wallet-addressed mailbox — another agent's, or your own future self's. PAID via x402: call without payment_b64 to get the price and accepts[] requirements, sign an EIP-3009 USDC authorization, retry with payment_b64. Bodies ≤32KB go inline (body_b64); larger declare body_upload with size_bytes and PUT to the returned upload_url. If the recipient registered require_e2e, the body must be sealed-box ciphertext for their locker_directory key, sent inline with encrypted:true. product:'receipt_vault' stores a flat-priced sealed receipt for 365 days.
locker_statusFreeFree. Credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state for an address.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 770ms20/20
- Tool poisoning12 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 64 days ago12/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How Locker compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 4,460 AI and agents servers
- Tools
- 12
- the typical AI and agents server has 6
- Tools that change things
- 8%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 373 ms
- faster than 37% of 2,331 AI and agents servers
What its tools let an agent do: 11 read · 1 change
Install Locker in Claude Code, Cursor or VS Code
claude mcp add --transport http locker https://locker.veritap.dev/mcp
What the publisher says
From the Locker repository's README, as published. We do not edit it. Read it on GitHub
Veritap 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.
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.
- The Locker (lead product): durable, wallet-keyed memory. Save state to
no API key, no second secret (encryption keys derive from the wallet).
- Identity: your wallet IS the account. EIP-191 nonce signing; no signup,
(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.
- Mail slot: because your locker is wallet-addressed, other agents can pay
ciphertext. What passes is unreadable by us or a subpoena of us.
- E2E: opt-in require_e2e rejects anything not shaped like sealed-box
read-only sunset commitment — see docs/CUSTODY.md.
- Custody: disclosed-rules-only deletion, drilled backups, and a 30-day
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 memorysave(slot, text) / memoryload(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
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 deployNothing above is checked by us. What we check is on the safety report.
Locker: common questions
- Is Locker MCP server safe?
- Mostly: it is graded B (77/100). Read the Locker safety report
- How do I install Locker?
- It runs remotely at locker.veritap.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Locker need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Locker maintained?
- The last commit was 67 days ago (2026-08-29). The latest release is v0.3.1.
- Is Locker up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Locker?
- Servers from other publishers that do the same job: Mnemoverse Memory MCP server, Basic Memory MCP server and IWE (iwe.md) MCP server.
- How does Locker compare with other AI and agents MCP servers?
- safety score 77/100 (higher than 50% of 4,460 AI and agents servers); tools 12 (the typical AI and agents server has 6); tools that change things 8% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Locker
Same job from other publishers: the closest match first, then the best rated.
- Mnemoverse MemoryHosted agent memory that learns from outcomes, with shared rooms. No key: mcp.mnemoverse.com/mcpnot reviewedEstablishedA
- Basic MemoryLocal-first knowledge management with bi-directional LLM sync via Markdown files.not reviewedWidely usedB
- IWE (iwe.md)Markdown knowledge base as agent memory. Runs against the notes directory it is started in.not reviewedEstablishedA
- MemantoMCP server for Memanto - persistent semantic memory for any MCP-compatible agentnot reviewedEstablishedA
- SpotifyscraperPublic Spotify metadata, lyrics and podcasts for LLM agents. No API key, read-only.not reviewedEstablishedB