memory-decay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_STORAGE_PATH | No | Optional environment variable to set the directory where the vector database and journal file are stored. Defaults to ./data relative to the working directory. | ./data |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_memoryA | |
| recall_memoryA | Retrieves memories based on semantic relevance and decay. Successfully recalled memories receive a 'Hebbian boost', refreshing their strength. |
| verify_historyA | Bypasses decay to search the immutable Archive. Use for audit or when recall fails. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: store_memory writes, recall_memory retrieves with decay, and verify_history accesses the immutable archive. No two tools overlap in functionality.
All tool names follow the consistent verb_noun pattern (store_memory, recall_memory, verify_history), making the API predictable and easy to navigate.
With only 3 tools, the server is tightly scoped to its core purpose of memory storage, recall, and archival verification. Each tool earns its place and the count is within the ideal 3-15 range.
The core memory lifecycle (store, recall, verify) is covered well, and decay handles forgetting implicitly. However, there is no explicit update or delete operation, which could be considered a minor gap for full lifecycle management.