frugal-memory
PYPI · FRUGAL-MEMORY
Memory for AI assistants in one SQLite file: full-text search, no vectors, no embeddings.
Available components
Last scanned (1 hour ago)
Scores higher than 60% of PyPI 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 Security94
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
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 Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1910 tokens (~238/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.1.4 and 0.3.1: 6 tool removals, 0 breaking changes, 6 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 0
- Schema quality: good → excellent functional
- Package version: 0.3.0 → 0.3.1 functional
- 28 Oct 26 −3
- Stability: 0.27 → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 287 → 222 ▲ functional
- Package version: 0.2.3 → 0.3.0 functional
- 27 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.2.0 → 0.2.3 functional
- Package version: 0.2.0 → 0.2.2 functional
- Package version: 0.2.0 → 0.2.1 functional
- 26 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.5 → 0.2.0 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 22 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Install scripts: pass → partial ▼ security
- The code this package runs automatically changed: its declared build backend → build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module) security
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.1.4 → 0.1.5 functional
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 pypi/frugal-memory@0.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 2 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
| build_hook | unreviewed | tool.setuptools.dynamic attr |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
check ~220
Has a small language model judge how the named entries relate. Use it on a group from consolidate, or on two entries that seem to disagree, to ask whether a CONTRADICTION is behind it, PROGRESS (a newer state), or nothing (INDEPENDENT). Not authoritative: measured 67 % correct on 70 German pairs, so the result says where to look, not what is true. Returns one line per pair. Each pair is asked in both directions; only what comes back the same both times is reported, otherwise "disputed". At most 5 pairs per call, roughly 10 seconds each. Opt-in: needs MEMORY_FC_URL and MEMORY_FC_MODEL (any OpenAI-compatible endpoint; MEMORY_FC_KEY if it wants a key). Without them this tool does nothing and says so. When set up, up to 200 characters of each note are sent there. Args: ids: Two or more entry ids, e.g. "249,255".
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
classify ~167
Sets the kind of knowledge for existing entries. Use it in passing on entries recall shows as "unsorted"; the backlog need not be sorted in one sitting. Writes only the kind - text, tags, ids and superseded status stay as they are - and is undone by classifying again. Returns the ids changed, names unknown ids, and how many live entries are still unsorted. Args: ids: One or more entry ids, e.g. "376,481"; a range "376-380" means every id in between. kind: Exactly one of: interface, pitfall, decision, measurement, workflow, history. "unsorted" undoes the classification.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | yes | – |
| kind | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
consolidate ~261
Finds groups of entries that say largely the same thing. Use it for tidying up. Read-only, changes nothing: merging is a judgment call - replace a group by one new entry via remember(..., supersedes="..."). Compares shared word stems weighted by rarity, not meaning; identical copies are always found. A few seconds for thousands of entries. Returns how many entries and pairs were compared, then the groups, largest first, each with its best similarity and its entries (id, kind, date, title) - or that nothing reached the threshold. Args: tag: Only consider entries from this project (empty = all). Sub-tags are included, as in recall. kind: Only consider entries of this kind/these kinds, comma-separated. Default "all"; "history" alone is the most rewarding case. threshold: Share of the weighted stems two entries must have in common, 0 to 1. Default 0.5; 0.8 shows only near-copies. groups: Maximum number of groups reported (default 5).
| Name | Type | Req | Description |
|---|---|---|---|
| groups | integer | – | – |
| kind | string | – | – |
| tag | string | – | – |
| threshold | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
forget ~136
Hides entries that are wrong or obsolete and have no replacement. If a newer entry replaces them, use remember(..., supersedes=...) instead. Nothing is deleted: show and recall(..., include_superseded=True) still find them, undo=True brings them back. Returns the ids changed and names unknown ones. Args: ids: One or more entry ids, e.g. "12,34". reason: Why - shown later next to the superseded entry. undo: True brings superseded entries back.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | string | yes | – |
| reason | string | – | – |
| undo | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
recall ~367
Searches memory by words, best matches first. Use it first, before searching files or the web for something noted before. It matches words, not meaning: inflected forms count ("configured" -> "configuring"), synonyms don't - if nothing fits, retry in the other language your notes may use. No search terms? Browse with topics. Returns a preview per hit (id, kind, date, title line). Read the ones you need with show("376,481"), or set full=True for a narrow question. Args: query: Search term(s), FTS5 syntax allowed (e.g. "sqlite AND fts5", "proj*"). limit: Maximum number of hits (default 8). kind: Restrict to kinds of knowledge, e.g. "pitfall,decision". Possible: interface, pitfall, decision, measurement, workflow, history, unsorted, all. Default: everything except history - otherwise the chronicle drowns out every search for a detail. tag: Restrict to a project, e.g. "spaceship". Several tags separated by comma or space are OR-combined. Sub-tags are included: "lighthouse" also matches "lighthouse-project", but "mcp-memory-server" does not match "mcp-memory". topics() lists which tags exist. full: Full text instead of preview (default: no), capped like show. include_superseded: Also show superseded entries (default: no).
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| include_superseded | boolean | – | – |
| kind | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| tag | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remember ~274
Stores one fact permanently in memory. Use it for knowledge a later session needs: a decision with its reason, a pitfall, a measured number, an interface. Not for secrets, guesses or short-lived details. Search with recall first; if an entry covers the fact, supersede that one. Returns the new id, existing entries that resemble it (candidates to supersede) and a note when the tag is new - often a misspelling. Args: text: The fact. A text that belongs to two kinds is two entries. tags: The project, i.e. WHERE the knowledge belongs (spaces or commas between several). kind: WHICH KIND of knowledge: interface (signature, file name, command, data format), pitfall (the obvious approach is wrong because ...), decision (with rationale), measurement (a number plus its criterion), workflow (how to work with this user), history (chronicle, hidden from recall's default view). Empty = unsorted. supersedes: Ids this entry replaces, e.g. "12,34". Hidden, not deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| supersedes | string | – | – |
| tags | string | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
show ~150
Returns the named entries in full text. Use it after recall or topics, once you know which entries you need - it takes ids, not search terms. Superseded entries are included: whoever asks for the id means that one. Returns about 6000 characters per call, in the order asked. Whatever doesn't fit comes back as a title line plus the call that fetches it; unknown ids are named as such. Args: ids: One or more entry ids, e.g. "376,481". Most wanted first. full: Everything asked for at once, without the cap (default: no).
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | – |
| ids | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
topics ~203
Browses memory: the board of all tags, or the title index of one project. Use it when search terms are missing - a project picked up after months, or "what happened here lately". To find a specific fact, recall is faster. Returns the tag board (entries per tag and kind) or, with a tag, that project's title lines, newest first, one page at a time. Follow up with show("...") or recall(query, tag="..."). Args: tag: Project, e.g. "spaceship". Empty = tag board. limit: Rows per page (default 40 for the board, 30 for the title index). page: Page of the title index (default 1 = the newest). all: Whole title index at once, grouped by kind.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | – |
| limit | integer | – | – |
| page | integer | – | – |
| tag | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the frugal-memory MCP server?
frugal-memory runs locally as a PyPI package, launched with uvx frugal-memory. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · frugal-memory
claude mcp add komakeule57-maker-frugal-memory -- uvx frugal-memory
What is the frugal-memory MCP server?
frugal-memory is an MCP server listed in the public MCP registry as io.github.komakeule57-maker/frugal-memory. Memory for AI assistants in one SQLite file: full-text search, no vectors, no embeddings. This page covers its PyPI package (frugal-memory).
Is the frugal-memory MCP server safe to use?
frugal-memory scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 frugal-memory MCP server expose?
frugal-memory exposes 8 tools: remember, recall, show, topics, consolidate, and 3 more. Their descriptions and schemas cost roughly 1,778 tokens of context every time the server is loaded.
Is the frugal-memory MCP server still maintained?
frugal-memory 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 frugal-memory MCP server under?
frugal-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.