Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MemoStem

REMOTE · WWW.MEMOSTEM.COM · SCANNED SEP 28

Your reviewed knowledge, across AI conversations.

Available components

0 this week 70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security69
Transport & Reachability100
Schema Quality & AI Usability66
  • 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1324 tokens (~110/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the MemoStem MCP server?

MemoStem is a hosted endpoint at https://www.memostem.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.memostem.com

# add to Claude Code
claude mcp add --transport http girapphe-memostem 'https://www.memostem.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "girapphe-memostem": {
      "url": "https://www.memostem.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "girapphe-memostem": {
      "type": "http",
      "url": "https://www.memostem.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.girapphe-memostem]
url = "https://www.memostem.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "girapphe-memostem": {
      "type": "remote",
      "url": "https://www.memostem.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add girapphe-memostem --url 'https://www.memostem.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  girapphe-memostem:
    url: "https://www.memostem.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "girapphe-memostem": {
      "Transport": "http",
      "Url": "https://www.memostem.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add girapphe-memostem -t streamable-http -u 'https://www.memostem.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "girapphe-memostem": {
      "type": "http",
      "url": "https://www.memostem.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 −2
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 920 → 1324 ▼ functional
    • Schema quality: 100% → 50% ▼ functional
    • Schema quality: fail → pass ▲ functional
    • First check of Capabilities: pass functional
    • New resource “MemoStem getting started” functional
    • New tool “refresh_guest_knowledge_shelf_link” functional
    • New tool “connect_memostem” functional
    • New tool “start_memostem” functional
  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +2
    • Schema quality: 128 → 115 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • The server now declares the “resources” capability functional
    • Schema quality: excellent → good functional
    • New resource “MemoStem knowledge candidate picker” functional
  • 18 Sept 26 +34
    • Authorization: pass → partial ▼ security
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Tool coverage: 0 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 100 functional
    • First check of Tool coverage: 100 functional
  • 15 Sept 26 33

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 28 Sept 2026 · Probed https://www.memostem.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=memostem.com CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d1ea4765832d72a313e475b932ca2e1a
SANs: memostem.com, www.memostem.com, *.www.memostem.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.memostem.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
memostem.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.memostem.com/api/mcp Verified 200
http (plaintext) http://www.memostem.com/api/mcp Inconclusive 405
MCP tools · 10 exposed · ~915 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_memostem_connection ~35

Verify the authenticated MemoStem connection and report only the currently granted knowledge permissions. This test does not read or write knowledge.

Input schema present but exposes no named parameters.

NameTypeReqDescription
draft_review_pathstringyes–
granted_scopesarrayyes–
settings_pathstringyes–
statusstringyes–

No examples provided.

claim_guest_knowledge_workspace ~65

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.

NameTypeReqDescription
workspace_tokenstringyes–
NameTypeReqDescription
claimed_draft_countintegeryes–
review_pathstringyes–
statusstringyes–

No examples provided.

connect_memostem ~49

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.

NameTypeReqDescription
cursor–––
localestring––
NameTypeReqDescription
localestringyes–
next_cursor–yes–
statusstringyes–
topicsarrayyes–

No examples provided.

create_card_drafts ~146

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.

NameTypeReqDescription
cardsarrayyes–
provenanceobjectyes–
providerstringyes–
request_idstringyes–
NameTypeReqDescription
batch_idstringyes–
createdbooleanyes–
draft_countintegeryes–
review_pathstringyes–
review_urlstringyes–
statusstringyes–

No examples provided.

create_knowledge_bundle_drafts ~131

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.

NameTypeReqDescription
bundlesarrayyes–
provenanceobjectyes–
providerstringyes–
request_idstringyes–
NameTypeReqDescription
batch_idstringyes–
bundle_countintegeryes–
createdbooleanyes–
review_pathstringyes–
review_urlstringyes–
statusstringyes–

No examples provided.

preview_knowledge_bundle ~109

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.

NameTypeReqDescription
bundlesarrayyes–
provenanceobjectyes–
providerstringyes–
request_idstringyes–
NameTypeReqDescription
bundle_countnumberyes–
knowledge_typestringyes–
persistedbooleanyes–
statusstringyes–
titlestringyes–

No examples provided.

refresh_guest_knowledge_shelf_link ~84

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.

NameTypeReqDescription
workspace_tokenstringyes–
NameTypeReqDescription
card_countintegeryes–
card_limitnumberyes–
expires_atstringyes–
review_urlstringyes–
statusstringyes–

No examples provided.

save_guest_knowledge_bundles ~135

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.

NameTypeReqDescription
bundlesarrayyes–
provenanceobjectyes–
providerstringyes–
request_idstringyes–
workspace_tokenstring––
NameTypeReqDescription
accepted_bundle_countintegeryes–
account_requiredbooleanyes–
card_countintegeryes–
card_limitnumberyes–
expires_atstringyes–
persistedbooleanyes–
remaining_capacityintegeryes–
review_urlstringyes–
statusstringyes–
workspace_tokenstringyes–

No examples provided.

start_memostem ~64

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.

NameTypeReqDescription
cursor–––
localestring––
NameTypeReqDescription
localestringyes–
next_cursor–yes–
statusstringyes–
topicsarrayyes–

No examples provided.

validate_knowledge_bundle ~97

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, personal or organization-specific memory, and unsupported knowledge types.

NameTypeReqDescription
bundlesarrayyes–
provenanceobjectyes–
providerstringyes–
request_idstringyes–
NameTypeReqDescription
bundle_countnumberyes–
knowledge_typestringyes–
persistedbooleanyes–
statusstringyes–
titlestringyes–

No examples provided.

Common questions

What is the MemoStem MCP server?

MemoStem is an MCP server listed in the public MCP registry as io.github.girapphe/memostem. Your reviewed knowledge, across AI conversations. This page covers its hosted endpoint (https://www.memostem.com/api/mcp).

Is the MemoStem MCP server safe to use?

MemoStem scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MemoStem MCP server expose?

MemoStem exposes 10 tools: start_memostem, connect_memostem, validate_knowledge_bundle, save_guest_knowledge_bundles, refresh_guest_knowledge_shelf_link, and 5 more. Their descriptions and schemas cost roughly 915 tokens of context every time the server is loaded.

Does the MemoStem MCP server require authentication?

No. We connected to MemoStem without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MemoStem MCP server still maintained?

MemoStem is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.