How do I install Agent Memory?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Agent Memory need an API key?

No required environment variable is listed on this record.

What transport does Agent Memory use?

Agent Memory is reached over HTTP.

When was Agent Memory last checked?

Last checked 2026-11-08. Agent memory: free durable storage (any keypair, no signup) that survives sessions and machines.

Agent Memory MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://locker.veritap.dev/mcp/memory

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http dev.veritap-agent-memory https://locker.veritap.dev/mcp/memory

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "dev.veritap-agent-memory": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://locker.veritap.dev/mcp/memory"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.3.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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.

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_e2e rejects 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

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Agent Memory?

Does Agent Memory need an API key?

What transport does Agent Memory use?

When was Agent Memory last checked?

Documentation

Veritap Locker

One paste = durable agent memory

Surfaces

Develop