Evergences — Memos, Content and Shared Memory
io-github-seanmeverett-evergences 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.
9 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
search_content | read |
declared |
get_content_updates | read |
declared |
list_memos | read |
declared |
read_memo | read |
declared |
read_content | read |
declared |
list_capabilities | read |
declared |
search_memories | read |
declared |
read_memory | read |
declared |
read_memory_context | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 16 | tools/list on https://evergences.com/api/mcp/, published in the official MCP registry as io.github.seanmeverett/evergences 1.0.0 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.