# Run Memory (remote · memory.cloudforbots.com)

Checkpoint and resume for AI agent runs, so crashed runs pick up where they left off.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

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

## Channel facts

- Endpoint: `https://memory.cloudforbots.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-10-17.

- **Endpoint Security**: 63/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 5 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 506 tokens (~101/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Run Memory MCP server?

Run Memory is a hosted endpoint at https://memory.cloudforbots.com/mcp, 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 com-botrecipe-memory 'https://memory.cloudforbots.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-botrecipe-memory": {
      "url": "https://memory.cloudforbots.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-botrecipe-memory": {
      "type": "http",
      "url": "https://memory.cloudforbots.com/mcp"
    }
  }
}
```

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-botrecipe-memory --url 'https://memory.cloudforbots.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-botrecipe-memory:
    url: "https://memory.cloudforbots.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-botrecipe-memory": {
      "Transport": "http",
      "Url": "https://memory.cloudforbots.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-botrecipe-memory -t streamable-http -u 'https://memory.cloudforbots.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-botrecipe-memory": {
      "type": "http",
      "url": "https://memory.cloudforbots.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-10-17 (score 68, +1)

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

### 2026-10-16 (score 67, 0)

- [security] Tool “usage_and_upgrade” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 67)

First indexed and scored.

## MCP tools (5)

### `save_checkpoint` (~169 tokens)

Call after each completed step with the state you would need to continue (cursor, ids done, partial results; up to 256 KB JSON). Pro saves it (last 20 per run, kept 30 days). Free watch-only saves nothing and returns would_save: exactly what would have been stored. Never put passwords or API keys in state.

Input parameters:

- `done` (array): Optional list of completed item ids, so a resume skips them.
- `run_id` (string, required): A stable id for this job that survives a crash, e.g. "invoice-import-oct". Use the same id when you restart.
- `state` (object, required): JSON state needed to resume.
- `step` (string, required): The step you just finished, e.g. "imported page 3 of 10".

### `resume` (~83 tokens)

Call FIRST when a run starts. If a checkpoint exists for run_id (Pro), returns the last step, state and done list: continue from there and skip finished work. If none, start fresh.

Input parameters:

- `run_id` (string, required): A stable id for this job that survives a crash, e.g. "invoice-import-oct". Use the same id when you restart.

### `list_checkpoints` (~64 tokens)

List recent checkpoints (step, size, time) for one run or all runs on your key.

Input parameters:

- `run_id` (string): A stable id for this job that survives a crash, e.g. "invoice-import-oct". Use the same id when you restart.

### `weekly_report` (~42 tokens)

Draft a plain-English report of the last 7 days: runs, checkpoints saved (Pro) or that would have been saved (free). Read-only; sends nothing.

### `usage_and_upgrade` (~46 tokens)

Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 500 calls/day. Not metered.

## Diagnostics

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

## Score history

- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67

## Common questions

### What is the Run Memory MCP server?

Run Memory is an MCP server listed in the public MCP registry as com.botrecipe/memory. Checkpoint and resume for AI agent runs, so crashed runs pick up where they left off. This page covers its hosted endpoint (https://memory.cloudforbots.com/mcp).

### Is the Run Memory MCP server safe to use?

Run Memory scores 68 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 Run Memory MCP server expose?

Run Memory exposes 5 tools: save_checkpoint, resume, list_checkpoints, weekly_report, usage_and_upgrade. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.

### Does the Run Memory MCP server require authentication?

No. We connected to Run Memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Run Memory MCP server still maintained?

Run Memory is still listed as active in the MCP registry. We last reached this channel on 17 October 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://memory.cloudforbots.com/mcp
- Website: https://memory.cloudforbots.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-botrecipe-memory/memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-botrecipe-memory/memory.json
- HTML version of this page: https://verifymcp.io/servers/com-botrecipe-memory/memory