thron-memory
NPM · THRON-MEMORY
One private memory for all your AI apps, on your phone and computer. Part of ThronOS.
Available components
Last scanned (12 hours ago)
Scores higher than 39% of npm servers
Category Memory and Knowledge
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- 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 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 686 tokens (~114/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 14 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 13 Nov 26 53
First indexed and scored.
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 21 Nov 2026 · Analysed npm/thron-memory@0.2.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 →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
overview ~43
Start here, once per task. Returns the user's core rules for agents, every page (id, title, one-line summary, last update), inbox size and pages in conflict.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read ~63
Read one page, or one section of it (e.g. Current, History, Open questions). Prefer a section when you only need part.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | Page id, e.g. "alex-kim" |
| section | string | – | Optional section name |
No output schema declared.
No examples provided.
remember ~183
Save one durable fact. With page: added to that page's Current section (the page is created if new). Without page: goes to the inbox to be filed later. Write it as a plain sentence with no date; the date and source are added for you.
| Name | Type | Req | Description |
|---|---|---|---|
| fact | string | yes | The fact in plain words, e.g. "Prefers morning meetings" |
| page | string | – | Page id it belongs on, lowercase-with-hyphens, e.g. "alex-kim". Omit if unsure. |
| section | string | – | Section to add to (default Current; use Open questions for unresolved conflicts) |
| source | string | – | Where it came from, e.g. "user in chat", "email 2026-11-02" |
| title | string | – | Title for a new page, e.g. "Alex Kim" |
No output schema declared.
No examples provided.
search ~70
Find facts. Returns short snippets (page > section: text) ranked by match, not whole pages. Read a page or section only when a snippet looks relevant.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Words to look for, e.g. "alex birthday" or "deploy steps" |
No output schema declared.
No examples provided.
update_fact ~111
Change a fact that is no longer true. Replaces the line containing old_text with new_text and moves the old line to History with today's date. Use this instead of deleting.
| Name | Type | Req | Description |
|---|---|---|---|
| new_text | string | yes | The new fact (plain sentence; date added for you). Empty string to retire the fact without a replacement. |
| old_text | string | yes | A unique piece of the line to replace |
| page | string | yes | Page id |
| source | string | – | Where the new fact came from |
No output schema declared.
No examples provided.
write_page ~94
Rewrite a whole page: for filing the inbox, merging duplicates, reorganizing, or setting status (current, conflict, archived). Read the page first. The previous version is kept automatically. Keep the format: header with title/updated/status, a short summary, then ## sections (Current, History, Open questions).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full Markdown content of the page |
| page | string | yes | Page id |
No output schema declared.
No examples provided.
How do I install the thron-memory MCP server?
thron-memory runs locally as an npm package, launched with npx -y thron-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 · thron-memory
claude mcp add jacobbarglof-thron-memory -- npx -y thron-memory
What is the thron-memory MCP server?
thron-memory is an MCP server listed in the public MCP registry as io.github.jacobbarglof/thron-memory. One private memory for all your AI apps, on your phone and computer. Part of ThronOS. This page covers its npm package (thron-memory).
Is the thron-memory MCP server safe to use?
thron-memory scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 thron-memory MCP server expose?
thron-memory exposes 6 tools: overview, search, read, remember, update_fact, write_page. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.
Is the thron-memory MCP server still maintained?
thron-memory is still listed as active in the MCP registry. We last reached this channel on 21 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 thron-memory MCP server under?
thron-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.
What did VerifyMCP test on the thron-memory MCP server?
VerifyMCP ran 15 checks on thron-memory, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about thron-memory: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.