Is io.github.mnemoverse/mcp-memory-server safe to use?

io.github.mnemoverse/mcp-memory-server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.mnemoverse/mcp-memory-server?

io.github.mnemoverse/mcp-memory-server can be installed by cloning its GitHub repository and following the setup instructions in the README.

Is io.github.mnemoverse/mcp-memory-server actively maintained?

io.github.mnemoverse/mcp-memory-server is actively maintained — last commit was 2 days ago.

io.github.mnemoverse/mcp-memory-server

Persistent memory across Claude, Cursor, ChatGPT, VS Code. Importance scoring, linked recall.

ActiveNot tested

AI / ML

GitHub

28DNo CVEsactive

Quick Install

{
  "mcpServers": {
    "io-github-mnemoverse-mcp-memory-server": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Setup guide

No install config available. Check the server's README for setup instructions.

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-mnemoverse-mcp-memory-server)](https://mcppedia.org/s/io-github-mnemoverse-mcp-memory-server)

Should you use this server?

Persistent memory across Claude, Cursor, ChatGPT, VS Code. Importance scoring, linked recall.

✓

Is it safe?

No package registry to scan.

No authentication — any process on your machine can connect.

License not specified.

✓

Is it maintained?

Last commit 2 days ago.

Will it work with my client?

Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

README

@mnemoverse/mcp-memory-server

Shared AI memory across Claude, Cursor, VS Code, ChatGPT, and any MCP client. Write once, recall anywhere.

Your agent remembers everything — across sessions, projects, and tools. One API key, one memory, everywhere.

Quick Start

1. Get a free API key

2. Connect to your AI tool

Claude Code — add via CLI:

claude mcp add mnemoverse \
  -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY \
  -- npx -y @mnemoverse/mcp-memory-server@latest

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

VS Code — add to .vscode/mcp.json (note: VS Code uses servers, not mcpServers):

{
  "servers": {
    "mnemoverse": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

Windsurf — add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

Why @latest? Bare npx @mnemoverse/mcp-memory-server is cached indefinitely by npm and stops re-checking the registry. The @latest suffix forces a metadata lookup on every Claude Code / Cursor / VS Code session start (~100-300ms), so you always pick up new releases.

⚠️ Restart your AI client after editing the config. MCP servers are only picked up on client startup.

3. Try it — 30 seconds to verify it works

Paste this in your AI chat:

"Remember that my favourite TypeScript framework is Hono, and please call memory_write to save it."

Your agent should call memory_write and confirm the memory was stored.

Then open a new chat / new session (this is the whole point — memory survives restarts), and ask:

"What's my favourite TypeScript framework?"

Your agent should call memory_read, find the entry, and answer "Hono". If it does — you're wired up. Write whatever you want next.

If it doesn't remember: check that the client was fully restarted and the config has your real mk_live_... key, not the placeholder.

Tools

Tool	What it does
`memory_write`	Store a memory — insight, preference, lesson learned
`memory_read`	Search memories by natural language query
`memory_feedback`	Rate memories as helpful or not (improves future recall)
`memory_stats`	Check how many memories stored, which domains exist
`memory_delete`	Permanently delete a single memory by `atom_id`
`memory_delete_domain`	Wipe an entire domain (requires `confirm: true` safety interlock)

Ideas: What to Remember

User preferences: "I use dark mode", "I prefer Tailwind over CSS modules

... View full README on GitHub

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Score Breakdown

MCPpedia Score

Click each category to see evidence

28D

Last scored 6h ago

How we score →

Security

3/30

No known vulnerabilities.

○

Known CVEs — No package registry to scan

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

✓

Tool stability — Tool definitions stable

○

Dependency health — No package to analyze

✗

License — No license specified

○

Authentication — No authentication required

○

Repository — active repo

CVEs checked daily via OSV.dev. Score algorithm is open source.

Reviews

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.mnemoverse/mcp-memory-server safe to use?: io.github.mnemoverse/mcp-memory-server has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.mnemoverse/mcp-memory-server?: io.github.mnemoverse/mcp-memory-server can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with io.github.mnemoverse/mcp-memory-server?: io.github.mnemoverse/mcp-memory-server is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.
Is io.github.mnemoverse/mcp-memory-server actively maintained?: io.github.mnemoverse/mcp-memory-server is actively maintained — last commit was 2 days ago.

Similar servers

View all →

Sequential Thinking MCP Server

Official

No CVEs98A

Dynamic problem-solving through sequential thought chains

1 toolsstdio83.8k111.0k/wk1d ago

XcodeBuildMCP

Official

No CVEs97A

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

2 toolsremote5.2k46.6k/wk1d ago

Python Sdk

Official

No CVEs95A

The official Python SDK for Model Context Protocol servers and clients

1 toolsremote22.6k156.5k/wk21h ago

Gemini Cli

No CVEs95A

An open-source AI agent that brings the power of Gemini directly into your terminal.

8 toolsremote101.3k814.6k/wk12h ago

MCP Security Weekly

Get CVE alerts and security updates for io.github.mnemoverse/mcp-memory-server and similar servers.

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

@mnemoverse/mcp-memory-server

Shared AI memory across Claude, Cursor, VS Code, ChatGPT, and any MCP client. Write once, recall anywhere.

Your agent remembers everything — across sessions, projects, and tools. One API key, one memory, everywhere.

Quick Start

1. Get a free API key

2. Connect to your AI tool

Claude Code — add via CLI:

claude mcp add mnemoverse \
  -e MNEMOVERSE_API_KEY=mk_live_YOUR_KEY \
  -- npx -y @mnemoverse/mcp-memory-server@latest

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

VS Code — add to .vscode/mcp.json (note: VS Code uses servers, not mcpServers):

{
  "servers": {
    "mnemoverse": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

Windsurf — add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

Why @latest? Bare npx @mnemoverse/mcp-memory-server is cached indefinitely by npm and stops re-checking the registry. The @latest suffix forces a metadata lookup on every Claude Code / Cursor / VS Code session start (~100-300ms), so you always pick up new releases.

⚠️ Restart your AI client after editing the config. MCP servers are only picked up on client startup.

3. Try it — 30 seconds to verify it works

Paste this in your AI chat:

"Remember that my favourite TypeScript framework is Hono, and please call memory_write to save it."

Your agent should call memory_write and confirm the memory was stored.

Then open a new chat / new session (this is the whole point — memory survives restarts), and ask:

"What's my favourite TypeScript framework?"

Your agent should call memory_read, find the entry, and answer "Hono". If it does — you're wired up. Write whatever you want next.

If it doesn't remember: check that the client was fully restarted and the config has your real mk_live_... key, not the placeholder.

Tools

Tool	What it does
`memory_write`	Store a memory — insight, preference, lesson learned
`memory_read`	Search memories by natural language query
`memory_feedback`	Rate memories as helpful or not (improves future recall)
`memory_stats`	Check how many memories stored, which domains exist
`memory_delete`	Permanently delete a single memory by `atom_id`
`memory_delete_domain`	Wipe an entire domain (requires `confirm: true` safety interlock)

Ideas: What to Remember

User preferences: "I use dark mode", "I prefer Tailwind over CSS modules

... View full README on GitHub