io.github.memtomem/memtomem
io-github-memtomem-memtomem declares 9 capabilities across 9 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
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.
3 tools can modify data and declare no limit.
6 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
mem_index | read |
inferred |
mem_add | write |
inferred |
mem_recall | write |
inferred |
mem_search | read |
inferred |
mem_stats | read |
inferred |
mem_status | read |
inferred |
mem_list | read |
inferred |
mem_read | read |
inferred |
mem_do | write |
assumed |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-27 | 26 | tools/list answered by the PyPI package memtomem==0.7.0 (published to PyPI as memtomem, listed in the official MCP registry as io.github.memtomem/memtomem 0.7.0), 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.