Memory for AI
PYPI · MEMORY-FOR-AI · 8 COMPONENTS · SCANNED SEP 21
Local codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
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 hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, 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 Memory for AI MCP server?
Memory for AI runs locally as a PyPI package, launched with uvx memory-for-ai. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · memory-for-ai
claude mcp add lonelytraderbay-memory-for-ai -- uvx memory-for-ai
{
"mcpServers": {
"lonelytraderbay-memory-for-ai": {
"command": "uvx",
"args": [
"memory-for-ai"
]
}
}
} {
"servers": {
"lonelytraderbay-memory-for-ai": {
"command": "uvx",
"args": [
"memory-for-ai"
]
}
}
} codex mcp add lonelytraderbay-memory-for-ai -- uvx memory-for-ai
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"lonelytraderbay-memory-for-ai": {
"type": "local",
"command": [
"uvx",
"memory-for-ai"
],
"enabled": true
}
}
} openclaw mcp add lonelytraderbay-memory-for-ai --command uvx --arg memory-for-ai
mcp_servers:
lonelytraderbay-memory-for-ai:
command: "uvx"
args: ["memory-for-ai"] {
"McpServers": {
"lonelytraderbay-memory-for-ai": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"memory-for-ai"
]
}
}
} assistant mcp add lonelytraderbay-memory-for-ai -t stdio -c uvx -a memory-for-ai
{
"mcpServers": {
"lonelytraderbay-memory-for-ai": {
"command": "uvx",
"args": [
"memory-for-ai"
]
}
}
} 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.
- 19 Sept 26 0
- Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
- Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
- Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
- Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
- Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
- 18 Sept 26 0
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 0.10.9 → 0.11.0 functional
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 25
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 20 Sept 2026 · Analysed pypi/memory-for-ai@0.11.0
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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
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 Memory for AI MCP server?
Memory for AI is an MCP server listed in the public MCP registry as io.github.LonelyTraderBay/memory-for-ai. Local codebase knowledge graph for AI agents, 162 languages, sub-ms queries, 99% fewer tokens. This page covers its PyPI package (memory-for-ai).
Is the Memory for AI MCP server safe to use?
Memory for AI scores 40 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.
Is the Memory for AI MCP server still maintained?
Memory for AI is still listed as active in the MCP registry. We last reached this channel on 20 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 Memory for AI MCP server under?
Memory for AI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.