Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theprodsde/agent-memory

PYPI · AGENT-MEMORY-SDK

Persistent agent memory with a decision layer: replay, restore, verify, or none — explainable.

Available components

0 this week 71 Trust /100

Last scanned (20 hours ago)

Scores higher than 64% of PyPI servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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 build step with no custom scripting around it. View diagnostics → Pass
  • 12 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management97
  • Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1
    • Provenance: unverified → fail ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 20 Nov 26 −1
    • Provenance: fail → unverified ▼ security
    • Stability: pass → 0.93 functional
  • 17 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 16 Nov 26 0
    • Provenance: unverified → fail ▼ security
  • 15 Nov 26 0
    • Provenance: fail → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Nov 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
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool 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 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H 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 98 packages
Packages resolved 98
Stale 10
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~317 tokens

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 →

Tool Tokens
archive_memory ~26

Archive a memory so it is excluded from retrieval.

NameTypeReqDescription
memory_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

consolidate_memories ~18

Merge near-duplicate memories into summary entries.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

forget_memory ~22

Delete a memory by ID.

NameTypeReqDescription
memory_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_memory_by_id ~25

Fetch a single memory by ID.

NameTypeReqDescription
memory_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_memories ~47

List stored memories with pagination and optional scope filter.

NameTypeReqDescription
include_archivedboolean––
limitinteger––
offsetinteger––
scope–––
NameTypeReqDescription
resultstringyes–

No examples provided.

remember_memory ~103

Store a query/response pair in persistent agent memory. ttl accepts formats like "30d", "24h", "60m", "3600s".

NameTypeReqDescription
confidencenumber––
memory_typestring––
metadata_jsonstring––
querystringyes–
requires_verificationboolean––
responsestringyes–
scopestring––
tags–––
ttl–––
NameTypeReqDescription
resultstringyes–

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

NameTypeReqDescription
enable_verifyboolean––
modestring––
querystringyes–
scope–––
top_kinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add theprodsde-agent-memory -- uvx agent-memory-sdk
Common questions

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 71 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 21 November 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 21 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 io.github.theprodsde/agent-memory MCP server under?

io.github.theprodsde/agent-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.

What did VerifyMCP test on the io.github.theprodsde/agent-memory MCP server?

VerifyMCP ran 16 checks on io.github.theprodsde/agent-memory, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.