Turbo Quant Memory
PYPI · TURBO-QUANT-MEMORY
Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.
Available components
Last scanned (21 hours ago)
Scores higher than 62% of PyPI servers
Category Memory and Knowledge
Recent critical change
CVE-2026-112398 affects this package (24 Oct 2026). See the changelog before you install this server.
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 Security32
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects cryptography 46.0.7, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 96 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Lexus2016/turbo_quant_memory). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 2276 tokens (~94/item across 24 items; 24 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage52
- 67% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "unlink_entities" implies "unlink" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 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 4 Nov 2026 · Analysed pypi/turbo-quant-memory@0.34.0
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 | Lexus2016/turbo_quant_memory |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Lexus2016/turbo_quant_memory/.github/workflows/publish.yml@refs/tags/v0.34.0 |
| Rekor log index | 3360785856 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:1d00cb8d179798355ae4d35243107596a88ae0d65fb70bc2db5d743184962cef |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 7 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-537c-gmf6-5ccf | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-g6cj-pr64-35w5 | CVE-2026-69247 | high | yes | |
| GHSA-jwv3-5hgf-82ww | CVE-2026-69249 | high | yes | |
| GHSA-m2h6-j472-rp4c | CVE-2026-69248 | medium | yes | |
| PYSEC-2026-3552 | CVE-2026-69247 | none | yes | |
| PYSEC-2026-3553 | CVE-2026-69249 | none | yes | |
| PYSEC-2026-3554 | CVE-2026-69248 | none | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 14 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
announce_work ~85
Tell the other agents in this working tree what you are changing. feature: short name of the work. areas: workspace-relative files or directories (globs allowed). Returns the peers whose announced areas overlap yours and recent changes inside them. Inferred writers are guesses from announced areas, never facts.
| Name | Type | Req | Description |
|---|---|---|---|
| areas | – | – | – |
| details | – | – | – |
| feature | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_secret ~23
Delete a project secret by exact name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
deprecate_note ~40
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | string | yes | – |
| reason | – | – | – |
| replacement_note_id | – | – | – |
| replacement_scope | – | – | – |
| scope | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
file_history ~70
Journaled versions of one file in this working tree, newest first. Versions are snapshots taken while several sessions share the tree. Use restore_file with a version id to bring one back; the overwritten content is kept as a new version.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| path | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
finish_work ~18
Clear the work this session announced with announce_work.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_related_entities ~92
Query relations involving a specific entity URI. uri: the entity to look up, as note://<note_id>, file://<relative/path>, issue://KEY, task://KEY, or https://... — the same URI forms link_entities accepts. Returns nothing for an entity that has no links yet.
| Name | Type | Req | Description |
|---|---|---|---|
| relation_type | – | – | – |
| scope | string | – | – |
| uri | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_secret ~84
Fetch a project secret by exact name. Returns the value in a dedicated ``secret_value`` field (never in descriptive text). Status is ``"ok"`` on hit, ``"missing"`` when no such name exists, or ``"error"`` with ``setup_hint`` when no master key is configured yet.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
health ~4
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
hydrate ~26
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
| mode | string | – | – |
| scope | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
index_paths ~130
Register and index Markdown directories into project memory. Supports .tqmemoryignore files (placed in project root or any indexed directory) with glob patterns to exclude paths from indexing. One pattern per line, # for comments. Example patterns: ``workspace-*`` skips any directory matching the glob; ``data/reports/*.md`` skips files matching a path pattern; ``backups/`` (trailing slash, as in .gitignore) skips a directory. Agent worktrees under ``.claude/worktrees`` are skipped by default.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| paths | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
link_entities ~100
Create a Knowledge Graph link between two entities. Entities are specified using URIs: - Note: note://<note_id> - File: file://<relative_path> (relative to project root) - External: e.g. issue://BUG-404, task://TASK-101
| Name | Type | Req | Description |
|---|---|---|---|
| relation_type | string | yes | – |
| scope | string | – | – |
| source_uri | string | yes | – |
| target_uri | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
lint_knowledge_base ~21
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| max_issues | integer | – | – |
| paths | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_scopes ~6
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_secrets ~21
List secret names in the active project. Never returns values.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
promote_note ~13
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
recent_context ~274
Query-free session bootstrap: the most recently updated notes. Call this FIRST when starting a new session or resuming after a context compaction, when you do not yet know what to search for. Returns notes ordered by recency (newest first), NOT by relevance — including `handoff` notes (episodic tier), which a plain semantic_search hides by default. This is the reliable "where did I leave off" entry point. scope: 'project' (default), 'global', or 'hybrid'. Use 'hybrid' to also surface promoted cross-project knowledge. tier_filter: defaults to all tiers (so handoffs are included). Pass e.g. ["durable"] to exclude episodic session notes. format: 'json' (default); 'text' — compact plain text, one line per note with its hydrate handle (about 20% of the JSON size); 'hook' — the same text as Claude Code SessionStart hook output. Use 'hook' from a SessionStart mcp_tool hook: Claude Code shows the model only an mcp_tool hook's JSON additionalContext, never its plain text.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | – |
| limit | integer | – | – |
| scope | string | – | – |
| tier_filter | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
remember_note ~363
Store a typed project note. kind must be exactly one of: lesson, decision, pattern, handoff. tags: 2-3 lowercase tags are strongly recommended — tags are the only way to FILTER notes; an untagged note is reachable by semantic_search alone. source_refs: the files / notes / issues this note is about. Pass them as entity URIs (note://<id>, file://<relative/path>, issue://KEY, https://...) and they are auto-linked into the knowledge graph as `references` relations, so get_related_entities can later surface them. provenance: who originated the note. Use "human-explicit" when the USER asked to remember something ("remember this", "save that"); "agent" for your own observations (the default); "external-tool" for API/tool data; "system" for automatic processes. tier: normally derived from `kind` (handoff -> episodic, every other kind -> durable). Override e.g. tier="durable" to keep a `handoff` in the default-searchable set, or tier="episodic" to keep a noisy lesson out of regular search. After storing, connect the note with link_entities(source_uri="note://<id>", ...) when it relates to a file, issue, or prior note — the response echoes the note's uri and hints this when the note still has no relations.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| kind | string | yes | – |
| provenance | string | – | – |
| scope | string | – | – |
| source_refs | – | – | – |
| tags | – | – | – |
| tier | – | – | – |
| title | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
restore_file ~72
Write a journaled version of one file back into the working tree. version: a version id from file_history, or "HEAD" for the committed content. The content being overwritten is kept as a new version, so the restore can be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
| version | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
self_test ~5
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
semantic_search ~239
Compact memory retrieval (dense vector + BM25, fused via RRF). By default only the `durable` and `reference` tiers are searched, so session `handoff` notes (which live in the `episodic` tier) are NOT returned. To recover handoffs / session summaries pass ``tier_filter=["episodic"]`` (or list every tier to opt everything in). For a query-free "where did I leave off" bootstrap at session start, prefer the `recent_context` tool instead. source_filter narrows results by source type: ``"notes"`` returns only memory notes (decisions/lessons/patterns/handoffs), ``"markdown"`` only indexed doc blocks. In doc-heavy projects the reference blocks often crowd notes out of the top ranks on question-shaped queries — when you are asking "what did we decide/learn about X", pass ``source_filter="notes"``.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| scope | string | – | – |
| source_filter | – | – | – |
| tier_filter | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
server_info ~5
No description provided.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
set_secret ~122
Store an encrypted secret in the active project's vault. The value is encrypted with AES-256-GCM under a per-project master key resolved from TQMEMORY_SECRETS_PASSPHRASE or the OS keyring. Secrets are NEVER indexed, embedded, or returned via ``semantic_search`` / ``hydrate``. They live in ``~/.turbo-quant-memory/projects/<project_id>/secrets/vault.tqv`` and stay on this machine.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| value | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
unlink_entities ~79
Remove a Knowledge Graph link between two entities. source_uri / target_uri use the same URI forms as link_entities: note://<note_id>, file://<relative/path>, issue://KEY, https://...
| Name | Type | Req | Description |
|---|---|---|---|
| relation_type | – | – | – |
| scope | string | – | – |
| source_uri | string | yes | – |
| target_uri | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
workspace_status ~79
Overview of the sessions sharing this working tree: peers, overlaps and recent file changes. Call it at session start. Inferred writers are guesses from announced areas, never facts. Peers that made no tqmemory call for a long time are listed under `idle_sessions`, not in `sessions`, and their announced areas are left out of `overlaps`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Turbo Quant Memory MCP server?
Turbo Quant Memory runs locally as a PyPI package, launched with uvx turbo-quant-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 · turbo-quant-memory
claude mcp add lexus2016-turbo-quant-memory -- uvx turbo-quant-memory
What is the Turbo Quant Memory MCP server?
Turbo Quant Memory is an MCP server listed in the public MCP registry as io.github.Lexus2016/turbo-quant-memory. Local-first memory and knowledge graph for coding agents. Compact retrieval, no network. This page covers its PyPI package (turbo-quant-memory).
Is the Turbo Quant Memory MCP server safe to use?
Turbo Quant Memory scores 66 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 4 November 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 Turbo Quant Memory MCP server expose?
Turbo Quant Memory exposes 24 tools: health, server_info, list_scopes, self_test, remember_note, and 19 more. Their descriptions and schemas cost roughly 1,971 tokens of context every time the server is loaded.
Is the Turbo Quant Memory MCP server still maintained?
Turbo Quant Memory is still listed as active in the MCP registry. We last reached this channel on 4 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 Turbo Quant Memory MCP server under?
Turbo Quant 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.