io.github.theprodsde/agent-memory
PYPI · AGENT-MEMORY-SDK · SCANNED SEP 23
Persistent agent memory with a decision layer: replay, restore, verify, or none — explainable.
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 Security74
- No malware found by supply-chain analysis.Pass
- A critical CVE affects chromadb, and no fixed version has been published yet. View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 10 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 317 tokens (~45/item across 7 items; 7 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 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; "forget_memory" implies "delete" 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 7 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.
How do I install the io.github.theprodsde/agent-memory MCP server?
io.github.theprodsde/agent-memory runs locally as a PyPI package, launched with uvx agent-memory-sdk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · agent-memory-sdk
claude mcp add theprodsde-agent-memory -- uvx agent-memory-sdk
{
"mcpServers": {
"theprodsde-agent-memory": {
"command": "uvx",
"args": [
"agent-memory-sdk"
]
}
}
} {
"servers": {
"theprodsde-agent-memory": {
"command": "uvx",
"args": [
"agent-memory-sdk"
]
}
}
} codex mcp add theprodsde-agent-memory -- uvx agent-memory-sdk
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theprodsde-agent-memory": {
"type": "local",
"command": [
"uvx",
"agent-memory-sdk"
],
"enabled": true
}
}
} openclaw mcp add theprodsde-agent-memory --command uvx --arg agent-memory-sdk
mcp_servers:
theprodsde-agent-memory:
command: "uvx"
args: ["agent-memory-sdk"] {
"McpServers": {
"theprodsde-agent-memory": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"agent-memory-sdk"
]
}
}
} assistant mcp add theprodsde-agent-memory -t stdio -c uvx -a agent-memory-sdk
{
"mcpServers": {
"theprodsde-agent-memory": {
"command": "uvx",
"args": [
"agent-memory-sdk"
]
}
}
} 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.
- 22 Sept 26 54
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 23 Sept 2026 · Analysed pypi/agent-memory-sdk@0.1.5
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 →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2wm9-hf6c-p5cr | CVE-2026-45830 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| GHSA-36p7-vc44-83pf | CVE-2026-45833 | critical | no | |
| GHSA-f4j7-r4q5-qw2c | CVE-2026-45829 | critical | no | |
| GHSA-xph7-9rjv-w5fr | CVE-2026-45831 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| PYSEC-2026-311 | CVE-2026-45829 | none | no | |
| PYSEC-2026-3813 | CVE-2026-45830 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| PYSEC-2026-3814 | CVE-2026-45833 | none | no | |
| PYSEC-2026-3815 | CVE-2026-45831 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 9 |
| 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 →
archive_memory ~26
Archive a memory so it is excluded from retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
consolidate_memories ~18
Merge near-duplicate memories into summary entries.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
forget_memory ~22
Delete a memory by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_memory_by_id ~25
Fetch a single memory by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_memories ~47
List stored memories with pagination and optional scope filter.
| Name | Type | Req | Description |
|---|---|---|---|
| include_archived | boolean | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| scope | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remember_memory ~103
Store a query/response pair in persistent agent memory. ttl accepts formats like "30d", "24h", "60m", "3600s".
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | number | – | – |
| memory_type | string | – | – |
| metadata_json | string | – | – |
| query | string | yes | – |
| requires_verification | boolean | – | – |
| response | string | yes | – |
| scope | string | – | – |
| tags | – | – | – |
| ttl | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_memory ~76
Retrieve memory and decide how the agent should respond. Actions: replay, restore, verify, none Modes: auto (default), replay, restore, verify
| Name | Type | Req | Description |
|---|---|---|---|
| enable_verify | boolean | – | – |
| mode | string | – | – |
| query | string | yes | – |
| scope | – | – | – |
| top_k | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.theprodsde/agent-memory MCP server?
io.github.theprodsde/agent-memory is an MCP server listed in the public MCP registry as io.github.theprodsde/agent-memory. Persistent agent memory with a decision layer: replay, restore, verify, or none, explainable. This page covers its PyPI package (agent-memory-sdk).
Is the io.github.theprodsde/agent-memory MCP server safe to use?
io.github.theprodsde/agent-memory scores 54 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 23 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.
What tools does the io.github.theprodsde/agent-memory MCP server expose?
io.github.theprodsde/agent-memory exposes 7 tools: remember_memory, resolve_memory, list_memories, get_memory_by_id, forget_memory, and 2 more. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.
Is the io.github.theprodsde/agent-memory MCP server still maintained?
io.github.theprodsde/agent-memory 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.