Back to Browse

Veritap Locker MCP Server

Developer ToolsUse Caution4.5MCP RegistryRemote
Free

Server data from the Official MCP Registry

Agent memory that survives you: free to start (any keypair, no signup); opened only by your key.

About

Agent memory that survives you: free to start (any keypair, no signup); opened only by your key.

Remote endpoints: streamable-http: https://locker.veritap.dev/mcp

Security Report

4.5
Use Caution4.5High Risk

Veritap Locker is a wallet-addressed durable memory system for AI agents with appropriate security controls for its use case. The codebase uses proper cryptographic libraries (viem, tweetnacl, blakejs) and EIP-191 signing for authentication. Permissions align with the stated purpose of storing and retrieving encrypted agent state. Minor concerns include broad exception handling and the bundled CLI code readability, but no critical vulnerabilities or authentication bypasses were identified. Supply chain analysis found 6 known vulnerabilities in dependencies (1 critical, 0 high severity).

4 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

env_vars

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

File System Read

Reads files on the server that hosts it, not on your machine.

File System Write

Writes files on the server that hosts it, not on your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "dev-veritap-locker": {
      "url": "https://locker.veritap.dev/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub 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

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

SurfaceWhere
MCPhttps://locker.veritap.dev/mcp — call locker_capabilities first
HTTPhttps://locker.veritap.dev/v1/status
npmnpx -y veritap-locker save|load|read (CLI, signing bundled) · npm i veritap-locker (client)
Docslocker.veritap.dev/docs
ResearchPriors, not search: how AI agents choose tools — a 9-run, 2-vendor field study
X@veritaplocker
Reference clientclient/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

Reviews

No reviews yet

Be the first to review this server!