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

io.github.baodq06/memocall

NPM · MEMOCALL · SCANNED AUG 3

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

Available components

+25 this week 70 Trust /100
Trust breakdown (6 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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
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 Management27
  • Stability observed for 8 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · memocall

# add to Claude Code
claude mcp add baodq06-memocall -- npx -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"]
// 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.

  • 3 Aug 26 +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.

  • 2 Aug 26 +49
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Licence: MIT functional
  • 1 Aug 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 +3
    • Malware scan: pass → unverified security
    • Tool coverage: unverified → 100 functional
  • 30 Jul 26 −21
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 45

    First indexed and scored.

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

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.