Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.baodq06/memocall

NPM · MEMOCALL · SCANNED SEP 20

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

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

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
  • 31 of 96 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 93 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the io.github.baodq06/memocall MCP server?

io.github.baodq06/memocall runs locally as an npm package, launched with npx -y memocall. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · memocall

# add to Claude Code
claude mcp add baodq06-memocall -- npx -y memocall
// .cursor/mcp.json
{
  "mcpServers": {
    "baodq06-memocall": {
      "command": "npx",
      "args": [
        "-y",
        "memocall"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "baodq06-memocall": {
      "command": "npx",
      "args": [
        "-y",
        "memocall"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add baodq06-memocall --command npx --arg -y --arg memocall
# ~/.hermes/config.yaml
mcp_servers:
  baodq06-memocall:
    command: "npx"
    args: ["-y", "memocall"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "baodq06-memocall": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "memocall"
      ]
    }
  }
}
# add to Vellum
assistant mcp add baodq06-memocall -t stdio -c npx -a -y memocall
// mcp.json
{
  "mcpServers": {
    "baodq06-memocall": {
      "command": "npx",
      "args": [
        "-y",
        "memocall"
      ]
    }
  }
}
Changelog

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 0
    • Security disclosure: fail → unverified functional
  • 19 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.

  • 18 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 17 Sept 26 +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.

  • 16 Sept 26 −3
    • Security disclosure: fail → unverified functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 0
    • Security disclosure: fail → unverified functional
Diagnostics

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/memocall@0.1.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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~697 tokens

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 →

Tool Tokens
list_sessions ~93

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.

NameTypeReqDescription
cwdstringOptional: only show sessions whose project path contains this substring.
limitintegerMax sessions to list (default 40).

No output schema declared.

No examples provided.

load_session ~252

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.

NameTypeReqDescription
formatstringcompact (default): elide tool details. full: include brief tool inputs.
idstringSession id (uuid) from list_sessions/search_sessions.
includeThinkingbooleanInclude a short trace of assistant thinking (default false).
maxTokensintegerApprox token budget for the returned transcript (default 16000, capped ~18000).
querystringFree-text to locate the session if you don't have an id.
turnsstringLoad only a turn range, 1-based inclusive: "300-340", "300-", "-50", or "300". Turn numbers come from session_outline.

No output schema declared.

No examples provided.

search_in_session ~141

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.

NameTypeReqDescription
idstringSession id from list_sessions/search_sessions.
querystringyesKeyword(s) to find inside the session.
sessionstringFree-text to locate the session if you don't have an id.

No output schema declared.

No examples provided.

search_sessions ~101

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.

NameTypeReqDescription
limitintegerMax results (default 20).
querystringyesKeyword(s) to search for in titles / first messages / project paths.

No output schema declared.

No examples provided.

session_outline ~110

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

NameTypeReqDescription
idstringSession id from list_sessions/search_sessions.
querystringFree-text to locate the session if you don't have an id.

No output schema declared.

No examples provided.

Common questions

What is the io.github.baodq06/memocall MCP server?

io.github.baodq06/memocall is an MCP server listed in the public MCP registry as io.github.baodq06/memocall. Recall past Claude Code conversations from any project as clean, compact Markdown. This page covers its npm package (memocall).

Is the io.github.baodq06/memocall MCP server safe to use?

io.github.baodq06/memocall scores 83 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.baodq06/memocall MCP server expose?

io.github.baodq06/memocall exposes 5 tools: list_sessions, search_sessions, load_session, session_outline, search_in_session. Their descriptions and schemas cost roughly 697 tokens of context every time the server is loaded.

Is the io.github.baodq06/memocall MCP server still maintained?

io.github.baodq06/memocall 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.baodq06/memocall MCP server under?

io.github.baodq06/memocall declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.