# com.borisinc/memory (remote · mem.borisinc.com)

Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.

- Trust score: 64/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mem.borisinc.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-borisinc-memory/mem.md), [page](https://verifymcp.io/servers/com-borisinc-memory/mem)

## Channel facts

- Endpoint: `https://mem.borisinc.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-03.

- **Endpoint Security**: 57/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 8 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 is enforced; there's no plaintext access path.
  - 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**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 726 tokens (~90/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-borisinc-memory https://mem.borisinc.com/mcp
```

### Codex

```toml
[mcp_servers.com-borisinc-memory]
url = "https://mem.borisinc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-borisinc-memory": {
      "type": "remote",
      "url": "https://mem.borisinc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-borisinc-memory --url https://mem.borisinc.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-borisinc-memory:
    url: "https://mem.borisinc.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-borisinc-memory": {
      "type": "http",
      "url": "https://mem.borisinc.com/mcp"
    }
  }
}
```

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-08-02 (score 64, +1)

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

### 2026-07-31 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 62, +3)

- [security improvement] HTTPS: unverified → pass

### 2026-07-29 (score 59, +2)

- [security] Tool “memory_write” rewrote its description, which is the text the model reads
- [security] Tool “memory_export” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 55 → 90
- [functional improvement] Tool coverage: 60% → 73%
- [functional] New tool “memory_import”
- [functional] New tool “memory_search_free”
- [functional] New tool “memory_write_free”
- [functional] New tool “memory_forget”
- [cosmetic] “memory_export” added an optional parameter “offset”
- [cosmetic] “memory_write” added an optional parameter “supersedes”

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (8)

### `memory_write` (~148 tokens)

Store a memory permanently. Namespaced to YOUR paying wallet — your wallet is your private memory store. Semantic-indexed for later search. Optional supersedes=[ids] marks prior memories in your namespace as superseded by this one (excluded from search, still visible in export with their superseded_by id) — a Zep-style update-in-place without ever losing history. Paid: $0.001 per write via x402 (payment in _meta['x402/payment']).

Input parameters:

- `content` (string, required): The memory text (max 8000 chars)
- `supersedes` (array): ids of prior memories (same namespace) that this write supersedes
- `tags` (array)

### `memory_search` (~62 tokens)

Semantic search over YOUR stored memories (payer-wallet namespace). Returns top-k by embedding similarity. Paid: $0.002 per search via x402.

Input parameters:

- `k` (integer): max results (default 5, cap 20)
- `query` (string, required)

### `memory_export` (~83 tokens)

Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.

Input parameters:

- `offset` (integer): row offset for paging past the first 1000 (default 0)

### `memory_import` (~85 tokens)

Bulk-write memories into YOUR namespace (max 200/call, content <=8k chars each). Accepts the exact shape memory_export emits, so a whole namespace can move in with one paid call. Embeds best-effort; missing embeddings are backfilled hourly. Paid: $0.01 flat via x402.

Input parameters:

- `memories` (array, required): up to 200 items

### `memory_forget` (~63 tokens)

Delete memories by id from YOUR namespace (or a namespace you hold a write/rw grant for). Max 100 ids per call. Paid: $0.001 per call via x402.

Input parameters:

- `ids` (array, required): memory ids to delete (max 100)

### `memory_write_free` (~153 tokens)

FREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment. wallet_auth = base64 JSON {address,ts,signature} where signature = personal_sign of 'borismem-free:<address>:<ts>' (ts within 600s). Writes to the SAME namespace paid calls use. Capped at 1000 writes / rolling 30 days per wallet; over cap returns an error pointing to the paid tier.

Input parameters:

- `content` (string, required): The memory text (max 8000 chars)
- `tags` (array)
- `wallet_auth` (string, required): base64 JSON {address,ts,signature} -- see description

### `memory_search_free` (~94 tokens)

FREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign. Same wallet_auth scheme as memory_write_free. Capped at 500 searches / rolling 30 days per wallet.

Input parameters:

- `k` (integer): max results (default 5, cap 20)
- `query` (string, required)
- `wallet_auth` (string, required): base64 JSON {address,ts,signature}

### `memory_stats` (~38 tokens)

FREE: count + last-write timestamp for any wallet namespace. Content is never returned on the free tier.

Input parameters:

- `namespace` (string, required): wallet address

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-borisinc-memory/mem#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 62
- 2026-07-29: 59
- 2026-07-28: 57
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://mem.borisinc.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-borisinc-memory/mem/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-borisinc-memory/mem/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-borisinc-memory/mem