# 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.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `tdai-memory-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/tinhien11-tdai-memory-mcp/tdai-memory-mcp.md), [page](https://verifymcp.io/servers/tinhien11-tdai-memory-mcp/tdai-memory-mcp)

## Channel facts

- Registry: `npm`
- Package: `tdai-memory-mcp`
- Version: `0.3.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 44 of 170 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 36 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 839 tokens (~104/item across 8 items; 6 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add tinhien11-tdai-memory-mcp -- npx -y tdai-memory-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "tinhien11-tdai-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tdai-memory-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tinhien11-tdai-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tdai-memory-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add tinhien11-tdai-memory-mcp -- npx -y tdai-memory-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tinhien11-tdai-memory-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tdai-memory-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tinhien11-tdai-memory-mcp --command npx --arg -y --arg tdai-memory-mcp
```

### Hermes

```yaml
mcp_servers:
  tinhien11-tdai-memory-mcp:
    command: "npx"
    args: ["-y", "tdai-memory-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "tinhien11-tdai-memory-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "tdai-memory-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add tinhien11-tdai-memory-mcp -t stdio -c npx -a -y tdai-memory-mcp
```

### Other

```json
{
  "mcpServers": {
    "tinhien11-tdai-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tdai-memory-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 82, +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.

### 2026-09-17 (score 81, 0)

- [security improvement] GHSA-rgj7-g3m4-5g8c no longer affects this package
- [security improvement] GHSA-f88m-g3jw-g9cj no longer affects this package
- [security improvement] CVE-2026-39244 no longer affects this package
- [security improvement] Known CVEs: fail → pass
- [functional] Stability: pass → 0.80

### 2026-09-16 (score 81, 0)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 81, +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.

### 2026-09-13 (score 80, +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.

### 2026-09-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 78, −3)

- [functional] Stability: pass → 0.80

## MCP tools (6)

### `recall` (~163 tokens)

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.

Input parameters:

- `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, required): 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.

### `capture` (~117 tokens)

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.

Input parameters:

- `content` (string, required): 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, required): The type of the memory.

### `search` (~64 tokens)

Search memory by keyword or by semantic similarity. Use this tool when recall is too broad and you need specific facts.

Input parameters:

- `filters` (object)
- `limit` (integer)
- `mode` (string): The search mode.
- `query` (string, required): The search text.

### `forget` (~65 tokens)

Delete specific memory entries. Use this tool only when the user requests a deletion. Do not auto-forget.

Input parameters:

- `confirm` (boolean): Set this to true to execute the deletion.
- `filter` (object)
- `id` (string): The ID of the capture to delete.

### `handoff` (~213 tokens)

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.

Input parameters:

- `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, required): 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, required): The current status of the task.
- `task` (string, required): A one-line description of the task.

### `adr` (~192 tokens)

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.

Input parameters:

- `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, required): The problem or situation that requires a decision. Why is this decision needed?
- `decision` (string, required): 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, required): A short title for the decision. Example: 'Use SQLite for local storage'.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/tinhien11-tdai-memory-mcp/tdai-memory-mcp#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 81
- 2026-09-08: 81
- 2026-09-07: 80
- 2026-09-06: 80
- 2026-09-05: 79
- 2026-09-04: 79
- 2026-09-03: 78
- 2026-09-02: 78
- 2026-09-01: 77
- 2026-08-31: 77
- 2026-08-30: 76
- 2026-08-29: 76
- 2026-08-28: 75
- 2026-08-27: 75
- 2026-08-26: 74
- 2026-08-25: 75
- 2026-08-24: 74
- 2026-08-23: 74

## Common questions

### 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 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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.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 21 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.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.

## Links

- npm package: https://www.npmjs.com/package/tdai-memory-mcp
- Socket report: https://socket.dev/npm/package/tdai-memory-mcp
- Repository: https://github.com/tinhien11/tdai-memory-mcp
- Changelog RSS feed: https://verifymcp.io/servers/tinhien11-tdai-memory-mcp/tdai-memory-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tinhien11-tdai-memory-mcp/tdai-memory-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tinhien11-tdai-memory-mcp/tdai-memory-mcp