# Recall (mcpb · recall.mcpb)

Private, encrypted memory about you, shared by all your AI agents. Self-hosted; runs on a Pi.

- Trust score: 46/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `recall.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/j4ckxyz-recall/recall.md), [page](https://verifymcp.io/servers/j4ckxyz-recall/recall)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/j4ckxyz/recall/releases/download/v0.1.4/recall.mcpb`
- Transport: `stdio`
- SHA-256: `cbb14034b5a046bb3fa6e5e8d5554e3fbd3872b600919bdffdccf111a7a8d811`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 406 tokens (~101/item across 4 items; 3 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Recall MCP server?

Recall ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, cbb14034b5a046bb3fa6e5e8d5554e3fbd3872b600919bdffdccf111a7a8d811; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/j4ckxyz/recall/releases/download/v0.1.4/recall.mcpb`
- SHA-256: `cbb14034b5a046bb3fa6e5e8d5554e3fbd3872b600919bdffdccf111a7a8d811`

### Verify on macOS / Linux

```bash
echo "cbb14034b5a046bb3fa6e5e8d5554e3fbd3872b600919bdffdccf111a7a8d811  recall.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\recall.mcpb).Hash -eq "cbb14034b5a046bb3fa6e5e8d5554e3fbd3872b600919bdffdccf111a7a8d811"
```

## 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-11-04 (score 46, +1)

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

### 2026-11-02 (score 45, +1)

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

### 2026-10-31 (score 44, +1)

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

### 2026-10-29 (score 43, +1)

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

### 2026-10-27 (score 42, +1)

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

### 2026-10-25 (score 41, +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-24 (score 40, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 40)

First indexed and scored.

## MCP tools (3)

### `recall` (~50 tokens)

Recall about the user

Search what is known about the user. Omit `query` to get their whole profile.

Input parameters:

- `limit` (integer)
- `query` (string): A few keywords, e.g. "diet allergies"

### `remember` (~79 tokens)

Remember about the user

Save one durable fact about the user, in third person ("User prefers…").

Input parameters:

- `content` (string, required): One self-contained fact
- `date` (string): When this was learned or became true (YYYY-MM-DD or ISO 8601). Omit for now.
- `replaces` (string): Id of a memory this corrects or supersedes

### `forget` (~25 tokens)

Forget about the user

Remove a memory that is wrong or no longer true.

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/j4ckxyz-recall/recall#diagnostics

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 44
- 2026-10-31: 44
- 2026-10-30: 43
- 2026-10-29: 43
- 2026-10-28: 42
- 2026-10-27: 42
- 2026-10-26: 41
- 2026-10-25: 41
- 2026-10-24: 40
- 2026-10-23: 40

## Common questions

### What is the Recall MCP server?

Recall is an MCP server listed in the public MCP registry as io.github.j4ckxyz/recall. Private, encrypted memory about you, shared by all your AI agents. Self-hosted; runs on a Pi. This page covers its MCPB bundle (https://github.com/j4ckxyz/recall/releases/download/v0.1.4/recall.mcpb).

### Is the Recall MCP server safe to use?

Recall scores 46 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 MCP server expose?

Recall exposes 3 tools: recall, remember, forget. Their descriptions and schemas cost roughly 154 tokens of context every time the server is loaded.

### What licence is the Recall MCP server under?

Recall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/j4ckxyz/recall
- Changelog RSS feed: https://verifymcp.io/servers/j4ckxyz-recall/recall.xml
- Changelog JSON feed: https://verifymcp.io/servers/j4ckxyz-recall/recall.json
- HTML version of this page: https://verifymcp.io/servers/j4ckxyz-recall/recall