Developer · Remote MCP server
Memoire partagee
Shared memory MCP server for product classification in wealth management.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
live.alpic.memoire-partagee-ffe6c8c2/Memoire-partagee- Version
- 0.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-06-30
- Updated
- 2026-06-30
- Publisher
- live.alpic.memoire-partagee-ffe6c8c2
- Namespace
- Namespace verified by the MCP Registry via the domain memoire-partagee-ffe6c8c2.alpic.live or a parent domain of it · how
- Website
- memoire-partagee-ffe6c8c2.alpic.live
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://memoire-partagee-ffe6c8c2.alpic.live | None |
| SSE (HTTP + Server-Sent Events) | https://memoire-partagee-ffe6c8c2.alpic.live | 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.
- Endpoint
https://memoire-partagee-ffe6c8c2.alpic.live(HTTP)- 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
- Endpoint
https://memoire-partagee-ffe6c8c2.alpic.live(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: 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 Memoire partagee
Memoire partagee is a remote MCP server: there is nothing to install. Its endpoint is https://memoire-partagee-ffe6c8c2.alpic.live, 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.
It also lists an endpoint on the older SSE transport https://memoire-partagee-ffe6c8c2.alpic.live. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
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 developer servers
| Server | Runs |
|---|---|
| MeminiLocal-first project memory and mistake-prevention guardrails for AI coding agents. | Local · stdio |
| memoMemory for AI agents - MLX (Apple Silicon) or CPU (Linux), sqlite-vec + BM25, zero cloud. | Local · stdio |
| MemocallRecall past Claude Code conversations from any project as clean, compact Markdown. | Local · stdio |
| MemoirPersistent memory for AI coding tools via MCP. Remembers across sessions and machines. | Local · stdio |
| Memoize - persistent agent memoryPersistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents. | Remote · HTTPLive check: sign-in required |
| Memory FabricFile-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB. | Local · stdio |
| Memory FtsLong-term memory for Claude Code with SQLite FTS5 search and BM25 ranking. | Local · stdio |
| Memory IndustryMemoryIndustry persistent memory MCP server: BM25+MMR retrieval and audit. | Local · stdio |