MCP.Market

Korg Recall MCP server

by New1Direction·io.github.New1Direction/korg-recall-mcp·v0.1.1·4 stars

Cross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

4 stars

Reviews

Write one

Nobody has reviewed Korg Recall yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Korg Recall tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • recall

    Search across all prior AI sessions recorded in the korg ledger.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 95 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Korg Recall compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
4
more than 82% of 28,688 servers

What its tools let an agent do: 1 read

Install Korg Recall in Claude Code, Cursor or VS Code

Runs npx -y @korgg/recall-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add korg-recall-mcp -- npx -y @korgg/recall-mcp
Add to Cursor

What the publisher says

From the Korg Recall repository's README, as published. We do not edit it. Read it on GitHub

korg

A causally-ordered, rewindable event-ledger for autonomous AI agents. Every step your AI agent takes, recorded in a hash-chained ledger you can independently verify — tamper-evident, zero trust, no blockchain.

English · 简体中文 · 繁體中文

AI agents are black boxes. When they fail, you can't debug. When they succeed, you can't reproduce it.

When they do something wrong, you can't undo it.

Korg fixes this.

What Korg Does

[!NOTE]

Universal Ingestion Integration Mode:

Korg v1 is an MCP-callable audit sink. Any MCP-compatible coding agent (Claude Code, Codex, etc.) can call korg's tools to record its session as a causally-linked, replayable, rewindable ledger. The agent must be instructed to log its actions — typically via system prompt or MCP server configuration. Fully passive auditing without agent cooperation is on the roadmap for future versions.

[!WARNING]

Trust Boundary & Deployment Scope:

Korg v1 is designed strictly for local, single-user workspaces. Multi-tenant and networked deployments require cryptographic authentication and permission bounds that are not yet shipped. Running the server on an untrusted or public network exposes workspace read/write access.

Korg is a cognitive hypervisor — a runtime layer that sits beneath your AI agents and governs every decision they make.

It doesn't replace your LLM. It governs what the LLM does.

Foundation Model          →  predicts, suggests, generates
────────────────────────────────────────────────────────────
Korg Cognitive Runtime    →  schedules, validates, isolates,
                             reconciles, replays, heals, governs

Every agent action is:

  • Appended to an immutable, cryptographically-signed ledger
  • Ordered with Hybrid Logical Clocks (causal, deterministic, globally consistent)
  • Replayable — rebuild exact state at any point in history
  • Reversible — rewind the ledger to any prior sequence point

Try the Time-Travel Demo

You can run the built-in sandbox demo to see cognitive time-travel in action. The demo sets up a temporary workspace with a buggy Python script, lets a simulated coding agent make a wrong edit, catches the test failure, rewinds the workspace and ledger to before the edit, and speculatively commits the correct fix:

cargo run -- demo

You will see the complete, colorized time-travel sequence:

⚡ STARTING KORG COGNITIVE TIME-TRAVEL DEMO ⚡
────────────────────────────────────────────────────────────────────────────────
[korg] Initializing sandboxed demo environment...
[korg] Created temporary workspace with math_utils.py (subtraction bug present).

🚀 PHASE 1: AGENT INITIATES RUN (WRONG PATH)
  [seq 390] actor: agent:claude-code@0.2.29 | tool: user_prompt | prompt: "Fix subtraction bug and verify tests pass"
  [seq 391] actor: agent:claude-code@0.2.29 | tool: Read        | file: math_utils.py
  [seq 392] actor: agent:claude-code@0.2.29 | tool: Edit        | result: "Modified return a + b (wrong fix)"
  [seq 393] actor: agent:claude-code@0.2.29 | tool: Bash        | command: "pytest" -> ❌ FAILED (2 tests failed)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Korg Recall: common questions

Is Korg Recall MCP server safe?
Mostly: it is graded B (78/100). Read the Korg Recall safety report
How do I install Korg Recall?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Korg Recall need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Korg Recall maintained?
The last commit was 132 days ago (2026-06-24). The latest release is v0.1.1.
What can I use instead of Korg Recall?
Servers from other publishers that do the same job: Deja Vu MCP server and Claudexor MCP server.
How does Korg Recall compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Korg Recall

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • Claudexor
    Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.
    A

More from New1Direction →