Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Engrams is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
trust score
1
downloads a day
local
runs on your machine
54
downloads in 30d
What it does
Universal AI memory layer — MCP server with persistent, cross-tool memory for Claude Code, Cursor, Windsurf, and more
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user engrams-mcp '--' npx -y engrams
# 2 — ask your agent for something these tools do
# memory_write, memory_bulk_upload, memory_write_snippet and 37 more
Engrams costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SLAll 1 server
sunrise-labs-dot-ai1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Engrams as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user engrams-mcp '--' npx -y engramsReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
40 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Store a new memory. If a similar memory already exists, returns the existing memory and resolution options instead of writing immediately. Call again with
No parameter schema on file.
Upload many memories at once, bypassing dedup by default. Designed for imports from canonical external sources (Google Contacts, ChatGPT export, a contacts CSV) where the caller has already deduped against its own source. Each entry
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Check the staleness of indexed documents. Returns which documents haven
No parameter schema on file.
Search the user
No parameter schema on file.
Token-budget-aware context search optimized for LLM consumption. Returns memories packed into a specified token budget, organized hierarchically or as a narrative block.
No parameter schema on file.
Report which memories from a prior memory_context call you actually cited vs. filtered as noise. Call this BEFORE ending your turn — unrated retrievals are wasted learning signal. Pass the
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Delete a memory the user no longer wants stored. Call when the user explicitly asks to forget something.
No parameter schema on file.
Soft-delete many memories at once, scoped by a filter. Use to retire benchmark / test data, drop a whole domain, or de-pollute by entity name. ALWAYS dry-runs first by default — pass dryRun=false explicitly to commit. Filter requires at least one of
No parameter schema on file.
Confirm a memory is still accurate. Call this when you act on a memory and the user validates it was correct, or when the user reaffirms something you already know.
No parameter schema on file.
Replace a memory
No parameter schema on file.
Flag a memory as wrong or outdated. Call this when you act on a memory and the outcome was incorrect, or when the user says a memory is no longer true. Degrades confidence by 0.15.
No parameter schema on file.
Create a relationship between two memories. When
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Split a memory that contains multiple distinct facts into separate memories. Call this when a memory covers more than one topic or would be more useful as individual pieces. Each new memory inherits the original
No parameter schema on file.
Scan a memory for sensitive data (PII, API keys, etc.) and optionally redact it. Use this to check memories before sharing or to clean up accidentally stored secrets.
No parameter schema on file.
Get all connections for a memory
No parameter schema on file.
List all memory domains with counts. Returns per-domain metadata: count of memories, whether it
No parameter schema on file.
Board advisory work
No parameter schema on file.
Archive a life domain. Active snippets are preserved. Future memory_write_snippet calls to this domain are rejected until it is unarchived via memory_register_domain. Requires write permission on the target domain. Returns status=
No parameter schema on file.
Browse the user
No parameter schema on file.
Fetch one or more memories by ID (returns full record contents — including any PII). Use when you have a memory ID from a prior search/context call, a deeplink, or another tool
No parameter schema on file.
No parameter schema on file.
Export memories as JSON for migration to another Lodis instance. Returns paginated results — call repeatedly with increasing offset until hasMore is false. Use with memory_import (source_type:
No parameter schema on file.
List unclassified memories that need entity_type assignment. Returns memories without entity types so you can classify them using memory_update. Use this to find memories that need classification.
No parameter schema on file.
List all known entities grouped by type. Useful for discovering what the system knows about people, organizations, projects, etc.
No parameter schema on file.
Set per-agent read/write permissions for a domain
No parameter schema on file.
Pin a memory as canonical — permanent knowledge that is immune to confidence decay. Use for confirmed facts, preferences, skills, or lessons that should never fade.
No parameter schema on file.
Archive a memory — preserves it for reference but deprioritizes it in search results. Confidence is frozen. Use for completed project context or outdated but historically relevant information.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Migrate memories between local and cloud storage. Use
No parameter schema on file.
Interactive tutorial for learning how Lodis works. Call with no args for a table of contents, or with a chapter id (e.g.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Engrams or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 96 / 100
Release 0.5.1 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 3 capability
Capabilitymoderate
Coveragesource
Verificationrepo
Surface digest4af9a4914df7f3eada38c32fe54eed4c4477c16295d17e012523e0a12e91c600
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| memory_write | no tags | |
| memory_index | no tags | |
| memory_index_status | untrusted-input | untrusted-input: keyword "crawl" |
| memory_search | no tags | |
| memory_context | no tags | |
| memory_briefing | no tags | |
| memory_update | no tags | |
| memory_remove | no tags | |
| memory_confirm | no tags | |
| memory_correct | no tags | |
| memory_flag_mistake | no tags | |
| memory_connect | no tags | |
| memory_split | no tags | |
| memory_scrub | no tags | |
| memory_get_connections | no tags | |
| memory_list_domains | no tags | |
| memory_list | untrusted-input | untrusted-input: keyword "browse" |
| memory_export | no tags | |
| memory_classify | no tags | |
| memory_list_entities | no tags | |
| memory_set_permissions | no tags | |
| memory_pin | no tags | |
| memory_archive | no tags | |
| memory_onboard | no tags | |
| memory_interview | no tags | |
| memory_import | no tags | |
| memory_migrate | untrusted-inputexternal-sink | untrusted-input: keyword "download", handler fetches a URL taken from its input (fetch(params.cloud_api_url) at dist/cli.js:5388; external-sink: handler sends an HTTP POST (fetch(params.cloud_api_url) at dist/cli.js:5389 |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest4af9a4914df7f3ea
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.1. Pin a release below and the command asks for exactly that one.
0.5.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Engrams can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.