io.github.davidmosiah/delx-memory
NPM · DELX-MEMORY · SCANNED SEP 20
Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 52 of 130 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
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 22 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability85
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 806 tokens (~100/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 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
How do I install the io.github.davidmosiah/delx-memory MCP server?
io.github.davidmosiah/delx-memory runs locally as an npm package, launched with npx -y delx-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · delx-memory
claude mcp add davidmosiah-delx-memory -- npx -y delx-memory
{
"mcpServers": {
"davidmosiah-delx-memory": {
"command": "npx",
"args": [
"-y",
"delx-memory"
]
}
}
} {
"servers": {
"davidmosiah-delx-memory": {
"command": "npx",
"args": [
"-y",
"delx-memory"
]
}
}
} codex mcp add davidmosiah-delx-memory -- npx -y delx-memory
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"davidmosiah-delx-memory": {
"type": "local",
"command": [
"npx",
"-y",
"delx-memory"
],
"enabled": true
}
}
} openclaw mcp add davidmosiah-delx-memory --command npx --arg -y --arg delx-memory
mcp_servers:
davidmosiah-delx-memory:
command: "npx"
args: ["-y", "delx-memory"] {
"McpServers": {
"davidmosiah-delx-memory": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"delx-memory"
]
}
}
} assistant mcp add davidmosiah-delx-memory -t stdio -c npx -a -y delx-memory
{
"mcpServers": {
"davidmosiah-delx-memory": {
"command": "npx",
"args": [
"-y",
"delx-memory"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 13 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/delx-memory@0.2.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Deprecated | 1 |
| Stale | 51 |
| 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 →
memory_export Export memory contents (requires explicit_user_intent) ~147
Dump the memory store as JSON, JSONL, or Markdown. Optional since/until window on updated_at. Use for backup/inspection. Requires explicit_user_intent: true.
| Name | Type | Req | Description |
|---|---|---|---|
| explicit_user_intent | boolean | yes | Must be true. Set ONLY when the current user message explicitly asks the agent to modify memory (set/forget/export). Do not infer intent. |
| format | string | yes | Output format: json (single object), jsonl (one entry per line), markdown (human-friendly). |
| since | integer | – | Unix ms timestamp — include only entries with updated_at >= since. |
| until | integer | – | Unix ms timestamp — include only entries with updated_at <= until. |
No output schema declared.
No examples provided.
memory_forget Delete one memory entry (requires explicit_user_intent) ~98
Delete a single key from memory. Idempotent: returns existed=false if the key was not present. Requires explicit_user_intent: true.
| Name | Type | Req | Description |
|---|---|---|---|
| explicit_user_intent | boolean | yes | Must be true. Set ONLY when the current user message explicitly asks the agent to modify memory (set/forget/export). Do not infer intent. |
| key | string | yes | Stable identifier for the memory entry. Free-form text. Treat as case-sensitive. |
No output schema declared.
No examples provided.
memory_forget_by_tag Bulk-delete entries by tag (requires explicit_user_intent) ~80
Delete every entry carrying the given tag. Returns deleted_count. Requires explicit_user_intent: true.
| Name | Type | Req | Description |
|---|---|---|---|
| explicit_user_intent | boolean | yes | Must be true. Set ONLY when the current user message explicitly asks the agent to modify memory (set/forget/export). Do not infer intent. |
| tag | string | yes | Tag to bulk-delete. |
No output schema declared.
No examples provided.
memory_get Get one memory entry by key ~54
Exact key lookup. Returns the stored value plus timestamps, ttl, tags, metadata. Returns null if missing or expired.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Stable identifier for the memory entry. Free-form text. Treat as case-sensitive. |
No output schema declared.
No examples provided.
memory_list List memory keys (not values) ~82
List keys with optional prefix or tag filter. Returns keys + timestamps + tags only — call memory_get for values. Use this first on a new session to discover what is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max keys to return. |
| prefix | string | – | Only return keys starting with this string. |
| tag | string | – | Only return keys carrying this tag. |
No output schema declared.
No examples provided.
memory_search Keyword search across keys and values ~118
Full-text search across keys, values AND tags. Uses an FTS5 index with bm25 relevance ranking (key-weighted), word-stemming, diacritic folding and prefix matching — so multi-word, partial and accent-insensitive queries all hit, ranked by relevance. Falls back to a LIKE substring scan if the SQLite build lacks FTS5. Returns top N matches with a snippet. Case-insensitive.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches to return. |
| query | string | yes | Keyword query. Matched against keys and values. |
No output schema declared.
No examples provided.
memory_set Upsert a memory entry (requires explicit_user_intent) ~190
Create or update a key in memory. Rejects credential-shaped keys or values. Requires explicit_user_intent: true. Returns whether the row was created or updated.
| Name | Type | Req | Description |
|---|---|---|---|
| explicit_user_intent | boolean | yes | Must be true. Set ONLY when the current user message explicitly asks the agent to modify memory (set/forget/export). Do not infer intent. |
| key | string | yes | Stable identifier for the memory entry. Free-form text. Treat as case-sensitive. |
| metadata | object | – | Optional small JSON object with provenance/notes. Subject to same secret-detection rules. |
| tags | array | – | Optional list of tags for grouping/filter/bulk-delete. |
| ttl_seconds | integer | – | Optional TTL in seconds. After this, the entry is lazy-deleted on next read. |
| value | – | yes | The value to store. Will be JSON-serialized. Rejected if it looks like a credential. |
No output schema declared.
No examples provided.
memory_stats Memory store stats ~37
High-level stats about the local memory store. Safe to call first on every session to gauge whether the store is empty, small, or large.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.davidmosiah/delx-memory MCP server?
io.github.davidmosiah/delx-memory is an MCP server listed in the public MCP registry as io.github.davidmosiah/delx-memory. Local-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safe. This page covers its npm package (delx-memory).
Is the io.github.davidmosiah/delx-memory MCP server safe to use?
io.github.davidmosiah/delx-memory scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.davidmosiah/delx-memory MCP server expose?
io.github.davidmosiah/delx-memory exposes 8 tools: memory_get, memory_list, memory_search, memory_stats, memory_set, and 3 more. Their descriptions and schemas cost roughly 806 tokens of context every time the server is loaded.
Is the io.github.davidmosiah/delx-memory MCP server still maintained?
io.github.davidmosiah/delx-memory is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.davidmosiah/delx-memory MCP server under?
io.github.davidmosiah/delx-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.