Memoire partagee
live.alpic.memoire-partagee-ffe6c8c2Published by memoire-partagee-ffe6c8c2.alpic.liveOfficial publisherv0.0.1Updated Oct 24, 2026
Shared memory MCP server for product classification in wealth management.
Overview
A remote shared-memory MCP server for product classification in wealth management, letting an assistant store and reuse classification context across sessions.
- What you can do
- Provides shared memory for product classification work in wealth management, so an assistant can keep and recall classification context across sessions rather than rebuilding it each time. The manifest lists no individual tools, so the exact operations are not documented; expect memory-style read and write behavior around classification data. It runs as a hosted remote endpoint rather than a local package.
- When to use it
- Consider it when an assistant repeatedly classifies wealth-management products and you want that classification context kept in one shared place instead of restated in every conversation.
- Requirements
- A remote MCP client that supports streamable HTTP, plus OAuth authentication to the hosted endpoint. No local runtime, environment variables or headers are declared.
Installation
In SourceWeft
- Open Memoire partagee in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/live.alpic.memoire-partagee-ffe6c8c2%2FMemoire-partagee/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"memoire-partagee": {
"type": "http",
"url": "https://memoire-partagee-ffe6c8c2.alpic.live/"
}
}
}Tools
0Version history
1- v0.0.1LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.