memory-as-history
PulseGate's liveness check found it on 24 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 24 Sep 2026. How this is checked
memory-as-history is an open-source, SQLite-backed MCP server for managing AI agent memory as traceable claims and scoped narratives. It supports evidence, revisions, accountable forgetting, and history-aware context engineering for developers building agent systems.
Inferred · not functionally tested
Overview
6 featuresPurpose: Maintaining traceable, revisable, and scoped long-term memory for AI agents.
Inferred · not functionally tested
Audience: AI agent developers
Inferred · not functionally tested
Functions: agents
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: pypi.org · github.com. These links do not verify the individual claims.
In the Memory & skills space, memory-as-history takes a focused approach. Inferred · not functionally tested: It focuses on maintaining traceable, revisable, and scoped long-term memory for AI agents. Inferred · not functionally tested: memory-as-history is an open-source project aimed at AI agent developers. Basis unknown · not verified: memory-as-history is open source under the MIT license. Basis unknown · not verified: memory-as-history is available on the command line and API, and it can be self-hosted.
Behind memory-as-history is BrunoBanana, and it first shipped in 2026. Development happens publicly on GitHub with 80 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include traceable claims, evidence tracking, and claim revisions. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Traceable claims
- Evidence tracking
- Claim revisions
- Scoped narratives
- Accountable forgetting
- SQLite storage
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed24 Sep · 09:24 UTCmemory-as-history seen via PyPI Bulk EnumeratorSource: PyPI Bulk Enumerator · Open
Frequently asked questions about memory-as-history
- What is memory-as-history?
- Inferred · not functionally tested: Memory-as-history focuses on maintaining traceable, revisable, and scoped long-term memory for AI agents. It is catalogued under Memory & skills on PulseGate.
- Who should use memory-as-history?
- Inferred · not functionally tested: memory-as-history is an open-source project built for AI agent developers.
- Does memory-as-history have a free plan?
- Basis unknown · not verified: Yes — memory-as-history is open source under the MIT license and free to use.
- What platforms does memory-as-history run on?
- Basis unknown · not verified: memory-as-history runs on the command line and API. It can also be self-hosted.
- Is memory-as-history still active?
- PulseGate's liveness check found it on 24 Sep 2026. Its GitHub repository shows 80 commits in the last 90 days.
- What projects are similar to memory-as-history?
- Similar projects tracked by PulseGate include memorytrace, Agent Memory MCP, and agentmemory.memorytraceAgent Memory MCPagentmemory
- Who develops memory-as-history?
- memory-as-history is developed by BrunoBanana.
- How long has memory-as-history been around?
- memory-as-history first shipped in 2026.
Similar projects
Closest matches by what these projects do