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.n24q02m/mnemo-mcp

PYPI · MNEMO-MCP · SCANNED SEP 20

Persistent AI memory with hybrid search and embedded sync. Open, free, unlimited.

Available components

+15 this week 78 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 6 of 90 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency23
Schema Quality & AI Usability83
  • 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 1543 tokens (~102/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 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.n24q02m/mnemo-mcp server?

io.github.n24q02m/mnemo-mcp runs locally as a PyPI package, launched with uvx mnemo-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mnemo-mcp

# add to Claude Code
claude mcp add n24q02m-mnemo-mcp -- uvx mnemo-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "n24q02m-mnemo-mcp": {
      "command": "uvx",
      "args": [
        "mnemo-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "n24q02m-mnemo-mcp": {
      "command": "uvx",
      "args": [
        "mnemo-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add n24q02m-mnemo-mcp -- uvx mnemo-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "n24q02m-mnemo-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "mnemo-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add n24q02m-mnemo-mcp --command uvx --arg mnemo-mcp
# ~/.hermes/config.yaml
mcp_servers:
  n24q02m-mnemo-mcp:
    command: "uvx"
    args: ["mnemo-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "n24q02m-mnemo-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mnemo-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add n24q02m-mnemo-mcp -t stdio -c uvx -a mnemo-mcp
// mcp.json
{
  "mcpServers": {
    "n24q02m-mnemo-mcp": {
      "command": "uvx",
      "args": [
        "mnemo-mcp"
      ]
    }
  }
}
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 +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.

  • 19 Sept 26 +15
    • Malware scan: unverified → pass security
  • 18 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.

  • 17 Sept 26 −18
    • Malware scan: pass → unverified security
    • Known CVEs: pass → partial security
    • Stability: pass → 0.80 functional
    • Dependency health: 0.98 → partial functional
    • Package version: 2.15.8 → 2.15.13 functional
    • Package version: 2.15.8 → 2.15.12 functional
    • Package version: 2.15.8 → 2.15.11 functional
  • 16 Sept 26 +15
    • Stability: 0.97 → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: unverified → pass security
    • Stability: 0.97 → pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Schema quality: 100 → unverified functional
    • Package version: 2.15.7 → 2.15.8 functional
  • 15 Sept 26 +1
    • Package version: 2.15.5 → 2.15.7 functional
    • Package version: 2.15.5 → 2.15.6 functional
  • 14 Sept 26 0
    • Package version: 2.15.4 → 2.15.5 functional
  • 13 Sept 26 −14
    • Malware scan: pass → unverified security
    • Package version: 2.13.3 → 2.15.4 functional
    • Package version: 2.13.3 → 2.15.3 functional
    • Package version: 2.13.3 → 2.15.2 functional
    • Package version: 2.13.3 → 2.14.0 functional
    • Package version: 2.13.3 → 2.13.5 functional
    • Package version: 2.13.3 → 2.13.4 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 pypi/mnemo-mcp@2.15.13

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 90 packages
Packages resolved 90
Stale 5
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~1,523 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
add_memory ~74

Store NEW information. Use for preferences, decisions, facts. ACTION GUIDE — when to use: - Use when saving new information for the first time. Example: content='User prefers dark mode', category='preference', tags=['ui']

NameTypeReqDescription
category
contentstringyes
tags

Structured output declared, but exposes no named fields.

No examples provided.

archived_memories ~49

List archived memories. ACTION GUIDE — when to use: - Use to view memories that have been soft-deleted or automatically archived due to low importance/recency.

NameTypeReqDescription
limitinteger

Structured output declared, but exposes no named fields.

No examples provided.

config ~213

Server config, sync, setup, and bounded vector backfill. Actions: status|sync|set|warmup|setup_sync|backfill_embeddings. ACTION GUIDE — when to use each: - status: Show current configuration, setup status, and database stats. - sync: Trigger manual sync (requires sync_enabled=true + google_drive_client_id). - set: Update a setting. Requires 'key' and 'value'. Valid keys: 'sync_enabled' (true/false), 'sync_interval' (int), 'log_level' (str). Example: action='set', key='sync_enabled', value='true' - warmup: Pre-download embedding model (~570 MB) to avoid delays later. - backfill_embeddings: Embed active rows missing a current Vectorize ledger entry; optional batch_size is bounded to 100. - setup_sync: Authenticate Google Drive via Device Code OAuth flow.

NameTypeReqDescription
actionstringyes
batch_size
key
value

Structured output declared, but exposes no named fields.

No examples provided.

config__open_relay ~51

Get the relay configuration URL for mnemo-mcp, opening it in the user's browser when possible. Returns the relay URL, whether the browser launched, and the current status.

NameTypeReqDescription
ctxyes

Structured output declared, but exposes no named fields.

No examples provided.

consolidate_memories ~63

Summarize similar memories in a category (requires LLM API keys). ACTION GUIDE — when to use: - Use when a category has too many redundant or closely related memories and needs cleanup. Example: category='preference'

NameTypeReqDescription
categorystringyes

Structured output declared, but exposes no named fields.

No examples provided.

delete_memory ~56

Remove a memory by ID. ACTION GUIDE — when to use: - Use when a memory is completely outdated, incorrect, or explicitly requested to be forgotten. Example: memory_id='abc123'

NameTypeReqDescription
memory_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

export_memories ~39

Export all memories as JSONL. ACTION GUIDE — when to use: - Use when the user requests a backup or raw dump of their memory database.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

help ~55

Full documentation for memory and config tools. topic: 'memory' | 'config' ACTION GUIDE — when to use: - Use when you need detailed instructions on how to use specific server tools or features.

NameTypeReqDescription
topicstring
NameTypeReqDescription
resultstringyes

No examples provided.

import_memories ~72

Import memories from JSONL data or a list of objects. ACTION GUIDE — when to use: - Use when restoring from a backup or migrating data into the memory system. Example: data='[{"content": "example"}]', mode='merge'

NameTypeReqDescription
datayes
modestring

Structured output declared, but exposes no named fields.

No examples provided.

list_memories ~70

Browse all memories, optionally filtered by category. ACTION GUIDE — when to use: - Use when you want to view a broad set of memories, or see what's in a specific category. Example: category='preference', limit=10

NameTypeReqDescription
category
limitinteger

Structured output declared, but exposes no named fields.

No examples provided.

memory ~516

[DEPRECATED — use the granular tools (add_memory, search_memory, ...) instead; this composite tool will be removed in a future release] Legacy dispatcher for backward compatibility. Use specialized tools (add_memory, search_memory, etc.) instead. Persistent memory store. Actions: add|search|list|update|delete|export|import|stats|restore|archived|consolidate. ACTION GUIDE — when to use each: - add: Store NEW information. Requires 'content'. Use when saving preferences, decisions, facts for the first time. Example: action='add', content='User prefers dark mode', category='preference', tags=['ui'] - search: Find existing memories by natural language query. Requires 'query'. Use BEFORE add to avoid duplicates. Example: action='search', query='dark mode preference' - update: Modify an EXISTING memory by ID. Requires 'memory_id' (from search/list results). Use when a fact changes. Example: action='update', memory_id='abc123', content='User now prefers light mode' - list: Browse all memories, optionally filtered by category. No query needed. - delete: Remove a memory by ID. Requires 'memory_id'. - stats: Show database statistics (total memories, categories, embedding status). - export: Export all memories to JSONL format. - import: Import memories from JSONL data. Requires 'data'. - archived: List archived memories. Optionally filter by limit. - restore: Restore an archived memory by ID. Requires 'memory_id'. - consolidate: Summarize and consolidate similar memories in a category using LLM. Requires 'category'. WORKFLOW: search -> not found? -> add. Found outdated? -> update (with memory_id from results). PROACTIVE: save user preferences, decisions, corrections, project conventions.

NameTypeReqDescription
actionstringyes
as_of
autoboolean
category
content
context_typestring
data
depthinteger
entity_id
importance
include_archivedboolean
limitinteger
memory_id
min_importancenumber
modestring
name
query
since
source
tags
text
until

Structured output declared, but exposes no named fields.

No examples provided.

memory_stats ~50

Show database statistics (total memories, categories, embedding status). ACTION GUIDE — when to use: - Use when you need to understand the scale or health of the memory database, or check if embeddings are enabled.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

restore_memory ~54

Restore an archived memory by ID. ACTION GUIDE — when to use: - Use to bring a previously archived memory back into the active search pool. Example: memory_id='abc123'

NameTypeReqDescription
memory_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

search_memory ~71

Find existing memories by natural language query. Always search before adding. ACTION GUIDE — when to use: - Use BEFORE adding new information to avoid duplicates. Example: query='dark mode preference'

NameTypeReqDescription
category
limitinteger
querystringyes
tags

Structured output declared, but exposes no named fields.

No examples provided.

update_memory ~90

Modify an EXISTING memory by ID. Get memory_id from search results. ACTION GUIDE — when to use: - Use when an existing fact or preference changes. Example: memory_id='abc123', content='User now prefers light mode'

NameTypeReqDescription
category
content
importance
memory_idstringyes
source
tags

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the io.github.n24q02m/mnemo-mcp server?

io.github.n24q02m/mnemo-mcp is listed in the public MCP registry as io.github.n24q02m/mnemo-mcp. Persistent AI memory with hybrid search and embedded sync. Open, free, unlimited. This page covers its PyPI package (mnemo-mcp).

Is the io.github.n24q02m/mnemo-mcp server safe to use?

io.github.n24q02m/mnemo-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.n24q02m/mnemo-mcp server expose?

io.github.n24q02m/mnemo-mcp exposes 15 tools: add_memory, search_memory, list_memories, update_memory, delete_memory, and 10 more. Their descriptions and schemas cost roughly 1,523 tokens of context every time the server is loaded.

Is the io.github.n24q02m/mnemo-mcp server still maintained?

io.github.n24q02m/mnemo-mcp 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.n24q02m/mnemo-mcp server under?

io.github.n24q02m/mnemo-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.