"Understanding Memory or Memory-Related Topics" matching MCP servers:

Persistent encrypted memory for AI agents. E2E encrypted private vaults, shared knowledge commons, topic channels, and agent-to-agent DMs. 23 MCP tools, free, no API key needed.

Enables AI assistants to keep and retrieve private context locally, with verifiable receipts and optional Solana anchoring for public proofs.

A zero-dependency Node.js playground for debugging how MCP clients authenticate to an MCP server over HTTP.

Enables AI tools and agents to share a persistent memory space, so a decision, task, or encrypted secret saved in one client can be searched, recalled, and handed off from another. It also tracks goals day by day, moves unfinished work between sessions, and keeps exports, trash recovery, and per-account isolation under the user's control.

A tool for detecting and cleaning Java memory shells via local or SSH remote execution. It enables AI agents to scan Java processes, analyze suspicious class code, and safely remove memory shells after user confirmation.

Guardrails for AI coding agents that enforces rules via compliance receipts, blocking destructive actions and syncing rules across all AI tools.

Enables security analysts to carry structured investigation state across sessions by storing typed observations, hypotheses, tasks, evidence and versioned decisions in a local SQLite graph with full-text search. It also enforces authorized scope and request controls, redacted and content-hashed evidence, duplicate-test signatures and validation gates that leave findings in draft until reproducibly confirmed, then produces technical and executive reports for Antigravity, Codex and other stdio MCP clients.

Enables MCP-compatible AI agents to save encrypted, DID-signed session checkpoints and resume the latest state across sessions, while keeping secrets and credentials in a local vault.

AI-powered memory dump analysis using Volatility 3 for digital forensics investigations. Enables process analysis, malware detection, network forensics, timeline generation, and anomaly detection with support for Claude, Llama, and other LLMs.

Enables agents and MCP clients to retain, recall, screen, quarantine, approve, supersede, and verify durable memories with session-level provenance. Every write passes a poisoning gate, so suspicious or secret-bearing entries are held for human review rather than silently trusted in later sessions.

Lets multiple AI agents and parallel coding sessions share one memory and task ledger, so they can claim work instead of duplicating it, resume each other's handoffs and reasoning, and use credentials without ever seeing the keys. Connects assistants such as Claude Code, Codex, Cursor, Gemini, ChatGPT and custom agents over MCP, backed by a single local SQLite file or a self-hosted Postgres hub.

Enables AI agents to query and record SOC analyst reasoning via a knowledge graph, allowing access to institutional memory from Splunk.

Enables secure, human-approved AI memory from Gmail messages for Claude, with provenance, risk inspection, expiry, and revocation controls.

Enables secure remote control of Home Assistant and Life Dashboard/DSH via MCP, supporting entity state queries, whitelisted entity/scene control, lifecycle overview reading, DSH workspace summaries, and follow-up sending.

8 standalone MCP servers for SMBs — Guardrails (prompt injection, PII, secrets detection), FinOps (AI cost tracking and budgets), Observability (agent tracing), Smart Router (17+ models, 9 providers), Trust Score (governance scoring 0-100), Memory (persistent agent memory), ThinkSecure (runtime security + SOC2/GDPR audit), and A2A Lite (agent-to-agent protocol). 37 tools total, TNC credits

Non-custodial memory MCP server with client-side encryption, enabling secure remember, recall, forget, and share operations with post-quantum security.

Lets MCP-compatible AI apps read and update files inside Cryptomator vaults after the user unlocks them, keeping keys in memory and allowing changes to be undone.

Policy proxy that governs what AI assistants can reach and do: it refuses forbidden tool calls before the upstream is contacted, with per-user memory and a tamper-evident audit. Stops prompt-injection exfiltration and forbidden data combinations across connectors.

Cryptographic accountability for AI agents. Ed25519-signed receipts for every MCP tool call. Constraints, chains, AI judgment, invoicing, and local dashboard included.

A local memory layer for AI coding tools that stores user preferences, lessons, and project context as local files, exposed via MCP so different AI tools can share the same understanding of you.