# TOMC Memory (mcpb · tomc-memory-0.1.1.mcpb)

CPU task-specific context preparation and explicitly saved local project notes through MCP.

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

## Components

- mcpb · `tomc-memory-0.1.1.mcpb`: 49/100 (this document), [markdown](https://verifymcp.io/servers/zipengwu365-tomc-memory/tomc-memory.md), [page](https://verifymcp.io/servers/zipengwu365-tomc-memory/tomc-memory)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/ZipengWu365/TOMC/releases/download/v0.1.1-assistant-preview.1/tomc-memory-0.1.1.mcpb`
- Transport: `stdio`
- SHA-256: `f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be`

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

- **Supply Chain Security**: 13/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 29 of 29 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - Install-script risk not yet assessed.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/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 19 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 709 tokens (~141/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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 TOMC Memory MCP server?

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

- Download bundle: `https://github.com/ZipengWu365/TOMC/releases/download/v0.1.1-assistant-preview.1/tomc-memory-0.1.1.mcpb`
- SHA-256: `f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be`

### Verify on macOS / Linux

```bash
echo "f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be  tomc-memory-0.1.1.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\tomc-memory-0.1.1.mcpb).Hash -eq "f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be"
```

## 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 49, +1)

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

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

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

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

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

### 2026-10-29 (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-10-27 (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-25 (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-22 (score 43, +1)

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

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

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

## MCP tools (5)

### `prepare_context` (~100 tokens)

Prepare separately supplied external history or documents for the next task without saving. Do not call this to proactively recompact the active host-managed chat; unknown host compaction state also leaves chat ownership with the host. Omit budget to keep about 80% of estimated history tokens (at least 1,024). Budget excludes task/tool framing; host history is unchanged.

Input parameters:

- `budget`
- `history` (string, required)
- `task` (string, required)

### `remember_memory` (~52 tokens)

Optionally save user-authorized history as text or message JSON to a named notebook. Appends; preserves earlier entries. Use one name per topic.

Input parameters:

- `content` (string, required)
- `name` (string, required)

### `recall_memory` (~77 tokens)

Prepare an optional notebook's history for the next task. Omit budget to keep about 80% of the notebook (at least 1,024 estimated tokens). Budget covers estimated memory tokens. Reports and old failures are not proof of current success.

Input parameters:

- `budget`
- `name` (string, required)
- `task` (string, required)

### `list_memories` (~26 tokens)

Find saved notebook names. Returns names, entry counts and update times, without content.

### `forget_memory` (~35 tokens)

Delete one exact named notebook when the user asks to forget it. Cannot be undone through this tool.

Input parameters:

- `name` (string, required)

## Diagnostics

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

## Score history

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

## Common questions

### What is the TOMC Memory MCP server?

TOMC Memory is an MCP server listed in the public MCP registry as io.github.ZipengWu365/tomc-memory. CPU task-specific context preparation and explicitly saved local project notes through MCP. This page covers its MCPB bundle (https://github.com/ZipengWu365/TOMC/releases/download/v0.1.1-assistant-preview.1/tomc-memory-0.1.1.mcpb).

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

TOMC Memory scores 49 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 TOMC Memory MCP server expose?

TOMC Memory exposes 5 tools: prepare_context, remember_memory, recall_memory, list_memories, forget_memory. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.

### What licence is the TOMC Memory MCP server under?

TOMC Memory 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/ZipengWu365/TOMC
- Website: https://github.com/ZipengWu365/TOMC/blob/main/docs/assistant_plugin.md
- Changelog RSS feed: https://verifymcp.io/servers/zipengwu365-tomc-memory/tomc-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/zipengwu365-tomc-memory/tomc-memory.json
- HTML version of this page: https://verifymcp.io/servers/zipengwu365-tomc-memory/tomc-memory