io.github.tinhien11/tdai-memory-mcp
NPM · TDAI-MEMORY-MCP
Local-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec.
Available components
Last scanned (5 hours ago)
Scores higher than 81% of npm servers
Category Memory and Knowledge
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 Security99
- 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
- 43 of 167 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 81 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 839 tokens (~104/item across 8 items; 6 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "forget" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 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
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −3
- Stability: pass → 0.83 functional
- 14 Oct 26 +1
- 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 5 Nov 2026 · Analysed npm/tdai-memory-mcp@0.3.0
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 167 packages
| Packages resolved | 167 |
|---|---|
| Stale | 43 |
| 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 →
adr ~192
Record an Architecture Decision Record (ADR). Use this tool when you make a technical decision that future agents should know about. The ADR is stored as a structured capture and can be recalled by any agent working on the same project.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | Other options that were considered but rejected. Include why each was rejected. |
| consequences | string | – | The consequences of this decision. What are the trade-offs, risks, and benefits? |
| context | string | yes | The problem or situation that requires a decision. Why is this decision needed? |
| decision | string | yes | The decision that was made. What was chosen? |
| session_key | string | – | The session key. The default is hash(cwd). |
| tags | array | – | Optional tags for filtering. Example: ['arch', 'storage']. |
| title | string | yes | A short title for the decision. Example: 'Use SQLite for local storage'. |
No output schema declared.
No examples provided.
capture ~117
Save a decision, a learning, or a task outcome to memory. Call this tool after you complete a non-trivial task, make a decision, or fix a bug with a known root cause.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text to remember. The tool redacts secrets before it stores the text. |
| metadata | object | – | Optional metadata. |
| session_key | string | – | The session key. The default is hash(cwd). |
| tags | array | – | Optional tags. |
| type | string | yes | The type of the memory. |
No output schema declared.
No examples provided.
forget ~65
Delete specific memory entries. Use this tool only when the user requests a deletion. Do not auto-forget.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | Set this to true to execute the deletion. |
| filter | object | – | – |
| id | string | – | The ID of the capture to delete. |
No output schema declared.
No examples provided.
handoff ~213
Write a structured handoff packet for the next agent session. Call this tool at the end of a session, or before you switch to a different agent. The next agent calls recall to load this packet and continue without re-reading files. This saves 60-85% of tokens compared to re-discovering context.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | array | – | A list of decisions made during this session. Include what was chosen and why. |
| files | array | – | A list of files that matter for this task. Use the format: path:lines - reason. |
| next_steps | array | – | A list of next steps for the next agent. Order by priority. |
| progress | string | yes | A summary of what has been done so far. Include the root cause if this is a bug fix. |
| session_key | string | – | The session key. The default is hash(cwd). |
| status | string | yes | The current status of the task. |
| task | string | yes | A one-line description of the task. |
No output schema declared.
No examples provided.
recall ~163
Retrieve relevant past memory. Call this tool before you answer the user. Use it when the user references past work or when the task needs project context.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | The maximum number of results. |
| max_tokens | integer | – | The maximum number of tokens in the response. If the result exceeds this value, the tool truncates the text. |
| mode | string | – | The search mode. |
| offset | integer | – | The pagination offset. Use this to get the next page of results. |
| query | string | yes | A natural language query. The tool uses this text for the BM25 search and the vector search. |
| session_key | string | – | The session key. The default is hash(cwd). Use this to recall memory from a different project. |
No output schema declared.
No examples provided.
search ~64
Search memory by keyword or by semantic similarity. Use this tool when recall is too broad and you need specific facts.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | – | – |
| limit | integer | – | – |
| mode | string | – | The search mode. |
| query | string | yes | The search text. |
No output schema declared.
No examples provided.
How do I install the io.github.tinhien11/tdai-memory-mcp server?
io.github.tinhien11/tdai-memory-mcp runs locally as an npm package, launched with npx -y tdai-memory-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tdai-memory-mcp
claude mcp add tinhien11-tdai-memory-mcp -- npx -y tdai-memory-mcp
What is the io.github.tinhien11/tdai-memory-mcp server?
io.github.tinhien11/tdai-memory-mcp is listed in the public MCP registry as io.github.tinhien11/tdai-memory-mcp. Local-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec. This page covers its npm package (tdai-memory-mcp).
Is the io.github.tinhien11/tdai-memory-mcp server safe to use?
io.github.tinhien11/tdai-memory-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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.tinhien11/tdai-memory-mcp server expose?
io.github.tinhien11/tdai-memory-mcp exposes 6 tools: recall, capture, search, forget, handoff, adr. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.
Is the io.github.tinhien11/tdai-memory-mcp server still maintained?
io.github.tinhien11/tdai-memory-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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.tinhien11/tdai-memory-mcp server under?
io.github.tinhien11/tdai-memory-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.