LLMSlim memory
PYPI · LLMSLIM
Long-term memory and context fitting for agents, with no LLM in the loop. Local SQLite.
Available components
Last scanned (10 hours ago)
Scores higher than 77% 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 13 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Thanatos9404/llmslim). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 542 tokens (~108/item across 5 items; 5 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 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 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
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.
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.
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 63
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 18 Oct 2026 · Analysed pypi/llmslim@0.11.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Thanatos9404/llmslim |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Thanatos9404/llmslim/.github/workflows/release.yml@refs/tags/v0.11.1 |
| Rekor log index | 3297471182 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:59ffe9a6802be5261446625decfa6cdb36a09b8a1f3d26da3d31a1b398fd9d1f |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 13 packages
| Packages resolved | 13 |
|---|---|
| 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 →
fit_context ~101
Shrink a long text (a document, log or tool output) to a token budget, keeping the parts that answer the query, in their original order. Text that already fits comes back unchanged. Args: text: The text to shrink. budget: Most tokens to return. query: Optional question; the parts that answer it are kept first.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | – |
| query | – | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
forget ~52
Delete one stored message by its id (from `remember` or `list_memories`). This cannot be undone. Args: memory_id: The id of the message to delete.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_memories ~61
List the most recently stored messages with their ids, newest first. Args: limit: How many to list, at most 100. session: Optional conversation id to list only that conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| session | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
recall ~97
Find what earlier conversations said about a question: the stored messages that answer it, whole and under their dates, within a token budget. Args: query: The question, e.g. the user's latest message. budget: Most tokens to return. Defaults to the server's budget. session: Optional conversation id to search only that conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | – |
| query | string | yes | – |
| session | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remember ~92
Store a message in long-term memory, word for word. Args: text: The message to keep, in the speaker's own words. role: Who said it: "user" (default) or "assistant". session: Optional id of the conversation it belongs to. Messages without one are grouped by day.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | – |
| session | – | – | – |
| text | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the LLMSlim memory MCP server?
LLMSlim memory runs locally as a PyPI package, launched with uvx llmslim. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · llmslim
claude mcp add thanatos9404-llmslim -- uvx llmslim
What is the LLMSlim memory MCP server?
LLMSlim memory is an MCP server listed in the public MCP registry as io.github.Thanatos9404/llmslim. Long-term memory and context fitting for agents, with no LLM in the loop. Local SQLite. This page covers its PyPI package (llmslim).
Is the LLMSlim memory MCP server safe to use?
LLMSlim memory scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. Its build provenance is signed and verified. 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 LLMSlim memory MCP server expose?
LLMSlim memory exposes 5 tools: remember, recall, list_memories, forget, fit_context. Their descriptions and schemas cost roughly 403 tokens of context every time the server is loaded.
Is the LLMSlim memory MCP server still maintained?
LLMSlim memory is still listed as active in the MCP registry. We last reached this channel on 18 October 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 LLMSlim memory MCP server under?
LLMSlim 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.