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.
Available components
Last scanned (22 hours ago)
Scores higher than 0% of remote servers
Reachable. Last reached 27 Sep 2026.
Category Memory and Knowledge
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. How we score → Why this is hard to score →
Endpoint Security0
- 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.Unverified
- 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.Unverified
- 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. View diagnostics → Unverified
- 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.Unverified
- 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.Unverified
Transport & Reachability0
- 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. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 −71
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://recall.notdown-app.workers.dev/mcp/{key}
Transports 1 probe
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| http (plaintext) | http://recall.notdown-app.workers.dev/mcp/%7Bkey%7D | Inconclusive |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
memory_forget ~23
Delete a saved memory by key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
memory_list ~27
List the keys of all your saved memories, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
memory_recall ~26
Retrieve a previously saved memory by its exact key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | – |
No output schema declared.
No examples provided.
memory_save ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Unique key/name for this memory. |
| tags | array | – | Optional tags for later search. |
| value | string | yes | The content to remember. |
No output schema declared.
No examples provided.
memory_search ~43
Search your saved memories by keyword across keys, values, and tags. Returns matching memories, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
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.
remote · recall.notdown-app.workers.dev
claude mcp add --transport http dev-workers-notdown-app-recall-memory 'https://recall.notdown-app.workers.dev/mcp/%7Bkey%7D'
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.