
Perseus Ledger — verifiable, hash-chained event provenance
io.github.Perseus-Computing-LLCPublished by GitHub account Perseus-Computing-LLCv1.2.4Updated Oct 24, 2026
Verifiable, hash-chained event provenance for autonomous systems. Local-first, MIT. 5 MCP tools.
Overview
A local-first MCP server that gives an assistant verifiable, hash-chained event provenance for autonomous systems, exposed through five tools.
- What you can do
- Record events into a hash-chained ledger so activity can be traced and verified later, using the five MCP tools the server exposes. The registry description gives no tool names or per-tool details, so the exact operations are not documented here. It runs locally on the user's machine over stdio, either as a Python package or a Docker image.
- When to use it
- Worth considering when you want an assistant's or autonomous system's actions recorded in a tamper-evident, verifiable event log kept on your own machine. Less useful if you only need general-purpose tooling, since the description covers provenance logging only.
- Requirements
- Runs as a local process over stdio, on desktop only. Install the Python package perseus-ledger or run the Docker image ghcr.io/perseus-computing-llc/ledger:1.2.4. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Perseus Ledger — verifiable, hash-chained event provenance in the dashboard and add it to a workspace.
- 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
0Version history
1- v1.2.4LatestSep 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.