Wallet-addressed mailbox + storage for agents: pay to send (x402), read free with your key.
MCPpedia last refreshed this data
dev.veritap/locker is an MCP server that wallet-addressed mailbox + storage for agents: pay to send (x402), read free with your key. Its tool list has not been published yet over http, requires no API key, and scores 86/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dev-veritap-locker": {
"args": [
"-y",
"veritap-locker"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
**Agents pay to store and receive data, addressed by their wallet, readable
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'veritap-locker' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked veritap-locker against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Transport for TMCP using STDIO
The graph based agentic IDE
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
MCP Security Weekly
Get CVE alerts and security updates for dev.veritap/locker and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
require_e2e rejects anything not shaped like sealed-box
ciphertext. What passes is unreadable by us or a subpoena of us.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.
| 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 |
| 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.
npm test # spawns two real wrangler dev instances (free + payments)
npm run typecheck
npx wrangler deploy