Stellar Memory
NPM · STELLAR-MEMORY · SCANNED SEP 29
Persistent AI memory using orbital mechanics. 100% local, zero API keys, MCP-native.
Available components
Recent critical change
CVE-2026-41242 affects this package (2 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 Security67
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Declares code that runs automatically (preinstall, postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 62 of 178 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 184 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1020 tokens (~60/item across 17 items; 16 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "consolidate" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 17 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
How do I install the Stellar Memory MCP server?
Stellar Memory runs locally as an npm package, launched with npx -y stellar-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · stellar-memory
claude mcp add sangjun0000-stellar-memory -- npx -y stellar-memory
{
"mcpServers": {
"sangjun0000-stellar-memory": {
"command": "npx",
"args": [
"-y",
"stellar-memory"
]
}
}
} {
"servers": {
"sangjun0000-stellar-memory": {
"command": "npx",
"args": [
"-y",
"stellar-memory"
]
}
}
} codex mcp add sangjun0000-stellar-memory -- npx -y stellar-memory
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sangjun0000-stellar-memory": {
"type": "local",
"command": [
"npx",
"-y",
"stellar-memory"
],
"enabled": true
}
}
} openclaw mcp add sangjun0000-stellar-memory --command npx --arg -y --arg stellar-memory
mcp_servers:
sangjun0000-stellar-memory:
command: "npx"
args: ["-y", "stellar-memory"] {
"McpServers": {
"sangjun0000-stellar-memory": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"stellar-memory"
]
}
}
} assistant mcp add sangjun0000-stellar-memory -t stdio -c npx -a -y stellar-memory
{
"mcpServers": {
"sangjun0000-stellar-memory": {
"command": "npx",
"args": [
"-y",
"stellar-memory"
]
}
}
} 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.
- 29 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: pass → 0.80 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 11 Sept 26 0
- Stability: pass → 0.77 functional
- 10 Sept 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 29 Sept 2026 · Analysed npm/stellar-memory@1.0.3
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 →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| preinstall | unreviewed | node scripts/check-node.mjs |
| postinstall | unreviewed | node scripts/setup.mjs || true |
Background: Why install scripts are a supply-chain risk →
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-xq3m-2v4x-88gg | CVE-2026-41242 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-f88m-g3jw-g9cj | high | yes | ||
| GHSA-rgj7-g3m4-5g8c | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 178 packages
| Packages resolved | 178 |
|---|---|
| Deprecated | 1 |
| Stale | 61 |
| 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 →
analytics ~54
Memory analytics: health, topics, survival, or movements.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (for movements report). |
| project | string | – | Project to analyse. |
| report | string | yes | Report type. |
No output schema declared.
No examples provided.
commit ~84
Save session state (work, decisions, next steps, errors) to the Sun.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Additional project background. |
| current_work | string | yes | What is currently being worked on. |
| decisions | array | – | Decisions made this session. |
| errors | array | – | Active errors or blockers. |
| next_steps | array | – | Concrete next actions for future sessions. |
No output schema declared.
No examples provided.
consolidate ~35
Merge similar memories to reduce noise.
| Name | Type | Req | Description |
|---|---|---|---|
| dry_run | boolean | – | Preview candidates without merging. |
| project | string | – | Target project. |
No output schema declared.
No examples provided.
constellation ~66
Explore the knowledge graph between memories.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | "graph" (default), "related", or "extract". |
| depth | integer | – | Graph traversal depth. |
| id | string | yes | Memory ID to explore. |
| limit | integer | – | Max related memories to return. |
No output schema declared.
No examples provided.
daemon ~24
Start or stop the background scheduler.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform. |
No output schema declared.
No examples provided.
export ~45
Export memories as JSON or Markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Output format. |
| type | string | – | Filter by memory type. |
| zone | string | – | Filter by orbital zone. |
No output schema declared.
No examples provided.
forget ~51
Push a memory further from the Sun or soft-delete it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory ID to forget. |
| mode | string | – | "push" moves to Oort Cloud; "delete" permanently removes. |
No output schema declared.
No examples provided.
galaxy ~94
Manage projects: switch, list, create, stats, or universal memories.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform. |
| is_universal | boolean | – | Mark as universal (true) or project-specific (false). |
| limit | integer | – | Max results for universal_context. |
| memory_id | string | – | Memory ID (required for mark_universal). |
| project | string | – | Project name (required for switch/create). |
No output schema declared.
No examples provided.
observe ~36
Extract memories from conversation text automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| conversation | string | yes | Conversation text to extract memories from. |
| project | string | – | Target project. |
No output schema declared.
No examples provided.
orbit ~17
Recalculate all memory positions based on current importance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recall ~97
Search memories. Matching results are pulled closer to the Sun.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | ISO date — return memories active at this point in time instead. |
| include_universal | boolean | – | Include universal memories from other projects. |
| limit | integer | – | Max results to return. |
| max_au | number | – | Max distance in AU. |
| query | string | yes | Search query. |
| type | string | – | Filter by memory type. |
No output schema declared.
No examples provided.
remember ~88
Store a new memory. Auto-placed by type and impact.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full memory content. |
| impact | number | – | Impact score 0.0–1.0. |
| summary | string | – | One-line summary (default: first 50 chars of content). |
| tags | array | – | Tags for search and categorization. |
| type | string | – | Memory type. |
No output schema declared.
No examples provided.
resolve_conflict ~86
List, resolve, or dismiss memory conflicts.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform. |
| conflict_id | string | – | Conflict ID (required for resolve/dismiss). |
| project | string | – | Target project. |
| resolution | string | – | How the conflict was resolved. |
| resolve_action | string | – | "supersede", "dismiss", or "keep_both". |
No output schema declared.
No examples provided.
scan ~65
Register and scan local data sources.
| Name | Type | Req | Description |
|---|---|---|---|
| git | boolean | – | Also import git commit history. |
| max_kb | integer | – | Max file size in KB to process. |
| path | string | yes | Directory path to scan. |
| recursive | boolean | – | Recurse into subdirectories. |
No output schema declared.
No examples provided.
status ~53
View memories grouped by orbital zone.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max memories to return. |
| show | string | – | Show memories, data sources, or both. |
| zone | string | – | Filter to a specific orbital zone. |
No output schema declared.
No examples provided.
temporal ~105
Time-based queries: point-in-time recall, evolution chains, or bounds.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to perform. |
| memory_id | string | – | Memory ID (required for chain/set_bounds). |
| project | string | – | Target project. |
| timestamp | string | – | ISO date (required for action="at"). |
| valid_from | string | – | ISO date — when the memory became valid. |
| valid_until | string | – | ISO date — when the memory stopped being valid. |
No output schema declared.
No examples provided.
What is the Stellar Memory MCP server?
Stellar Memory is an MCP server listed in the public MCP registry as io.github.sangjun0000/stellar-memory. Persistent AI memory using orbital mechanics. 100% local, zero API keys, MCP-native. This page covers its npm package (stellar-memory).
What tools does the Stellar Memory MCP server expose?
Stellar Memory exposes 16 tools: status, commit, recall, remember, orbit, and 11 more. Their descriptions and schemas cost roughly 1,000 tokens of context every time the server is loaded.
Is the Stellar Memory MCP server still maintained?
Stellar Memory is still listed as active in the MCP registry. We last reached this channel on 29 September 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 Stellar Memory MCP server under?
Stellar Memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.