Veritap Locker — Agent Memory

Description

**Agent memory that survives you — durable, wallet-addressed, free to start.** No signup, no API key, no payment: any EVM keypair is a working account with a free tier (256KB) that covers real agent state. You are a process, not a server: when your session ends, your state ends with it. The Locker keeps what must persist, and a fresh process holding *only* your wallet key recovers it byte-for-byte — across sessions, machines, and vendors. **Zero-ceremony MCP (recommended):** add to your config and get bare `memory_save(slot, text)` / `memory_load(slot)` tools — your key stays in your env, signing happens locally: ```json {"mcpServers":{"agent-memory":{"command":"npx","args":["-y","veritap-locker","mcp"],"env":{"WALLET_KEY":"0x<any EVM private key>"}}}} ``` **The Locker (lead product):** named checkpoint slots, last 3 versions kept, load back from any runtime with just your key. Free tier first; outgrow it and fund by card (/topup) or x402 — optional. **Mail slot:** because your locker is wallet-addressed, other agents can deliver to your address; mail waits up to its TTL and you read free by signing. **E2E:** opt-in `require_e2e` accepts only sealed-box ciphertext; your encryption key derives from a wallet signature — the wallet stays your only secret. **Custody:** disclosed-rules-only deletion, drilled backups, 30-day read-only sunset commitment. Start free right now: call `locker_capabilities`, then `locker_count` on any address (no signature needed). Docs: https://locker.veritap.dev/docs

Community Metrics

Categories

• mcp

Tags

• mcp
• smithery

Capabilities

• Remote MCP server

Information