# loreweave

Durable agent memory over a markdown vault: bitemporal facts, timelines, hybrid graph search.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.38.0
- **Author:** io.github.lets-order-some-fries
- **License:** Unknown
- **npm:** loreweave
- **Source:** https://github.com/lets-order-some-fries/loreweave
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 9 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T18:33:12.030Z
- **Version scanned:** 0.38.0
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `lore_search` — Hybrid retrieval over the markdown vault: BM25 + knowledge-graph spreading activation (+ dense embeddings when configured). Returns one passage per note — the s
- `lore_context_pack` — Progressive-disclosure primer: vault stats, top entities, recently modified notes, currently-valid facts, and (if topic given) top search hits. Call once at ses
- `lore_read_note` — Read the raw markdown of a note by vault-relative path (as returned in search results). Never reads outside the vault — a path that escapes it, including throug
- `lore_assert_fact` — Record an atomic fact (subject :: predicate :: object) with bitemporal validity. Contradicting facts in the same slot are superseded automatically (never delete
- `lore_invalidate_fact` — Close the currently-valid fact in a (subject, predicate) slot without asserting a replacement — e.g. "no longer true". Journalled; history preserved.
- `lore_resume` — What changed since this tool was last called: notes edited, facts asserted, and knowledge updates (slot: old → new). Call once at session start to continue wher
- `lore_review` — Important-but-fading knowledge: blocks whose retrievability has decayed below the threshold despite mattering, plus long-untouched open facts. This is the space
- `lore_timeline` — Chronological history of an entity in one call: every value change from the bitemporal fact store (with what each value replaced and when it stopped holding) me
- `lore_query_facts` — Query the bitemporal fact store. Default: currently-valid facts. asOf answers "what was true on DATE", asKnownAt answers "what did we know on DATE"; includeHist
- `lore_aggregate_facts` — Deterministic aggregation over fact history — counts grouped by object/subject/predicate with date-range filters. Use for "how many X", "which Y most often" que
- `lore_capture` — Append a timestamped line to lore/inbox.md (or another vault note). Use for fleeting observations worth keeping that are not atomic facts. The captured text is 
- `lore_mark_used` — Reinforce passages that actually contributed to your answer (spaced-repetition signal: used memories decay slower). Call after citing a note.
- `lore_dream_report` — Run the consolidation pass: duplicate passages, contradicting/recently-changed facts, stale knowledge needing review, suggested missing links, orphan notes. Lea
- `lore_propose_facts` — Returns candidate facts mined from a note's structure that are NOT yet in the fact store, for you to adjudicate. The engine only auto-accepts unambiguous field 
- `lore_index` — Incrementally sync the markdown vault into the index. Call after writing files to the vault through anything OTHER than lore_* tools (an editor, another agent, 

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"loreweave\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"loreweave\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/loreweave
- Install plan: https://forgeregistry.com/api/v1/packages/loreweave/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/loreweave
- HTML page: https://forgeregistry.com/registry/loreweave
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.