Other · Remote MCP server
Memxus
Persistent memory layer that saves and recalls your project context and preferences.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.memxus/memxus- Version
- 1.3.2
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- com.memxus
- Namespace
- Namespace verified by the MCP Registry via the domain memxus.com · how
- Repository
- github.com/gpitrella/memxus-remote-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.memxus.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- memxus 1.3.2 · protocol 2024-11-05
- Tools discovered
- 9:
remember,recall,get_context,list_memories,get_memory,list_collections,forget,memory_stats,update - Checked on
- 2026-10-05
How to connect Memxus
Memxus is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.memxus.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| MemQ Team SyncShared project memory that keeps teammates and AI agents aligned across sessions. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MemraPersistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection. | Remote · HTTPLive check: ✓ handshake |
| MemtetherCross-client AI memory hub: agents share one SQLite memory.db via file-level pointers. | Local · stdio |
| MemtrustIndependent, reproducible benchmark harness for agent-memory backends. | Local · stdio |
| MencoroTrack and manage how your brand appears in AI answers: rank, mentions, sentiment, share of voice. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MendriftMCP server for ML drift detection, MLflow registry diffing, and HMAC-gated model rollback. | Local · stdio |
| MengramLong-term memory for AI agents: semantic facts, episodic events, and procedural workflows. | Remote · HTTPLive check: sign-in required |
| MeniscusLiquid glass design system for AI agents: specs, recipes and reference renders for every platform. | Remote · HTTPLive check: sign-in required |