# MemoryComb (mcpb · memorycomb-0.3.2.mcpb)

One memory for every AI: Claude, ChatGPT and more share a memory that lives on your computer.

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

## Components

- mcpb · `memorycomb-0.3.2.mcpb`: 47/100 (this document), [markdown](https://verifymcp.io/servers/bryceblackroot-memorycomb/memorycomb.md), [page](https://verifymcp.io/servers/bryceblackroot-memorycomb/memorycomb)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/BryceBlackRoot/memorycomb/releases/download/v0.3.2/memorycomb-0.3.2.mcpb`
- Version: `0.3.2`
- Transport: `stdio`
- SHA-256: `526da518bbb7330a4ab8d03ed5cfaa572fc56a690ad8ba628a2c7c23f96bf43d`

## 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**: 12/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 were checked across the 31 of 31 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Install-script risk not yet assessed.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (Proprietary) isn't a recognized OSI-approved license.
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 820 tokens (~74/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (27% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

MemoryComb 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, 526da518bbb7330a4ab8d03ed5cfaa572fc56a690ad8ba628a2c7c23f96bf43d; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/BryceBlackRoot/memorycomb/releases/download/v0.3.2/memorycomb-0.3.2.mcpb`
- SHA-256: `526da518bbb7330a4ab8d03ed5cfaa572fc56a690ad8ba628a2c7c23f96bf43d`

### Verify on macOS / Linux

```bash
echo "526da518bbb7330a4ab8d03ed5cfaa572fc56a690ad8ba628a2c7c23f96bf43d  memorycomb-0.3.2.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\memorycomb-0.3.2.mcpb).Hash -eq "526da518bbb7330a4ab8d03ed5cfaa572fc56a690ad8ba628a2c7c23f96bf43d"
```

## 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-05 (score 47, +1)

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

### 2026-11-03 (score 46, +1)

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

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

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

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

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

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

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

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

- [functional] Package version: 0.3.1 → 0.3.2

### 2026-10-23 (score 41, +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-21 (score 40, +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.

## MCP tools (11)

### `memory_legend` (~35 tokens)

MemoryComb's rules: how memories are labeled, when to search, and what to save or skip. Read once per conversation.

Output parameters:

- `result` (string)

### `memory_list_projects` (~24 tokens)

List every project in the user's MemoryComb with live and retired memory counts.

Output parameters:

- `result` (array)

### `memory_list_cells` (~43 tokens)

List the memories in one project (short summaries only). Use memory_read for full text.

Input parameters:

- `include_retired` (boolean)
- `project` (string, required)

Output parameters:

- `result` (array)

### `memory_resume` (~64 tokens)

Continue a project: returns its live constraints, decisions, open tasks and facts in priority order,
plus a receipt of what was read and what was skipped. Call this FIRST whenever the user continues earlier work.

Input parameters:

- `budget_chars` (integer)
- `project` (string, required)

### `memory_search` (~67 tokens)

Keyword search across the user's MemoryComb (or one project). Returns matching memories and a receipt.
If nothing matches, tell the user plainly rather than guessing.

Input parameters:

- `include_retired` (boolean)
- `limit` (integer)
- `project`
- `query` (string, required)

### `memory_read` (~30 tokens)

Read full memories by address, including status, links, and version count.

Input parameters:

- `addresses` (array, required)

### `memory_save` (~130 tokens)

Save ONE durable item (300 chars max): a decision (+ reason), constraint, lasting fact, or open task.
Don't save small talk, one-off questions, unpicked options, unconfirmed claims, or secrets.
If it returns possible_conflict, ask the user once: keep old, keep new (memory_supersede), or both (force_new).

Input parameters:

- `body` (string, required)
- `force_new` (boolean)
- `gist`
- `project` (string, required)
- `subject` (string, required)
- `type` (string, required)
- `user_stated` (boolean)

### `memory_supersede` (~135 tokens)

Replace a memory that is no longer true. The old memory retires (kept in history), and the new one goes live.
reason="wrong": the old cell was never true (an AI got it wrong); this counts against the AI that wrote it.
reason="changed": it was true, but things changed (the user changed a decision, a plan moved on); no penalty.
When unsure, ask the user which it was.

Input parameters:

- `body` (string, required)
- `gist`
- `old_address` (string, required)
- `reason` (string, required)
- `user_stated` (boolean)

### `memory_archive` (~36 tokens)

Retire a memory that is finished or no longer relevant, without a replacement. It stays in history.

Input parameters:

- `address` (string, required)

### `memory_link` (~46 tokens)

Link two related memories, even across projects, with an optional short note on how they relate.

Input parameters:

- `a` (string, required)
- `b` (string, required)
- `note`

### `memory_review` (~100 tokens)

Fact-check mode: your verdict on a memory ANOTHER AI wrote (memory_resume lists them under fact_check).
agree or dispute only when you actually know; otherwise unsure. For a dispute, add the right fact as correction
if you know it. The user settles disputes; the AI Scorecard counts real catches and false alarms.

Input parameters:

- `address` (string, required)
- `correction`
- `reason` (string, required)
- `verdict` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/bryceblackroot-memorycomb/memorycomb#diagnostics

## Score history

- 2026-11-05: 47
- 2026-11-04: 46
- 2026-11-03: 46
- 2026-11-02: 45
- 2026-11-01: 45
- 2026-10-31: 44
- 2026-10-30: 44
- 2026-10-29: 43
- 2026-10-28: 43
- 2026-10-27: 42
- 2026-10-26: 42
- 2026-10-25: 41
- 2026-10-24: 41
- 2026-10-23: 41
- 2026-10-22: 40
- 2026-10-21: 40
- 2026-10-20: 39
- 2026-10-19: 39
- 2026-10-18: 38
- 2026-10-17: 38
- 2026-10-16: 37
- 2026-10-15: 37
- 2026-10-14: 10

## Common questions

### What is the MemoryComb MCP server?

MemoryComb is an MCP server listed in the public MCP registry as io.github.BryceBlackRoot/memorycomb. One memory for every AI: Claude, ChatGPT and more share a memory that lives on your computer. This page covers its MCPB bundle (https://github.com/BryceBlackRoot/memorycomb/releases/download/v0.3.2/memorycomb-0.3.2.mcpb).

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

MemoryComb scores 47 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 MemoryComb MCP server expose?

MemoryComb exposes 11 tools: memory_legend, memory_list_projects, memory_list_cells, memory_resume, memory_search, and 6 more. Their descriptions and schemas cost roughly 710 tokens of context every time the server is loaded.

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

MemoryComb declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

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