MemoStem MCP server
online · 100% uptimeio.github.girapphe/memostem·v0.6.3Your reviewed knowledge, across AI conversations.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed MemoStem yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
MemoStem tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How MemoStem compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 76/100
- higher than 48% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 1,490 ms
- faster than 5% of 30,031 servers
Release history: 4 versions in the registry since 2026-09-16, latest 2026-10-16, typically one every 6 days.
Install MemoStem in Claude Code, Cursor or VS Code
claude mcp add --transport http memostem https://www.memostem.com/api/mcp
What the publisher says
From the MemoStem repository's README, as published. We do not edit it. Read it on GitHub
MemoStem across AI conversations
Your reviewed knowledge, across AI conversations.
Let a connected AI reuse your private, confirmed knowledge or notice knowledge worth keeping as the conversation unfolds. New material becomes a private draft only after you confirm—without uploading the whole conversation or publishing anything automatically.
Use MemoStem · Connection guide · Privacy · Terms · Support · Security
This public repository is the official distribution source for MemoStem's chat-host skills, plugin packages, and hosted remote MCP connection metadata. ChatGPT, Claude, Kimi, Gemini and Grok are the primary channels; Codex and Claude Code are compatible secondary channels. The MemoStem application and server implementation remain private. Distributable manifests, skills, examples, and documentation have no mirrored authoring copy in that private repository.
Save here, reuse in another AI conversation
Select an explanation in ChatGPT, save it as a private pending draft, and review and approve it in MemoStem. Then ask Claude or another connected host to find that knowledge. Sign in to the same MemoStem account in each host; no host gets access to another host's conversation history.
Why MemoStem
name a reusable result and ask whether to keep it, so you do not need to remember a MemoStem or card command.
- Get a timely suggestion. In supported plugin clients, the assistant can
Only the specific suggestion you confirm is sent, never a transcript or hidden history. If you invoke MemoStem without naming material and the current chat has no eligible candidate, the same flow may use recent conversation context the host explicitly provides; it cannot browse unavailable conversation history.
- Confirm, don't scrape. Nothing is transferred when the AI notices an idea.
you edit, merge, save, or ignore it.
- Review before saving. New material stays in a private pending inbox until
question-and-answer draft for one retrieval question.
- Keep knowledge teachable. Create an atomic memo for one concept or a
signed-in owner's confirmed knowledge and, only when explicitly requested, inspect its lifecycle state.
- Reuse only your knowledge. A read-authorized connection can retrieve the
Ask for useful cards
and an example.”
- Concept: “Save how rain forms as one concise concept card, with a definition
forms water droplets, using what we just discussed.”
- Retrieval question: “Make one question-and-answer card about why cooling air
so I can choose which to keep.”
- Selection first: “Show me candidates for the weather concepts we discussed
In an MCP Apps-capable host with a connected account, check candidates and click Add. That click creates only the selected private pending drafts; no second chat confirmation is needed. If the host shows a text list instead, reply with the candidates to keep. Then open Candidate Inbox to read, edit, and approve them. Previewing or adding drafts does not approve knowledge or enroll it in practice. The picker UI is served by the hosted MCP server; see the MCP Apps contract and host requirements.
See card examples and review steps.
Connect from an AI app
The production Streamable HTTP MCP endpoint is:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Grade history
- 2026-10-03restoreC → Bscore 76: Write-action tools reachable without authentication
- 2026-09-19downgradeB → Cscore 69: Write-action tools reachable without authentication
MemoStem: common questions
- Is MemoStem MCP server safe?
- Mostly: it is graded B (76/100). Read the MemoStem safety report
- How do I install MemoStem?
- It runs remotely at www.memostem.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does MemoStem need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is MemoStem maintained?
- The last commit was 34 days ago (2026-10-01). The latest release is v0.6.3.
- Is MemoStem up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does MemoStem compare with other MCP servers?
- safety score 76/100 (higher than 48% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,490 ms (faster than 5% of 30,031 servers). Full comparison.