Is com.memxus/memxus safe to use?

com.memxus/memxus 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 com.memxus/memxus?

com.memxus/memxus supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with com.memxus/memxus?

com.memxus/memxus is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.

Is com.memxus/memxus actively maintained?

com.memxus/memxus is actively maintained — last commit was 4 days ago. It has 3 GitHub stars.

com.memxus/memxus

npm

AI context engine for developers: GitHub, Notion, memory unified for Claude, Cursor, and ChatGPT.

3 15.3M/wk GitHub npm

No known CVEs

No license

Actively maintained

Last commit 4d ago

Works with most clients

Transport:

0 tools

Grade F

MCPpedia last refreshed this data 2d ago

Edit this pageView history

AI / ML

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "memxus": {
      "url": "https://mcp.memxus.com/mcp",
      "transport": "streamable-http"
    }
  }
}

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/com-memxus-memxus-gpitrella)](https://mcppedia.org/s/com-memxus-memxus-gpitrella)

Read me

What com.memxus/memxus does

Builds persistent context from GitHub, Notion, and your saved decisions — delivered to Claude, Cursor, ChatGPT, VS Code, and any MCP-compatible client.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

49/100across 5 weighted dimensions

How we score →

0255075100

−51

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b

Affected: >= 0Fixed in 6.13.4source →

Community

Reviews

Be the first to review

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 com.memxus/memxus safe to use?: com.memxus/memxus 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 com.memxus/memxus?: com.memxus/memxus supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with com.memxus/memxus?: com.memxus/memxus is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is com.memxus/memxus actively maintained?: com.memxus/memxus is actively maintained — last commit was 4 days ago. It has 3 GitHub stars.

Similar servers

Others in ai-ml

View all →

Sequential Thinking MCP Server96

Dynamic problem-solving through sequential thought chains

88.9k 1

Memory MCP Server96

Persistent memory using a knowledge graph

88.9k 5

Antigravity Workspace Template96

Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.

1.3k 2

LycheeMem96

Compact, efficient, and extensible long-term memory for LLM agents.

1.2k 3

MCP Security Weekly

Get CVE alerts and security updates for com.memxus/memxus and similar servers.

Community

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?

Edit this pageView history

AI / ML

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "memxus": {
      "url": "https://mcp.memxus.com/mcp",
      "transport": "streamable-http"
    }
  }
}

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/com-memxus-memxus-gpitrella)](https://mcppedia.org/s/com-memxus-memxus-gpitrella)

Read me

What com.memxus/memxus does

Builds persistent context from GitHub, Notion, and your saved decisions — delivered to Claude, Cursor, ChatGPT, VS Code, and any MCP-compatible client.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Memxus — AI Context Engine

One context engine. Every AI.

Builds persistent context from GitHub, Notion, and your saved decisions — delivered to Claude, Cursor, ChatGPT, VS Code, and any MCP-compatible client.

Glama MCP Connector License: AGPL-3.0 Node 20+ Railway MCP Registry v1.2.0

Website · Docs · Connect your first AI · Glama Inspector

Watch the Memxus demo on YouTube

▶️ Watch the demo on YouTube · Demo page

The problem

Every AI tool starts from zero.

Claude doesn't know what Cursor knows. Cursor doesn't know what ChatGPT knows.
Your stack, project decisions, coding preferences and workflow context get repeated again and again.

Memxus fixes that with a shared context engine for your AI tools — not another chatbot, but persistent context built from your real work sources.

Sync GitHub once → every AI knows your stack. Save a decision in Claude → recall it in Cursor → reuse it in ChatGPT.

What is Memxus?

Memxus is the AI context engine — a hosted remote MCP server that automatically builds and delivers persistent project context to every AI client you use.

GitHub repos, Notion docs, commits, PRs, issues, and saved decisions become searchable context. GitHub and Notion connectors are live in production (v1.2.0) — connect from the dashboard or directly from chat via MCP connector tools.

No local setup.
No file syncing.
No copy-pasting context between tools.

Connect once with OAuth and your context becomes portable across your entire AI workflow.

Why developers use Memxus

Keep project architecture and stack context available across Claude, Cursor, and ChatGPT
Sync GitHub and Notion into unified project collections — one context per repo
Stop pasting the same context into every new AI session
Share team context across agents and workflows
Build AI apps with persistent context through MCP or API

Real context from GitHub & Notion

Memxus reads your real work — not generic memory snippets. Synced content lands in a unified collection per project: project:<slug>.

What gets synced

Source	Content indexed into context
GitHub	Repos, READMEs, commits, pull requests, issues
Notion	Selected workspace pages and docs
Manual	Decisions, preferences, and notes via `remember`

How to connect

Dashboard — dashboard.memxus.com/integrations (GitHub App + Notion OAuth)
From chat (MCP) — connect_source → check_connect_status → list_syncable_items → set_sync_selection

How to use synced context

Call recall or get_context with collection=project:<slug> (or let semantic search find it). GitHub/Notion content is tagged and searchable alongside manual memories.

flowchart LR
  GitHub[GitHub repos] --> Sync[Memxus sync]
  Notion[Notion pages] --> Sync
  Manual[Manual remember] --> Sync
  Sync --> Collection["project:slug"]
  Collection --> Tools["recall / get_context"]
  Tools --> Clients[Claude Cursor ChatGPT]

Context Engine connector tools (4): connect GitHub/Notion from chat via MCP. Production ships a 13-tool public manifest (9 core + 4 connect) with skill routing deferred.

Connect in 30 seconds

URL:       https://mcp.memxus.com/mcp
Auth:      OAuth 2.1 (handled automatically)
Transport: Streamable HTTP

Claude Desktop (`claude_desktop_conf

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

49/100across 5 weighted dimensions

How we score →

0255075100

−51

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

8 fixed

CVE-2022-29244high · fixedCVSS 7.5

Packing does not respect root-level ignore files in workspaces

Affected: >= 7.9.0Fixed in 8.11.0source →

CVE-2018-7408high · fixedCVSS 7.8

Incorrect Permission Assignment for Critical Resource in NPM

Affected: >= 0Fixed in 5.7.1source →

CVE-2013-4116info · fixed

Local Privilege Escalation in npm

Affected: >= 0Fixed in 1.3.3source →

CVE-2020-15095medium · fixedCVSS 4.4

npm CLI exposing sensitive information through logs

Affected: >= 0Fixed in 6.14.6source →

CVE-2019-16777high · fixedCVSS 7.7

npm Vulnerable to Global node_modules Binary Overwrite

Affected: >= 0Fixed in 6.13.4source →

Community

Reviews

Be the first to review

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 com.memxus/memxus safe to use?: com.memxus/memxus 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 com.memxus/memxus?: com.memxus/memxus supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with com.memxus/memxus?: com.memxus/memxus is compatible with claude-desktop, cursor, claude-code. It uses stdio transport.
Is com.memxus/memxus actively maintained?: com.memxus/memxus is actively maintained — last commit was 4 days ago. It has 3 GitHub stars.

Similar servers

Others in ai-ml

View all →

Sequential Thinking MCP Server96

Dynamic problem-solving through sequential thought chains

88.9k 1

Memory MCP Server96

Persistent memory using a knowledge graph

88.9k 5

Antigravity Workspace Template96

Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.

1.3k 2

LycheeMem96

Compact, efficient, and extensible long-term memory for LLM agents.

1.2k 3

MCP Security Weekly

Get CVE alerts and security updates for com.memxus/memxus and similar servers.

Community

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?