# Recall — persistent memory for agents (remote · recall.notdown-app.workers.dev)

Persistent memory for AI agents. Free, no LLM, no SDK. Open Worker you can self-host in 2 commands.

- Trust score: 0/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `recall.notdown-app.workers.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-notdown-app-recall-memory/mcp-key.md), [page](https://verifymcp.io/servers/dev-workers-notdown-app-recall-memory/mcp-key)

## Channel facts

- Endpoint: `https://recall.notdown-app.workers.dev/mcp/{key}`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## 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-23.

- **Endpoint Security**: 0/100
  - TLS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - Authorisation not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - HTTPS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - HSTS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
  - DNSSEC not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.
- **Transport & Reachability**: 0/100
  - Transport not yet verified: the listed URL is a template whose key variable has no value or default, so there is no address for us to connect to.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 7 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Recall — persistent memory for agents MCP server?

Recall — persistent memory for agents is a hosted endpoint at https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D, 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-workers-notdown-app-recall-memory 'https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-recall-memory": {
      "url": "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-notdown-app-recall-memory": {
      "type": "http",
      "url": "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-notdown-app-recall-memory]
url = "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-notdown-app-recall-memory": {
      "type": "remote",
      "url": "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-notdown-app-recall-memory --url 'https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-notdown-app-recall-memory:
    url: "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-notdown-app-recall-memory": {
      "Transport": "http",
      "Url": "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-notdown-app-recall-memory -t streamable-http -u 'https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-recall-memory": {
      "type": "http",
      "url": "https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

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-28 (score 0, −71)

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

### 2026-09-25 (score 71, 0)

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

### 2026-09-24 (score 71, +1)

- [security] Stability: 0.97 → pass

### 2026-09-22 (score 70, +1)

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

### 2026-08-26 (score 0)

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

### 2026-08-25 (score 0)

First indexed and scored.

## MCP tools (5)

### `memory_save` (~81 tokens)

Save or overwrite a memory under a key so you can recall it in a later session. Use for durable facts, decisions, preferences, and context you want to persist across context resets.

Input parameters:

- `key` (string, required): Unique key/name for this memory.
- `tags` (array): Optional tags for later search.
- `value` (string, required): The content to remember.

### `memory_recall` (~26 tokens)

Retrieve a previously saved memory by its exact key.

Input parameters:

- `key` (string, required)

### `memory_search` (~43 tokens)

Search your saved memories by keyword across keys, values, and tags. Returns matching memories, newest first.

Input parameters:

- `limit` (number)
- `query` (string, required)

### `memory_list` (~27 tokens)

List the keys of all your saved memories, newest first.

Input parameters:

- `limit` (number)

### `memory_forget` (~23 tokens)

Delete a saved memory by key.

Input parameters:

- `key` (string, required)

## Diagnostics

Captured diagnostic sections: Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-notdown-app-recall-memory/mcp-key#diagnostics

## Score history

- 2026-10-23: 0
- 2026-10-22: 0
- 2026-10-21: 0
- 2026-10-20: 0
- 2026-10-19: 0
- 2026-10-18: 0
- 2026-10-17: 0
- 2026-10-16: 0
- 2026-10-15: 0
- 2026-10-14: 0
- 2026-10-13: 0
- 2026-10-12: 0
- 2026-10-10: 0
- 2026-10-07: 0
- 2026-10-05: 0
- 2026-10-04: 0
- 2026-10-03: 0
- 2026-10-02: 0
- 2026-10-01: 0
- 2026-09-30: 0
- 2026-09-29: 0
- 2026-09-28: 0
- 2026-09-27: 71
- 2026-09-26: 71
- 2026-09-25: 71
- 2026-09-24: 71
- 2026-09-23: 70
- 2026-09-22: 70
- 2026-09-21: 69
- 2026-09-20: 69

## Common questions

### What is the Recall — persistent memory for agents MCP server?

Recall — persistent memory for agents is an MCP server listed in the public MCP registry as dev.workers.notdown-app.recall/memory. Persistent memory for AI agents. Free, no LLM, no SDK. Open Worker you can self-host in 2 commands. This page covers its hosted endpoint (https://recall.notdown-app.workers.dev/mcp/{key}).

### Is the Recall — persistent memory for agents MCP server safe to use?

Recall — persistent memory for agents scores 0 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 Recall — persistent memory for agents MCP server expose?

Recall — persistent memory for agents exposes 5 tools: memory_save, memory_recall, memory_search, memory_list, memory_forget. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.

### Does the Recall — persistent memory for agents MCP server require authentication?

Its publisher declares no required credentials for Recall — persistent memory for agents. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Recall — persistent memory for agents MCP server still maintained?

Recall — persistent memory for agents is still listed as active in the MCP registry. We last reached this channel on 27 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://recall.notdown-app.workers.dev/mcp/%7Bkey%7D
- Website: https://recall.notdown-app.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-notdown-app-recall-memory/mcp-key.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-notdown-app-recall-memory/mcp-key.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-notdown-app-recall-memory/mcp-key