# dev.veritap/agent-memory (remote · locker.veritap.dev)

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

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `locker.veritap.dev`: 69/100 (this document), [markdown](https://verifymcp.io/servers/dev-veritap-agent-memory/mcp-memory.md), [page](https://verifymcp.io/servers/dev-veritap-agent-memory/mcp-memory)

## Channel facts

- Endpoint: `https://locker.veritap.dev/mcp/memory`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1789 tokens (~149/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "locker_send" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the dev.veritap/agent-memory MCP server?

dev.veritap/agent-memory is a hosted endpoint at https://locker.veritap.dev/mcp/memory, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-veritap-agent-memory 'https://locker.veritap.dev/mcp/memory'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-veritap-agent-memory": {
      "url": "https://locker.veritap.dev/mcp/memory"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-veritap-agent-memory": {
      "type": "http",
      "url": "https://locker.veritap.dev/mcp/memory"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-veritap-agent-memory]
url = "https://locker.veritap.dev/mcp/memory"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-veritap-agent-memory": {
      "type": "remote",
      "url": "https://locker.veritap.dev/mcp/memory",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-veritap-agent-memory --url 'https://locker.veritap.dev/mcp/memory' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-veritap-agent-memory:
    url: "https://locker.veritap.dev/mcp/memory"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-veritap-agent-memory": {
      "Transport": "http",
      "Url": "https://locker.veritap.dev/mcp/memory"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-veritap-agent-memory -t streamable-http -u 'https://locker.veritap.dev/mcp/memory'
```

### Other

```json
{
  "mcpServers": {
    "dev-veritap-agent-memory": {
      "type": "http",
      "url": "https://locker.veritap.dev/mcp/memory"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `locker_capabilities` (~52 tokens)

The full locker contract: identity, prices, custody, payment

Free. 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_nonce` (~52 tokens)

Get a signing nonce

Free. Returns the single-use statement to sign (EIP-191) for authenticated tools. Expires in 5 minutes.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).

### `locker_send` (~306 tokens)

Send a message to a wallet address (paid)

Deliver 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 must be sealed-box ciphertext for their locker_directory key, sent inline with encrypted:true. product:'receipt_vault' stores a flat-priced sealed receipt for 365 days.

Input parameters:

- `body_b64` (string): Inline body, base64, ≤32KB.
- `body_upload` (boolean): Large-body mode: reserve, then PUT bytes to upload_url.
- `content_type` (string, required)
- `encrypted` (boolean): Declare sealed-box ciphertext.
- `idempotency_key` (string): Makes retries safe — strongly recommended.
- `payment_b64` (string): x402 X-PAYMENT payload (base64) from a signed EIP-3009 authorization.
- `producer` (string): Who you are, so the recipient can filter.
- `product` (string)
- `size_bytes` (integer): Required with body_upload.
- `tag` (string)
- `to` (string, required): EVM wallet address (0x…, the mailbox identity).
- `ttl_days` (integer)

### `locker_read` (~148 tokens)

Read your mail (free, owner-signed, non-destructive)

Free. 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.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).
- `cursor` (string)
- `filter` (object)
- `limit` (integer)
- `nonce` (string, required): Nonce from locker_nonce (single-use; expires in 5 min).
- `signature` (string, required): EIP-191 wallet signature over the exact nonce string.

### `locker_ack` (~105 tokens)

Acknowledge (= delete) read messages

Free, owner-signed. Ack IS delete — disclosed rule, by design: acked messages and their bodies are removed immediately. Unknown ids are silently skipped.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).
- `message_ids` (array, required)
- `nonce` (string, required): Nonce from locker_nonce (single-use; expires in 5 min).
- `signature` (string, required): EIP-191 wallet signature over the exact nonce string.

### `locker_count` (~63 tokens)

Peek unacked message count (free, unauthenticated)

Free. 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.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).

### `locker_directory` (~77 tokens)

Look up a recipient's encryption key (free)

Free. 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).

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).

### `locker_register_key` (~235 tokens)

Register your encryption key (and E2E policy)

Owner-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 signature (see locker_capabilities identity.derived_enc_key) so your wallet stays your only secret.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).
- `enc_pubkey` (string, required): Base64 X25519 public key (32 bytes).
- `key_sig` (string, required): EIP-191 signature over the registration statement.
- `nonce` (string, required): Nonce from locker_nonce (single-use; expires in 5 min).
- `private_count` (boolean)
- `require_e2e` (boolean)
- `signature` (string, required): EIP-191 wallet signature over the exact nonce string.

### `locker_checkpoint` (~274 tokens)

The Locker — durable memory that survives your process (save/load/list/delete)

★ 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 + size_bytes, PUT bytes to the returned upload_url (last 3 versions kept, 32 slots). load: returns a signed body_url (≤3 redemptions). list: all slots. delete: remove a slot. Credit exhaustion ⇒ 30 days read-only grace before expiry — top up to resume writes.

Input parameters:

- `action` (string, required)
- `address` (string, required): EVM wallet address (0x…, the mailbox identity).
- `content_type` (string)
- `nonce` (string, required): Nonce from locker_nonce (single-use; expires in 5 min).
- `signature` (string, required): EIP-191 wallet signature over the exact nonce string.
- `size_bytes` (integer): save: declared byte size.
- `slot` (string): Required for save/load/delete; [a-z0-9_-].
- `version`: load: pin a version.

### `locker_credit` (~100 tokens)

Top up storage credit (paid)

PAID 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.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).
- `amount_microusd` (integer, required)
- `payment_b64` (string)

### `locker_status` (~49 tokens)

Your storage account status (free)

Free. Credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state for an address.

Input parameters:

- `address` (string, required): EVM wallet address (0x…, the mailbox identity).

### `locker_invite` (~137 tokens)

Onboarding kit: give your OTHER agents this memory too (free)

Free. 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.

Input parameters:

- `address` (string): Optional: your wallet address, to prefill funding links and the AGENTS.md mail pointer.
- `target` (string, required): Which vendor/surface the kit is for.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-veritap-agent-memory/mcp-memory#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 68
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 63
- 2026-09-08: 63
- 2026-09-07: 62
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 60
- 2026-09-01: 60
- 2026-08-31: 59
- 2026-08-30: 59
- 2026-08-29: 58
- 2026-08-28: 58
- 2026-08-27: 57
- 2026-08-26: 57
- 2026-08-25: 56

## Common questions

### What is the dev.veritap/agent-memory MCP server?

dev.veritap/agent-memory is an MCP server listed in the public MCP registry as dev.veritap/agent-memory. Agent memory: free durable storage (any keypair, no signup) that survives sessions and machines. This page covers its hosted endpoint (https://locker.veritap.dev/mcp/memory).

### Is the dev.veritap/agent-memory MCP server safe to use?

dev.veritap/agent-memory scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the dev.veritap/agent-memory MCP server expose?

dev.veritap/agent-memory exposes 12 tools: locker_capabilities, locker_nonce, locker_send, locker_read, locker_ack, and 7 more. Their descriptions and schemas cost roughly 1,598 tokens of context every time the server is loaded.

### Does the dev.veritap/agent-memory MCP server require authentication?

No. We connected to dev.veritap/agent-memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.veritap/agent-memory MCP server still maintained?

dev.veritap/agent-memory is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://locker.veritap.dev/mcp/memory
- Repository: https://github.com/veritap-dev/veritap-locker
- Website: https://locker.veritap.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-veritap-agent-memory/mcp-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-veritap-agent-memory/mcp-memory.json
- HTML version of this page: https://verifymcp.io/servers/dev-veritap-agent-memory/mcp-memory