Skip to content

Memoria — Deterministic AI Memory & Code Intelligence MCP server

io.github.kolivritech/memoria-mcpkolivritechstreamable-httpv1.0.2Scanned

Official Node.js MCP connector for Memoria Cloud (https://memoria.kolivri.com).

14 tools: 2 can delete or cancel things, 7 change things and 5 only read.

Tools: 2 delete, 0 irreversible, 7 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Memoria — Deterministic AI Memory & Code Intelligence MCP server can do

The Memoria — Deterministic AI Memory & Code Intelligence MCP server is published by the GitHub account kolivritech. It has 14 tools. It can delete or cancel things (2 tools: forget_memory and delete_by_context) and create or change data (7 tools: encode_memory, batch_encode, build_context, feedback and 3 more). 5 tools only read.

1 tool reads private data (search_code).

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 19, 2026, version 1.0.2.

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.

14 tools

Deletes or cancels 2Claude Code: deny
  • delete_by_contextPermanently bulk-delete all memories whose context array contains an exact [key, value] pair (destructive, idempotent; consumes 1 Write API call) and return { deleted_count }.No findings

    Why it is in this group

    • The name "delete_by_context" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently bulk-delete all memories whose context array contains an exact [key, value] pair (destructive, idempotent; consumes 1 Write API call) and return { deleted_count }. Scopes deletion to namespace when provided, or across all namespaces in your organization when namespace is omitted (rejecting reserved "org:" prefixes). Use to purge memories tied to a deleted file, PR, or feature tag; use forget_memory instead when deleting a single memory by UUID.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • forget_memoryPermanently delete one memory and its incident graph edges by ID (destructive, idempotent; consumes 1 Write API call) and return { deleted }.No findings

    Why it is in this group

    • The description's first verb is "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Permanently delete one memory and its incident graph edges by ID (destructive, idempotent; consumes 1 Write API call) and return { deleted }. Enforces organization ownership (returns JSON-RPC error -32003 on foreign IDs) and returns { deleted: false } when the ID is already absent. Use when removing a single known memory ID; use delete_by_context instead to bulk-delete memories by [key, value] metadata tag, or feedback (useful=false) to lower salience without deleting.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 7Claude Code: ask
  • batch_encodeStore multiple memories atomically in one request (consumes max(1, memories.length) Write API calls; non-idempotent) and return { ids, encoded }.No findings

    Why it is in this group

    • The description's first verb is "store": a word for a change.
    Description, as the server wrote it
    Store multiple memories atomically in one request (consumes max(1, memories.length) Write API calls; non-idempotent) and return { ids, encoded }. Validates every item namespace before writing so any reserved "org:" prefix aborts the entire batch cleanly; items inherit top-level namespace and default to type="episodic" and salience=0.5. Use when checkpointing or importing 2+ memories together; use encode_memory instead for a single memory write.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • build_contextAssemble a token-budgeted <memory_context> XML/Markdown block from a namespace (read-only, idempotent; consumes 1 Read API call) and return { context, memories_used }.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
    Assemble a token-budgeted <memory_context> XML/Markdown block from a namespace (read-only, idempotent; consumes 1 Read API call) and return { context, memories_used }. Ranks up to 500 namespace memories deterministically and packs lines greedily up to max(256, token_budget * 4) characters under "## Established Facts" (core/semantic) and "## Recent Context" (episodic/buffer). Use at session start or before planning a task to ground the model in one call; use recall_memories instead when you need raw memory objects and IDs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • consolidateRun an idempotent maintenance pass on a workspace namespace to deduplicate redundant records, link superseded state, and promote recurring high-salience episodic memories to Semant…No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    Run an idempotent maintenance pass on a workspace namespace to deduplicate redundant records, link superseded state, and promote recurring high-salience episodic memories to Semantic tier (consumes 1 Write API call; non-destructive to unique facts) and return { namespace, consolidated }. Requires Write permission and a valid logical namespace (never prefixed with "org:"). Use at session wrap-up after multiple encode_memory calls; use feedback instead to rate one memory, or delete_by_context to purge obsolete tags.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • encode_memoryStore a single memory record in Memoria Cloud (consumes 1 Write API call; non-idempotent: encoding identical text twice creates separate IDs until consolidate is run) and return { …No findings

    Why it is in this group

    • The description's first verb is "store": a word for a change.
    Description, as the server wrote it
    Store a single memory record in Memoria Cloud (consumes 1 Write API call; non-idempotent: encoding identical text twice creates separate IDs until consolidate is run) and return { id, namespace, salience }. Defaults type to "episodic", salience to 0.5 (items >=0.7 or semantic/core surface in memory://rules), and namespace to "default" while rejecting reserved "org:" prefixes. Use when persisting one architectural decision, bug root cause, or user rule; use batch_encode instead for 2+ memories at once, or handoff_to_agent for cross-wing task handoffs.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • feedbackAdjust a memory salience weight based on recall utility (consumes 1 Write API call; non-idempotent because repeated calls compound the salience delta) and return { updated }.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
    Adjust a memory salience weight based on recall utility (consumes 1 Write API call; non-idempotent because repeated calls compound the salience delta) and return { updated }. Enforces organization ownership on id; useful=true boosts salience toward 1.0 while useful=false dampens noisy or outdated entries without deleting them. Use after recall_memories to tune future ranking quality; use forget_memory instead for permanent removal, or consolidate to merge duplicate records.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • handoff_to_agentPersist a high-salience (0.9) Semantic handoff memory into a target specialist wing namespace (wing:<target>) (consumes 1 Write API call; non-idempotent: repeated calls create dist…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
    Persist a high-salience (0.9) Semantic handoff memory into a target specialist wing namespace (wing:<target>) (consumes 1 Write API call; non-idempotent: repeated calls create distinct handoff records) and return { id, wing, namespace }. Accepts target wing via wing or alias to_wing (defaults to "architect") and sender via from_agent or alias from_wing (defaults to "agent"), attaching files and memory_ids as searchable context tuples. Use when delegating findings and next steps between architect, reviewer, qa, security, or ops agents; use encode_memory instead for general project memories.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • healthCheck Memoria Cloud service status, total organization memory count across all namespaces, and rolling 30-day API quota usage (read-only, idempotent; consumes 1 Read API call on to…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
    Check Memoria Cloud service status, total organization memory count across all namespaces, and rolling 30-day API quota usage (read-only, idempotent; consumes 1 Read API call on tools/call) and return { status, memory_count, used_calls_30d, api_call_limit }. Takes no parameters; api_call_limit is null on Unlimited plans. Use to verify connectivity and overall organization quota headroom; use stats instead when you need memory counts scoped to one specific project namespace.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • explain_codeSynthesize definitions, caller/callee references, related tests, and architectural notes for a specific code symbol in a namespace (read-only, idempotent; consumes 1 Read API call)…No findings

    Why it is in this group

    • The name "explain_code" says "explain": a word for reading.
    Description, as the server wrote it
    Synthesize definitions, caller/callee references, related tests, and architectural notes for a specific code symbol in a namespace (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } (up to 20 ranked matches). Pass the identifier via symbol or its equivalent alias target (if both are supplied, symbol takes precedence). Use before editing a known function, class, or module to check its blast radius and invariants; use search_code instead when you only have keywords and need to find symbol names first.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_agent_wingsList all five built-in specialist multi-agent wings (architect, reviewer, qa, security, ops), their isolated wing:<id> namespaces, and active memory counts (read-only, idempotent; …No findings

    Why it is in this group

    • The name "list_agent_wings" says "list": a word for reading.
    Description, as the server wrote it
    List all five built-in specialist multi-agent wings (architect, reviewer, qa, security, ops), their isolated wing:<id> namespaces, and active memory counts (read-only, idempotent; consumes 1 Read API call) and return { wings }. Always returns all five wings even when memory_count is 0. Use to inspect wing responsibilities and queued handoff volume before delegating work; use handoff_to_agent to record a new cross-wing handoff, or stats to inspect a custom project namespace.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • recall_memoriesRetrieve up to 20 deterministically ranked memory records for a query (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } with per-item { mem…No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieve up to 20 deterministically ranked memory records for a query (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } with per-item { memory, score }. Scores up to 500 candidates in namespace by lexical match (0.55), salience (0.30), and 30-day freshness (0.15) multiplied by tier boost (core=1.5x, semantic=1.25x), excluding items below min_salience. Use when you need individual memory IDs, metadata, or scores (for inspection, feedback, or forget_memory); use build_context instead for a ready-to-inject <memory_context> block, or search_code for code symbols.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_codeSearch indexed code symbol definitions, file paths, and reference memories within a namespace (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidat…Reads private dataNo findings

    Why it is in this group

    • The name "search_code" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "file": it reads files.
    Description, as the server wrote it
    Search indexed code symbol definitions, file paths, and reference memories within a namespace (read-only, idempotent; consumes 1 Read API call) and return { results, total_candidates } capped at 20 ranked { memory, score } hits. Requires code memories in namespace (populated via /memoria-sync-code or encode_memory) and rejects reserved "org:" prefixes. Use to discover where functions, classes, or routes live by keyword; use explain_code instead to inspect callers and invariants of a known symbol, or recall_memories for general prose rules.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • statsRetrieve the stored memory count for a single logical namespace alongside rolling 30-day organization quota metrics (read-only, idempotent; consumes 1 Read API call) and return { n…No findings

    Why it is in this group

    • The description's first verb is "retrieve": a word for reading.
    Description, as the server wrote it
    Retrieve the stored memory count for a single logical namespace alongside rolling 30-day organization quota metrics (read-only, idempotent; consumes 1 Read API call) and return { namespace, memory_count, used_calls_30d, api_call_limit }. Rejects reserved "org:" prefixes on namespace. Use when inspecting how many memories exist inside one specific project or wing namespace; use health instead for an organization-wide connectivity and total-memory check, or list_agent_wings for per-wing counts.

    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 data1
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.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 21, 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
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (2 destructive, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://memoria.kolivri.com/v1/mcp: tools/list returned 14 tools to an anonymous client, including forget_memory (destructive), delete_by_context (destructive), encode_memory (write), batch_encode (write), build_context (write) and 4 more

    What this check looks for

Posture changes

  1. Nov 21, 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 9
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

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.

  1. 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 -> 9 (and 2 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 9
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: no to not observed

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http memoria https://memoria.kolivri.com/v1/mcp
claude mcp add --transport http memoria https://memoria.kolivri.com/v1/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__memoria__recall_memories",
      "mcp__memoria__stats",
      "mcp__memoria__search_code",
      "mcp__memoria__explain_code",
      "mcp__memoria__list_agent_wings"
    ],
    "ask": [
      "mcp__memoria__encode_memory",
      "mcp__memoria__batch_encode",
      "mcp__memoria__build_context",
      "mcp__memoria__feedback",
      "mcp__memoria__consolidate",
      "mcp__memoria__health",
      "mcp__memoria__handoff_to_agent"
    ],
    "deny": [
      "mcp__memoria__forget_memory",
      "mcp__memoria__delete_by_context"
    ]
  }
}

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 memoria. Review it before you use it.

Capability tags behind 1 rule
  • mcp__memoria__search_code 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/io.github.kolivritech/memoria-mcp/verify?hash=2f233ec292eb8d3b9c1262504591b0119a25e25926d28fdeae1556fe176595d1" | jq -e '.changed == false'

Pinned hash 2f233ec292eb, from Nov 19, 2026, 11: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.kolivritech/memoria-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.kolivritech/memoria-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.kolivritech/memoria-mcp.svg)](https://radar.anlyon.com/servers/io.github.kolivritech/memoria-mcp)

Source: MCP Registry · repository. Synced Nov 19, 2026, 11:18 UTC.

Memoria — Deterministic AI Memory & Code Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Memoria — Deterministic AI Memory & Code Intelligence MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 9 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 Memoria — Deterministic AI Memory & Code Intelligence MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: forget_memory and delete_by_context.

Can the Memoria — Deterministic AI Memory & Code Intelligence 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 Memoria — Deterministic AI Memory & Code Intelligence MCP server have?

14 tools: 2 destructive, 7 write, 5 read. forget_memory, delete_by_context, encode_memory, batch_encode, build_context, feedback, consolidate, health and 6 more.

Does the Memoria — Deterministic AI Memory & Code Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Memoria — Deterministic AI Memory & Code Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Memoria — Deterministic AI Memory & Code Intelligence MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.