TOMC Memory
MCPB · TOMC-MEMORY-0.1.1.MCPB
CPU task-specific context preparation and explicitly saved local project notes through MCP.
Available components
Last scanned (18 hours ago)
Scores higher than 79% of MCPB servers
Category Memory and Knowledge
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. How we score → Why this is hard to score →
Supply Chain Security13
- 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.Unverified
- Known CVEs were checked across the 29 of 29 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Install-script risk not yet assessed.Unverified
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 25 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
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 4 Nov 2026 · Analysed mcpb/https://github.com/ZipengWu365/TOMC/releases/download/v0.1.1-assistant-preview.1/tomc-memory-0.1.1.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
forget_memory ~35
Delete one exact named notebook when the user asks to forget it. Cannot be undone through this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
list_memories ~26
Find saved notebook names. Returns names, entry counts and update times, without content.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prepare_context ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | – | – |
| history | string | yes | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
recall_memory ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | – | – | – |
| name | string | yes | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
remember_memory ~52
Optionally save user-authorized history as text or message JSON to a named notebook. Appends; preserves earlier entries. Use one name per topic.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
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.
mcpb · tomc-memory-0.1.1.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be
macOS / Linux
echo "f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be tomc-memory-0.1.1.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\tomc-memory-0.1.1.mcpb).Hash -eq "f1186ac6cd146fd71a27e4444e189e398b894985a2d5fc66c8ca3a7a599512be"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
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.