memory-boost
io-github-arnaugonzalez-memory-boost declares 9 capabilities across 9 tools, with 1 critical issue.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
5 tools can modify data and declare no limit.
4 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
memory_brief | write |
assumed |
memory_recall | read |
inferred |
memory_page | read |
inferred |
memory_save | write |
assumed |
memory_shelf | read |
inferred |
memory_checkpoint | write |
assumed |
memory_resume | read |
inferred |
memory_drift | write |
assumed |
memory_lesson | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-15 | 31 | tools/list answered by the PyPI package memory-boost==0.1.1 (published to PyPI as memory-boost, listed in the official MCP registry as io.github.arnaugonzalez/memory-boost 0.1.1), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.