Memmo MCP server
dev.memmo/memmomemmo.devstreamable-httpv0.9.5Scanned
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
6 tools: 2 change things and 4 only read.
- Reads private data · 4
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- 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 Memmo MCP server can do
The Memmo MCP server is published by memmo.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: propose_memories and record_session_summary), but cannot delete data. 4 tools only read.
4 tools read private data (list_repos, search_memory, get_repo_context and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 7, 2026, version 0.9.5.
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.
6 tools
Changes things 2Claude Code: ask
propose_memoriesRecord durable, reusable knowledge (conventions, architecture, commands, risks, decisions) as PROPOSED memories for human review.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.
Description, as the server wrote it Record durable, reusable knowledge (conventions, architecture, commands, risks, decisions) as PROPOSED memories for human review. Keep each ATOMIC (one fact) and CONCISE (1–3 sentences). Use supersedes with an id from search_memory to correct an outdated memory.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
record_session_summarySubmit what you just did (task, summary, files, commands, errors) so Memmo can propose memories for review.No findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
Description, as the server wrote it Submit what you just did (task, summary, files, commands, errors) so Memmo can propose memories for review.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_relevant_warningsRisk/failure memories for the files you're about to edit.Reads private dataNo findings
Why it is in this group
- The name "get_relevant_warnings" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
Description, as the server wrote it Risk/failure memories for the files you're about to edit. Call before editing sensitive files.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_repo_contextStack, package manager, key commands, and known risks for a repo.Reads private dataNo findings
Why it is in this group
- The name "get_repo_context" says "get": a word for reading.
What it can reach
- private-dataThe name "get_repo_context" says "get" and "repo": it reads repositories.
- private-dataThe description's first sentence says "repo": it reads repositories.
- private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
Description, as the server wrote it Stack, package manager, key commands, and known risks for a repo. Call before starting work.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_reposList the repos this token can access (id, owner/name, project).Reads private dataNo findings
Why it is in this group
- The name "list_repos" says "list": a word for reading.
What it can reach
- private-dataThe name "list_repos" says "list" and "repo": it reads repositories.
- private-dataThe description's first sentence says "list" and "repo": it reads repositories.
Description, as the server wrote it List the repos this token can access (id, owner/name, project). Use to find the repo identifier.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_memorySearch the team's approved memory for a repo (rules, architecture, commands, decisions, risks, past failures).Reads private dataNo findings
Why it is in this group
- The name "search_memory" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "repo": it reads repositories.
- private-dataThe input names a repo (input.repo), and the tool reads: it reads repositories.
Description, as the server wrote it Search the team's approved memory for a repo (rules, architecture, commands, decisions, risks, past failures). Call it while planning — with a one-line summary of what you intend to do — and before non-trivial changes. Results marked 'replaces' are the current decision.
Annotations the server declares
- 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 untrusted-input or outbound.
- Reads private data4
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- 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, 18:23 UTC, unchanged since Nov 13, 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
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.memmo.dev/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.memmo.dev
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.memmo.dev/mcp: tools/list returned 6 tools to an anonymous client, including propose_memories (write), record_session_summary (write)
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.memmo.dev/.well-known/oauth-protected-resource to none
- RFC 9728 protected resource metadata: https://api.memmo.dev/.well-known/oauth-protected-resource to https://api.memmo.dev/.well-known/oauth-protected-resource/mcp
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 2 (and 4 more).View diff
- HTTP status of an anonymous initialize: 401 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 2
- Protocol version: none to 2025-06-18
- WWW-Authenticate on 401: yes to not observed
- resource_metadata in WWW-Authenticate: https://api.memmo.dev/.well-known/oauth-protected-resource to none
- RFC 9728 protected resource metadata: https://api.memmo.dev/.well-known/oauth-protected-resource to https://api.memmo.dev/.well-known/oauth-protected-resource/mcp
Install
Pinned to version 0.9.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http memmo https://api.memmo.dev/mcpclaude mcp add --transport http memmo https://api.memmo.dev/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__memmo__list_repos",
"mcp__memmo__search_memory",
"mcp__memmo__get_repo_context",
"mcp__memmo__get_relevant_warnings"
],
"ask": [
"mcp__memmo__propose_memories",
"mcp__memmo__record_session_summary"
],
"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 memmo. Review it before you use it.
Capability tags behind 4 rules
- mcp__memmo__list_repos private-data
- mcp__memmo__search_memory private-data
- mcp__memmo__get_repo_context private-data
- mcp__memmo__get_relevant_warnings private-data
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/dev.memmo/memmo/verify?hash=9761b8d6035a08a26fc28d4c08902012716fae145ca3e8bd6bea0b1e1f4b0be8" | jq -e '.changed == false'Pinned hash 9761b8d6035a, from Nov 7, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.memmo/memmo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.memmo/memmo)Source: MCP Registry. Synced Nov 7, 2026, 17:17 UTC.
Memmo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Memmo MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Memmo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Memmo MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Memmo MCP server have?
- 6 tools: 2 write, 4 read. propose_memories, record_session_summary, list_repos, search_memory, get_repo_context and get_relevant_warnings.
Does the Memmo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Memmo MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Memmo MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 7, 2026.