Other · Remote MCP server
MemPersist
Durable, revision-pinned memory storage and retrieval for AI conversations.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.ravhirizaldi/mempersist- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- ravhirizaldi (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/ravhirizaldi) · how
- Website
- mempersist.codifiedtech.id
- Repository
- github.com/ravhirizaldi/mempersist
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mempersist.codifiedtech.id/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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect MemPersist
MemPersist is a remote MCP server: there is nothing to install. Its endpoint is https://mempersist.codifiedtech.id/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 |
|---|---|
| Memorylens MCPMCP server for.NET memory profiling - in-process heap snapshots via EventPipe with leak heuristics. | Local · stdio |
| MemoryPluginGive every AI you use one shared, permanent memory. Store once, recall in whichever AI you open. | Remote · HTTP, SSELive check: ✓ handshake |
| MemoTrader MCP ServerAI-to-human attention marketplace. Agents pay CPM to reach humans, earn credits by replying. | Local · stdio |
| MemoweftPortable AI memory as MCP tools: five reads and three controlled writes. | Local · stdio |
| MemphoraAdd persistent memory to AI assistants. Store and recall info across conversations. | Local · stdio |
| 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 |