Skip to content

MCP servers › io.github.kolivritech › memoria-mcp

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

memoria-mcp MCP server

Registry name io.github.kolivritech/memoria-mcp

Memoria — Deterministic AI Memory & Code Intelligence MCP — the publisher's title

by kolivritech · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗

Official Node.js MCP connector for Memoria Cloud (https://memoria.kolivri.com). — the publisher's description

7 of 9 record checks metRead-only · tools listed 2026-11-19version 1.0.2JavaScriptMITstandard input/output, streamable HTTP14 tools

Summary

io.github.kolivritech/memoria-mcp is a remote and local MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the GitHub account kolivritech. Its linked repository, github.com/kolivritech/memoria-mcp, belongs to the same GitHub account. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 14 tools, 3 resources and 1 prompt.

Record checks

7 of 9 record checks met

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: no download figure available
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Your own values
for the package, a secret: MEMORIA_API_KEY
Sign-in
none needed to open a session
Package
npm · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Tools
14
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (memoria.kolivri.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.2).

Add to your client

Observed fact

This server accepted a session without any credential and lists 2 tools whose name or declaration suggests they change data (forget_memory, delete_by_context). That is our reading of the names; we did not call them. Source: our connection, 2026-11-19.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
1.0.2, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-14 to 2026-11-19; 2 in the 90 days before the 2026-11-19 snapshot.
Most recent 2 versions
  • 1.0.2 · 2026-11-19
  • 1.0.0 · 2026-11-14
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.0 (published 2026-11-14) → 1.0.2 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher published no GitHub release note for version 1.0.2: the repository has no release tagged for it.

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

What does this server offer?

Observed inventory
14tools
3resources
1prompts

None of its 14 tools are described as changing anything. For 14 the reading was uncertain, so no mark is shown.

  • encode_memory

    “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, sali…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    5 inputs, 2 required
    • namespacestringrequired“Logical project or workspace namespace (defaults to "default"; never prefix with "org:").”
    • contentstringrequired“Non-empty memory text to persist.”
    • typestring“Memory tier classification (core and semantic receive 1.5x/1.25x recall boosts).”
    • saliencenumber“Importance weight from 0.0 to 1.0 (use >=0.7 for durable team rules).”
    • contextarray“Optional [key, value] string pairs (for example [["file", "src/auth.js"]]) targetable by delete_by_context.”
  • batch_encode

    “Store multiple memories atomically in one request (consumes max(1, memories.length) Write API calls; non-idempotent) and return { ids, encoded }.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 1 required
    • namespacestring“Fallback logical workspace namespace applied to batch items that omit namespace.”
    • memoriesarrayrequired“Non-empty array of memory objects ({ content, type?, salience?, namespace?, context?”
  • recall_memorieson 5 other servers

    “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 }.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 2 required
    • namespacestringrequired“Logical workspace namespace to search (defaults to "default"; never prefix with "org:").”
    • querystringrequired“Keywords or natural-language topic to match against stored memory content.”
    • token_budgetnumber“Advisory token budget hint for downstream context sizing (default 4096).”
    • min_saliencenumber“Minimum salience filter (0.0-1.0); memories strictly below this value are excluded.”
  • build_context

    “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 }.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 2 required
    • namespacestringrequired“Logical workspace namespace to ground context around (never prefix with "org:").”
    • querystringrequired“Active task, feature, or session topic used to rank relevant facts and history.”
    • token_budgetnumber“Maximum token budget (~4 characters per token, default 4096) before truncating lower-ranked items.”
  • forget_memoryon 5 other servers

    “Permanently delete one memory and its incident graph edges by ID (destructive, idempotent; consumes 1 Write API call) and return { deleted }.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“Exact memory UUID returned by encode_memory or recall_memories.”
  • delete_by_context

    “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 }.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 2 required
    • namespacestring“Optional logical namespace filter; omit to match across the entire organization.”
    • keystringrequired“Exact context tuple key to match (for example "file" or "pr").”
    • valuestringrequired“Exact context tuple value to match (for example "src/legacy.js").”
  • “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 }.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    2 inputs, 2 required
    • idstringrequired“Target memory UUID from recall_memories.”
    • usefulbooleanrequired“True to boost salience when helpful; false to dampen salience when stale or noisy.”
  • “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…”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • namespacestringrequired“Logical workspace namespace to consolidate (for example "my-project").”
  • “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 retur…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “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_co…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • namespacestringrequired“Logical workspace namespace to inspect (for example "my-project" or "wing:qa").”
  • “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 r…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • namespacestringrequired“Logical repository or workspace namespace to search (never prefix with "org:").”
    • querystringrequired“Function, class, route, or file keyword to locate.”
  • explain_codeon 4 other servers

    “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 { resul…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • namespacestringrequired“Logical repository or workspace namespace containing indexed code memories.”
    • symbolstring“Exact function, class, or module name to explain (preferred; equivalent to target).”
    • targetstring“Alias for symbol accepted for client compatibility when symbol is omitted.”
Show 2 more tools
  • list_agent_wings

    “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…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • namespacestring“Optional logical workspace namespace context (never prefix with "org:").”
  • handoff_to_agent

    “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 record…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    8 inputs, 1 required
    • wingstring“Destination specialist wing (preferred; defaults to "architect" if both wing and to_wing are omitted).”
    • to_wingstring“Alias for destination wing used when wing is omitted.”
    • from_agentstring“Identifier of the sending agent or role (preferred; defaults to "agent").”
    • from_wingstring“Alias for sending specialist wing used when from_agent is omitted.”
    • summarystringrequired“Required concise summary of architectural findings, constraints, and state.”
    • taskstring“Optional concrete follow-up action appended for the receiving wing.”
    • filesarray“Optional file paths attached as ["file", path] context tags.”
    • memory_idsarray“Optional related memory UUIDs attached as ["memory_id", id] context tags.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 36
Tools with a description
100% of 14
Typical description length
515 characters

The tool set

Counted from the listing

Tools
14
Size of the list
about 5,051 tokens for an agent to load (characters ÷ 4)
Naming
10 of 14 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 14 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @kolivri/memoria-mcp

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "memoria-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "<MEMORIA_API_KEY>"
      }
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "memoria-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "<MEMORIA_API_KEY>"
      }
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "memoria-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "${input:memoria-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "memoria-api-key",
      "description": "MEMORIA_API_KEY",
      "password": true
    }
  ]
}
Claude Code
claude mcp add --env "MEMORIA_API_KEY=<MEMORIA_API_KEY>" --transport stdio memoria-mcp -- npx -y @kolivri/memoria-mcp@1.0.2
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "memoria-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "<MEMORIA_API_KEY>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "memoria-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "<MEMORIA_API_KEY>"
      }
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.memoria-mcp]
command = "npx"
args = ["-y", "@kolivri/memoria-mcp@1.0.2"]

[mcp_servers.memoria-mcp.env]
"MEMORIA_API_KEY" = "<MEMORIA_API_KEY>"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "memoria-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@kolivri/memoria-mcp@1.0.2"
      ],
      "env": {
        "MEMORIA_API_KEY": "<MEMORIA_API_KEY>"
      }
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "MEMORIA_API_KEY=<MEMORIA_API_KEY>" -- npx -y @kolivri/memoria-mcp@1.0.2
  • Replace <MEMORIA_API_KEY> with your own values; the entry marks MEMORIA_API_KEY as secret, so keep the file out of version control.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-19 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://memoria.kolivri.com/v1/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "memoria-mcp": {
      "url": "https://memoria.kolivri.com/v1/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "memoria-mcp": {
      "type": "http",
      "url": "https://memoria.kolivri.com/v1/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"memoria-mcp","type":"http","url":"https://memoria.kolivri.com/v1/mcp"}'
Claude Code
claude mcp add --transport http memoria-mcp https://memoria.kolivri.com/v1/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "memoria-mcp": {
      "type": "streamableHttp",
      "url": "https://memoria.kolivri.com/v1/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "memoria-mcp": {
      "httpUrl": "https://memoria.kolivri.com/v1/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.memoria-mcp]
url = "https://memoria.kolivri.com/v1/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "memoria-mcp": {
      "url": "https://memoria.kolivri.com/v1/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://memoria.kolivri.com/v1/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
1.0.2
Latest stable
1.0.2
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-19 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-I1Cx3wqrj2x85pnuJ…
Signature
signed
License
MIT

Source: the package registry · 2026-11-19.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Install-time script (npm). No install-time script in the published package.json (version 1.0.2). Source: read 2026-11-19.
  • Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: read 2026-11-19.
  • Node.js version (npm). Needs Node 18 or later (engines.node >=18.0.0). Source: read 2026-11-19.
  • MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list @modelcontextprotocol/sdk or any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: read 2026-11-19.
  • Build workflow. No build provenance published for this version. Source: read 2026-11-19.

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint memoria.kolivri.com/v1/mcpSession openedmatchesour test · 2026-11-19
A secret is declared as requiredOpened a session without any credentialdiffersour test · 2026-11-19
Version 1.0.2 on npmExists and can be installedmatchesnpm · 2026-11-19
Repository github.com/kolivritech/memoria-mcpOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.kolivritech · 2 servers
GitHub owner
an organization (kolivritech)
Build record
signed
Repository
github.com/kolivritech/memoria-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-14.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint memoria.kolivri.com/v1/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-11-14 to 2026-11-19; versions 1.0.0 to 1.0.2).

Last change seen between our reads on 2026-11-14 (version 1.0.0) and 2026-11-19 (version 1.0.2).

Changed (14):

batch_encode: description, input schemabuild_context: description, input schemaconsolidate: description, input schemadelete_by_context: description, input schemaencode_memory: description, input schemaexplain_code: description, input schemafeedback: description, input schemaforget_memory: description, input schemahandoff_to_agent: description, input schemahealth: descriptionlist_agent_wings: description, input schemarecall_memories: description, input schemasearch_code: description, input schemastats: description, input schema

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

7 of 9 record checks met

  • Not ranked by downloads: no download figure available
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-14). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.kolivritech/memoria-mcp

Answered from the data above

Who publishes io.github.kolivritech/memoria-mcp?

The registry ties the namespace io.github.kolivritech to the GitHub account kolivritech; only its owner can publish under it. Its linked repository, github.com/kolivritech/memoria-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.kolivritech/memoria-mcp safe to install?

We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.kolivritech/memoria-mcp need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares a required secret.

Has io.github.kolivritech/memoria-mcp been security tested?

Partly. 4 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does io.github.kolivritech/memoria-mcp publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 1.0.2, the latest stable release on npm.

Where is the source code of io.github.kolivritech/memoria-mcp?

In github.com/kolivritech/memoria-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

4 exercised12 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,459 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 14 tools, 3 resources, 1 prompt.
  4. 6,093 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
prompts, resources, tools
our test · 2026-11-19
Transport
standard input/output, streamable HTTP
registry · 2026-11-19
Required credentials
requires a secret
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
registry · 2026-11-19
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
package registry · 2026-11-19
Integrity hash
declared (sri)
package registry · 2026-11-19
Signature / provenance
signed
package registry · 2026-11-19
Dependency advisories
none known
npm audit · 2026-11-19
Popularity
not stated
npm has no download count yet: the package is 0 days old (the downloads API answered 404 on 4 asks)
Publisher signals
owner: an organization · repository age: 0–30 days · stars: 0–9 · build record: signed
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
either (remote or your machine)
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.kolivritech/memoria-mcp: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.kolivritech/memoria-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 7 of 9 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.kolivritech/memoria-mcp)](https://protocolprobe.com/mcp/servers/io.github.kolivritech/memoria-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology