MemoStem MCP server
io.github.girapphe/memostemgirapphestreamable-httpv0.6.4Scanned
Your reviewed knowledge, across AI conversations.
13 tools: 1 do something that can't be undone, 7 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 3 findings, 1 high
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MemoStem MCP server can do
The MemoStem MCP server is published by the GitHub account girapphe. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (claim_guest_knowledge_workspace) and create or change data (7 tools: start_memostem, connect_memostem, save_guest_knowledge_bundles, refresh_guest_knowledge_shelf_link and 3 more), but cannot delete data. 5 tools only read.
2 tools bring in text other people can write (search_card_browser and browse_memostem_cards).
The fixed checks matched 3 findings, 1 of them high severity (annotation-conflict, model-directed-text and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.6.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Can't be undone 1Claude Code: ask
claim_guest_knowledge_workspaceTransfer the temporary guest shelf identified by workspace_token to the authenticated MemoStem owner as private pending drafts.No findings
Why it is in this group
- The description's first verb is "transfer": a word for a change that another call does not undo.
Description, as the server wrote it Transfer the temporary guest shelf identified by workspace_token to the authenticated MemoStem owner as private pending drafts. Call only after the person explicitly agrees to connect or after the guest shelf reports account_required. This tool never approves or publishes cards.
Annotations the server declares
- title: Connect and keep a guest knowledge shelf
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Changes things 7Claude Code: ask
check_memostem_connectionVerify the MemoStem connection and report only the currently granted knowledge permissions.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Verify the MemoStem connection and report only the currently granted knowledge permissions. Without an account it reports status guest with no permissions, and the temporary guest shelf stays available. This test does not read or write knowledge.
Annotations the server declares
- title: Check MemoStem connection
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
connect_memostemConnect or grant knowledge read permission through the host OAuth flow, then show a page of the authenticated owner's topic labels.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Connect or grant knowledge read permission through the host OAuth flow, then show a page of the authenticated owner's topic labels. Never creates knowledge.
Annotations the server declares
- title: Connect MemoStem and show topics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_card_draftsCreate pending, user-owned general-knowledge card drafts only after clear affirmative consent to specifically named, independently teachable knowledge in the current conversation.No findings
Why it is in this group
- The name "create_card_drafts" says "create": a word for a change.
Description, as the server wrote it Create pending, user-owned general-knowledge card drafts only after clear affirmative consent to specifically named, independently teachable knowledge in the current conversation. Every card must declare knowledge_scope as general_knowledge. Personal or company decisions, product principles or policies, pricing rationale, preferences, plans, tasks, reminders, meeting outcomes, project status, and autobiographical facts are ineligible. An assistant suggestion alone is not consent. This tool never accepts raw transcripts or historical-conversation data, and it cannot approve, publish, or modify public knowledge cards.
Annotations the server declares
- title: Create knowledge-card drafts
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
create_knowledge_bundle_draftsCreate pending, user-owned concept, general procedure, comparison, mechanism, structure, claim/evidence, knowledge question, historical event, or language-expression drafts only af…No findings
Why it is in this group
- The name "create_knowledge_bundle_drafts" says "create": a word for a change.
Description, as the server wrote it Create pending, user-owned concept, general procedure, comparison, mechanism, structure, claim/evidence, knowledge question, historical event, or language-expression drafts only after clear affirmative consent to specifically named, independently teachable general knowledge in the current conversation. Every bundle must declare knowledge_scope as general_knowledge; decisions and organization-specific material are not accepted. An assistant suggestion alone is not consent. It cannot approve drafts, retain transcripts, or modify public knowledge.
Annotations the server declares
- title: Create structured knowledge-bundle drafts
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
refresh_guest_knowledge_shelf_linkIssue a new short-lived, one-time mobile or desktop web link for the existing guest shelf.No findings
Why it is in this group
- The name "refresh_guest_knowledge_shelf_link" says "link": a word for a change.
Description, as the server wrote it Issue a new short-lived, one-time mobile or desktop web link for the existing guest shelf. Use only when the person asks to open or recover that shelf. Pass the private workspace_token as a tool argument; never show or put it in a URL. This adds no card and makes the previous view link invalid.
Annotations the server declares
- title: Get a fresh guest shelf link
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
save_guest_knowledge_bundlesStore one to 10 specifically selected, independently teachable general-knowledge bundles from the current conversation in a private temporary MemoStem guest shelf.2 findings
Why it is in this group
- The name "save_guest_knowledge_bundles" says "save": a word for a change.
Findings
- High
The description contains "never reveal that", an instruction to keep something from the user.
What this check looks forMatched text
description: "...e_token to continue the same shelf, but never reveal that credential to the person. The shelf is..."
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...e the same shelf, but never reveal that credential to the person. The shelf is read-only i..."
Description, as the server wrote it Store one to 10 specifically selected, independently teachable general-knowledge bundles from the current conversation in a private temporary MemoStem guest shelf. Call only after a direct request or clear acceptance of a specific proposal. Reuse workspace_token to continue the same shelf, but never reveal that credential to the person. The shelf is read-only in MemoStem, expires after 90 days, and requires account connection at 10 cards.
Annotations the server declares
- title: Save knowledge to a temporary guest shelf
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
start_memostemStart MemoStem when no topic is named.1 finding
Why it is in this group
- The name "start_memostem" says "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "start_memostem" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_memostem" says "start": a word for a change.
Description, as the server wrote it Start MemoStem when no topic is named. Show a localized welcome App before login, or the connected owner's topic labels and empty-state guidance. Pass the conversation language as locale when known. No drafts are created.
Annotations the server declares
- title: Start MemoStem
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
browse_memostem_cardsBrowse or search the connected owner’s active approved knowledge cards.Reads text others writeNo findings
Why it is in this group
- The name "browse_memostem_cards" says "browse": a word for reading.
What it can reach
- untrusted-inputThe name "browse_memostem_cards" says "browse": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse or search the connected owner’s active approved knowledge cards. Open a card for its details. This does not create or change knowledge.
Annotations the server declares
- title: Browse MemoStem cards
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_card_neighborhoodRead a page of the selected owner card’s confirmed private relationships and inferred shared-tag connections.No findings
Why it is in this group
- The name "get_card_neighborhood" says "get": a word for reading.
Description, as the server wrote it Read a page of the selected owner card’s confirmed private relationships and inferred shared-tag connections. Results are bounded and read-only.
Annotations the server declares
- title: Explore card relationships
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
preview_knowledge_bundleReturn a transient preview of exactly one user-selected, independently teachable general-knowledge bundle without an account and without saving it.No findings
Why it is in this group
- The name "preview_knowledge_bundle" says "preview": a word for reading.
Description, as the server wrote it Return a transient preview of exactly one user-selected, independently teachable general-knowledge bundle without an account and without saving it. Call only at the person's direct request or after clear acceptance of a specific preview proposal. Use save_guest_knowledge_bundles only after the person explicitly asks to keep it; connected clients use create_knowledge_bundle_drafts.
Annotations the server declares
- title: Preview one knowledge bundle
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_card_browserSearch or page through active approved cards without reopening the browser.Reads text others writeNo findings
Why it is in this group
- The name "search_card_browser" says "search": a word for reading.
What it can reach
- untrusted-inputThe name "search_card_browser" says "search" and "browser": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "search" and "browser": it reads web pages, which anyone can write.
Description, as the server wrote it Search or page through active approved cards without reopening the browser.
Annotations the server declares
- title: Search MemoStem cards
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_knowledge_bundleValidate exactly one user-selected, independently teachable general-knowledge bundle without an account and without saving it.No findings
Why it is in this group
- The name "validate_knowledge_bundle" says "validate": a word for reading.
Description, as the server wrote it Validate exactly one user-selected, independently teachable general-knowledge bundle without an account and without saving it. Call only at the person's direct request or after clear acceptance of a specific preview proposal. The strict input rejects transcripts, conversation histories, and unsupported knowledge types; phrases that may be personal or organization-specific are returned as review_flags.
Annotations the server declares
- title: Validate one knowledge bundle
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.memostem.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://clerk.memostem.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 irreversible, 7 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.memostem.com/api/mcp: tools/list returned 13 tools to an anonymous client, including claim_guest_knowledge_workspace (irreversible), start_memostem (write), connect_memostem (write), save_guest_knowledge_bundles (write), refresh_guest_knowledge_shelf_link (write) and 3 more
Posture changes
- Nov 6, 2026
- RFC 9728 protected resource metadata: none to https://www.memostem.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers: none to https://clerk.memostem.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Findings
Matches of fixed checks, with the text they matched.
The description contains "never reveal that", an instruction to keep something from the user.
What this check looks forMatched text
description: "...e_token to continue the same shelf, but never reveal that credential to the person. The shelf is..."
- Warnstart_memostem
The server marks "start_memostem" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_memostem" says "start": a word for a change.
The description mentions "credential".
What this check looks forMatched text
description: "...e the same shelf, but never reveal that credential to the person. The shelf is read-only i..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 added.+3 addedView diff
- Added:browse_memostem_cardsOnly reads
- Added:get_card_neighborhoodOnly reads
- Added:search_card_browserOnly reads
PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://www.memostem.com/.well-known/oauth-protected-resource/api/mcp; Authorization servers: none -> https://clerk.memostem.com; Dynamic client registration: not observe…View diff
- RFC 9728 protected resource metadata: none to https://www.memostem.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers: none to https://clerk.memostem.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Install
Pinned to version 0.6.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http memostem https://www.memostem.com/api/mcpclaude mcp add --transport http memostem https://www.memostem.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__memostem__get_card_neighborhood",
"mcp__memostem__search_card_browser",
"mcp__memostem__browse_memostem_cards",
"mcp__memostem__validate_knowledge_bundle",
"mcp__memostem__preview_knowledge_bundle"
],
"ask": [
"mcp__memostem__start_memostem",
"mcp__memostem__connect_memostem",
"mcp__memostem__save_guest_knowledge_bundles",
"mcp__memostem__refresh_guest_knowledge_shelf_link",
"mcp__memostem__claim_guest_knowledge_workspace",
"mcp__memostem__check_memostem_connection",
"mcp__memostem__create_card_drafts",
"mcp__memostem__create_knowledge_bundle_drafts"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as memostem. Review it before you use it.
Capability tags behind 2 rules
- mcp__memostem__search_card_browser untrusted-input
- mcp__memostem__browse_memostem_cards untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.girapphe/memostem/verify?hash=8dc289a1eb2b7f6337e24f42f710f1db44b84789b8b0b6a7810d1710209f3df2" | jq -e '.changed == false'Pinned hash 8dc289a1eb2b, from Nov 16, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.girapphe/memostem/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.girapphe/memostem)Source: MCP Registry · repository. Synced Nov 16, 2026, 09:18 UTC.
MemoStem MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MemoStem MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 8 of which can change, send or delete something, and 3 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MemoStem MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MemoStem MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: claim_guest_knowledge_workspace.
What tools does the MemoStem MCP server have?
- 13 tools: 1 irreversible, 7 write, 5 read. claim_guest_knowledge_workspace, start_memostem, connect_memostem, save_guest_knowledge_bundles, refresh_guest_knowledge_shelf_link, check_memostem_connection, create_card_drafts, create_knowledge_bundle_drafts and 5 more.
Does the MemoStem MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MemoStem MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MemoStem MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.