Veritap Locker — Agent Memory
https://server.smithery.ai/veritapdev/locker/mcp**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
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (3451 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 12 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 24% of peers
- This listing 568 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/veritapdev/locker/mcpcurl -X POST https://server.smithery.ai/veritapdev/locker/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'