io.github.turbyho/mem-context
PYPI · MEM-CONTEXT · SCANNED SEP 23
Temporal memory MCP server with LanceDB vector search, weight-decay scoring, and LLM consolidation
Available components
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 Security36
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 93 of 152 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 93 of 152 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 99 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the io.github.turbyho/mem-context MCP server?
io.github.turbyho/mem-context runs locally as a PyPI package, launched with uvx mem-context. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mem-context
claude mcp add turbyho-mem-context -- uvx mem-context
{
"mcpServers": {
"turbyho-mem-context": {
"command": "uvx",
"args": [
"mem-context"
]
}
}
} {
"servers": {
"turbyho-mem-context": {
"command": "uvx",
"args": [
"mem-context"
]
}
}
} codex mcp add turbyho-mem-context -- uvx mem-context
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"turbyho-mem-context": {
"type": "local",
"command": [
"uvx",
"mem-context"
],
"enabled": true
}
}
} openclaw mcp add turbyho-mem-context --command uvx --arg mem-context
mcp_servers:
turbyho-mem-context:
command: "uvx"
args: ["mem-context"] {
"McpServers": {
"turbyho-mem-context": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mem-context"
]
}
}
} assistant mcp add turbyho-mem-context -t stdio -c uvx -a mem-context
{
"mcpServers": {
"turbyho-mem-context": {
"command": "uvx",
"args": [
"mem-context"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 35 to 36.
- 13 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 10 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 6 Aug 26 0
- Malware scan: pass → unverified ▼ security
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 23 Sept 2026 · Analysed pypi/mem-context@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 7 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the io.github.turbyho/mem-context MCP server?
io.github.turbyho/mem-context is an MCP server listed in the public MCP registry as io.github.turbyho/mem-context. Temporal memory MCP server with LanceDB vector search, weight-decay scoring, and LLM consolidation. This page covers its PyPI package (mem-context).
Is the io.github.turbyho/mem-context MCP server safe to use?
io.github.turbyho/mem-context scores 15 out of 100 on VerifyMCP. 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.
Is the io.github.turbyho/mem-context MCP server still maintained?
io.github.turbyho/mem-context is still listed as active in the MCP registry. We last reached this channel on 23 September 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 io.github.turbyho/mem-context MCP server under?
io.github.turbyho/mem-context declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.