Acta — Verifiable Agent Memory

io.github.Kylewilson04Published by GitHub account Kylewilson04v1.0.0-rc.1Updated Oct 24, 2026

Verifiable agent memory with signed ledger receipts — verify every write offline.

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & Memory

Overview

AI-generated overview

Acta gives an AI assistant verifiable agent memory backed by a signed ledger, so every memory write can be checked offline.

What you can do
  • Store and recall agent memory through an Acta server, with each write recorded in a signed ledger.
  • Verify memory writes offline using the ledger receipts the server returns.
  • Point the assistant at a specific Acta server and tenant via configuration.
When to use it
Useful when an assistant needs persistent memory whose history can be audited or proven later, for example in agent workflows where tamper-evident records of what was stored matter.
Requirements
Runs as a local stdio process (desktop only, distributed as an mcpb bundle). Needs a reachable Acta server, set by ACTA_BASE (default and a tenant via ACTA_TENANT (default default). ACTA_API_KEY is needed only when server auth is enabled.
Before you install
Memory content is sent to the configured Acta server, so check where that server runs and who operates it. ACTA_API_KEY is a credential; keep it out of shared configuration. Writes to the ledger are persistent, so confirm what the assistant is allowed to store.

Installation

In SourceWeft

  1. Open Acta — Verifiable Agent Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0-rc.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations