io.github.New1Direction/korg-recall-mcp
NPM · @KORGG/RECALL-MCP
Cross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning.
Available components
Last scanned (2 hours ago)
Scores higher than 65% of npm servers
Category Memory and Knowledge
Recent critical change
CVE-2026-41242 affects this package (3 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects protobufjs 6.11.6, reached via @xenova/transformers > onnxruntime-web > onnx-proto > protobufjs. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 61 of 170 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 158 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 187 tokens (~187/item across 1 items; 1 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +80
- CVE-2026-54269 affects this package: high ▼ security
- CVE-2026-44289 affects this package: high ▼ security
- CVE-2026-44288 affects this package: high ▼ security
- CVE-2026-44291 affects this package: high ▼ security
- CVE-2026-44292 affects this package: high ▼ security
- CVE-2026-44294 affects this package: high ▼ security
- CVE-2026-114112 affects this package: high ▼ security
- CVE-2026-48712 affects this package: high ▼ security
- CVE-2026-45740 affects this package: high ▼ security
- CVE-2026-114113 affects this package: high ▼ security
- CVE-2026-114111 affects this package: high ▼ security
- CVE-2026-44293 affects this package: high ▼ security
- CVE-2026-44290 affects this package: high ▼ security
- CVE-2026-41242 no longer affects this package ▲ security
- Known CVEs: CVE check failed: a known high-severity CVE affects protobufjs 6.11.6, reached via @xenova/transformers > onnxruntime-web > onnx-proto > protobufjs. A fixed version is available. security
- Score status: failed → scored ▲ functional
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.93 functional
- 17 Oct 26 0
- Stability: 0.77 → pass security
- 16 Oct 26 0
- Stability: pass → 0.77 functional
- 15 Oct 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/@korgg/recall-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 13 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2pr8-phx7-x9h3 | CVE-2026-44294 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-66ff-xgx4-vchm | CVE-2026-44293 | high | yes | |
| GHSA-685m-2w69-288q | CVE-2026-44289 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-75px-5xx7-5xc7 | CVE-2026-44291 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-f38q-mgvj-vph7 | CVE-2026-54269 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-fx83-v9x8-x52w | CVE-2026-44292 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-jggg-4jg4-v7c6 | CVE-2026-45740 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | yes |
| GHSA-jvwf-75h9-cwgg | CVE-2026-44290 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-q6x5-8v7m-xcrf | CVE-2026-44288 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-wcpc-wj8m-hjx6 | CVE-2026-48712 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-f88m-g3jw-g9cj | CVE-2026-114113 | high | yes | |
| GHSA-rgj7-g3m4-5g8c | CVE-2026-114112 | high | yes | |
| GHSA-wq5f-xc86-pv6w | CVE-2026-114111 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 170 packages
| Packages resolved | 170 |
|---|---|
| Deprecated | 1 |
| Stale | 60 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
recall ~187
Search across all prior AI sessions recorded in the korg ledger. Returns relevant past prompts, model replies, and tool calls/results. Use this BEFORE attempting work that may have been done before — finding the prior session saves the cost of rediscovery.
| Name | Type | Req | Description |
|---|---|---|---|
| min_score | number | – | Cosine-similarity floor for semantic matches (default 0.30). Ignored for substring mode. |
| mode | string | – | auto: semantic if @xenova/transformers installed else substring. semantic: require embedding-backed ranking. substring: pure keyword AND-of-terms. |
| query | string | yes | Natural-language description of what you're looking for. |
| tool_filter | array | – | Optional list of tool_name values to restrict the search to (e.g. ['user_prompt'], ['Read', 'Bash']). |
| top_n | integer | – | Max number of results (default 5). |
No output schema declared.
No examples provided.
How do I install the io.github.New1Direction/korg-recall-mcp server?
io.github.New1Direction/korg-recall-mcp runs locally as an npm package, launched with npx -y @korgg/recall-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @korgg/recall-mcp
claude mcp add new1direction-korg-recall-mcp -- npx -y @korgg/recall-mcp
What is the io.github.New1Direction/korg-recall-mcp server?
io.github.New1Direction/korg-recall-mcp is listed in the public MCP registry as io.github.New1Direction/korg-recall-mcp. Cross-vendor semantic memory: recall across Claude Code / Codex / Grok sessions by meaning. This page covers its npm package (@korgg/recall-mcp).
Is the io.github.New1Direction/korg-recall-mcp server safe to use?
io.github.New1Direction/korg-recall-mcp scores 80 out of 100 on VerifyMCP. We recorded 13 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.New1Direction/korg-recall-mcp server expose?
io.github.New1Direction/korg-recall-mcp exposes 1 tool: recall. Their descriptions and schemas cost roughly 187 tokens of context every time the server is loaded.
Is the io.github.New1Direction/korg-recall-mcp server still maintained?
io.github.New1Direction/korg-recall-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.New1Direction/korg-recall-mcp server under?
io.github.New1Direction/korg-recall-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.