All MCP Servers
AI & MemoryMCP Registryremote12 toolsB · 71

agent-memory MCP server

dev.veritap · Updated

Agent memory: free durable storage (any keypair, no signup) that survives sessions and machines.

At a glance

agent-memory is an MCP server in the AI & Memory category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 12 tools, including locker_capabilities, locker_nonce and locker_send. It scores B (71/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 0GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install agent-memory in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install agent-memory in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add --transport http agent-memory https://locker.veritap.dev/mcp/memory
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. locker_capabilities, locker_nonce, locker_send). It discovers them automatically.

What tools does agent-memory expose? (12)

Read from the live server. Click any tool for its input schema.

  • locker_capabilitiesFree. 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_nonceFree. Returns the single-use statement to sign (EIP-191) for authenticated tools. Expires in 5 minutes.
  • locker_sendDeliver 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
  • locker_readFree. 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_ackFree, owner-signed. Ack IS delete — disclosed rule, by design: acked messages and their bodies are removed immediately. Unknown ids are silently skipped.
  • locker_countFree. 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_directoryFree. 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_register_keyOwner-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 si
  • locker_checkpoint★ 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
  • locker_creditPAID 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_statusFree. Credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state for an address.
  • locker_inviteFree. 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.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Third-party hosted service — Your requests and any data in them are sent to locker.veritap.dev.
  • No local execution — Nothing is installed or run on your machine.
  • Last commit 2 months ago — Actively maintained.
  • Repository created 2 months ago — Very new project with little track record yet.
  • 0 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 71

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%96%

    Last commit 61 days ago.

  • Adoption20%0%

    0 stars.

  • Transparency20%100%

    4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.

  • Provenance15%75%

    Links to its own repository; package linkage unverified.

  • Packaging15%75%

    Remote endpoint; authentication requirements not declared.

Documentation

Full README

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

Maintain agent-memory? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![agent-memory on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/dev-veritap-agent-memory)](https://mcp-skills-hub.vercel.app/mcps/dev-veritap-agent-memory)

Catalog data refreshed . Something wrong? Report it.