# io.github.baodq06/memocall (npm · memocall)

Recall past Claude Code conversations from any project as clean, compact Markdown.

- Trust score: 70/100 (medium)
- Change this week: +25
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `memocall`: 70/100 (this document), [markdown](https://verifymcp.io/servers/baodq06-memocall/memocall.md), [page](https://verifymcp.io/servers/baodq06-memocall/memocall)

## Channel facts

- Registry: `npm`
- Package: `memocall`
- Version: `0.1.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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 45 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 697 tokens (~139/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add baodq06-memocall -- npx -y memocall
```

### Codex

```bash
codex mcp add baodq06-memocall -- npx -y memocall
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add baodq06-memocall --command npx --arg -y --arg memocall
```

### Hermes

```yaml
mcp_servers:
  baodq06-memocall:
    command: "npx"
    args: ["-y", "memocall"]
```

### Other

```json
{
  "mcpServers": {
    "baodq06-memocall": {
      "command": "npx",
      "args": [
        "-y",
        "memocall"
      ]
    }
  }
}
```

## 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-08-03 (score 70, +1)

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

### 2026-08-02 (score 69, +49)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 20, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 27, +3)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-30 (score 24, −21)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 45)

First indexed and scored.

## MCP tools (5)

### `list_sessions` (~93 tokens)

List recent Claude Code sessions

List your recent Claude Code conversations across ALL projects, grouped by project directory. Use this to answer 'what sessions have I worked on recently?' or to find a past session before loading it. Returns each session's title, date, turn count, and id.

Input parameters:

- `cwd` (string): Optional: only show sessions whose project path contains this substring.
- `limit` (integer): Max sessions to list (default 40).

### `search_sessions` (~101 tokens)

Search past Claude Code sessions

Search your past Claude Code conversations (across all projects) by keyword — matches session titles, first messages, and project paths. Use when the user refers to a past conversation by topic (e.g. 'the session where we set up the license system'). Returns matching sessions with their ids.

Input parameters:

- `limit` (integer): Max results (default 20).
- `query` (string, required): Keyword(s) to search for in titles / first messages / project paths.

### `load_session` (~252 tokens)

Load a past Claude Code conversation

Load the context of a past Claude Code conversation as compact Markdown (human turns, collapsed tool-call summaries, and assistant replies — tool outputs are elided). Provide either a session `id` (from list_sessions/search_sessions) or a free-text `query` to find it. Use this to pull a previous conversation's context into the current session. For a very large session, either pass `turns` to load a specific window (turn numbers come from session_outline), or prefer session_outline / search_in_session.

Input parameters:

- `format` (string): compact (default): elide tool details. full: include brief tool inputs.
- `id` (string): Session id (uuid) from list_sessions/search_sessions.
- `includeThinking` (boolean): Include a short trace of assistant thinking (default false).
- `maxTokens` (integer): Approx token budget for the returned transcript (default 16000, capped ~18000).
- `query` (string): Free-text to locate the session if you don't have an id.
- `turns` (string): Load only a turn range, 1-based inclusive: "300-340", "300-", "-50", or "300". Turn numbers come from session_outline.

### `session_outline` (~110 tokens)

Outline a past conversation

Get a quick MAP of a past Claude Code conversation: the numbered list of the user's prompts, one line each. Very cheap even for huge sessions. Use this to see what a session covered, or to find which turn numbers to then load with load_session's `turns`. Identify the session by `id` or free-text `query`.

Input parameters:

- `id` (string): Session id from list_sessions/search_sessions.
- `query` (string): Free-text to locate the session if you don't have an id.

### `search_in_session` (~141 tokens)

Search within a past conversation

Find specific turns WITHIN one past Claude Code conversation by keyword — returns only the matching turns (with their turn numbers). Use when the user asks what was decided or discussed about a topic inside a known or large session (e.g. 'what did we decide about retries in that session'). Pick the session by `id` or `session` (free-text); `query` is the keyword to find inside it.

Input parameters:

- `id` (string): Session id from list_sessions/search_sessions.
- `query` (string, required): Keyword(s) to find inside the session.
- `session` (string): Free-text to locate the session if you don't have an id.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/baodq06-memocall/memocall#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 20
- 2026-07-31: 27
- 2026-07-30: 24
- 2026-07-28: 45
- 2026-07-27: 45

## Links

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