# Perseus Ledger — verifiable, hash-chained event provenance (pypi · perseus-ledger)

Verifiable, hash-chained event provenance for autonomous systems. Local-first, MIT. 5 MCP tools.

- Trust score: 74/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-26

## Components

- oci · `ghcr.io/perseus-computing-llc/ledger:1.2.4`: 9/100, [markdown](https://verifymcp.io/servers/perseus-computing-llc-ledger/ghcr-io-perseus-computing-llc-ledger-1-2-4.md), [page](https://verifymcp.io/servers/perseus-computing-llc-ledger/ghcr-io-perseus-computing-llc-ledger-1-2-4)
- pypi · `perseus-ledger`: 74/100 (this document), [markdown](https://verifymcp.io/servers/perseus-computing-llc-ledger/perseus-ledger.md), [page](https://verifymcp.io/servers/perseus-computing-llc-ledger/perseus-ledger)

## Channel facts

- Registry: `pypi`
- Package: `perseus-ledger`
- Version: `1.2.4`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-26.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 1 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 644 tokens (~128/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 79/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 36% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Perseus Ledger — verifiable, hash-chained event provenance MCP server?

Perseus Ledger — verifiable, hash-chained event provenance runs locally as a PyPI package, launched with uvx perseus-ledger. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add perseus-computing-llc-ledger -- uvx perseus-ledger
```

### Cursor

```json
{
  "mcpServers": {
    "perseus-computing-llc-ledger": {
      "command": "uvx",
      "args": [
        "perseus-ledger"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "perseus-computing-llc-ledger": {
      "command": "uvx",
      "args": [
        "perseus-ledger"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add perseus-computing-llc-ledger -- uvx perseus-ledger
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "perseus-computing-llc-ledger": {
      "type": "local",
      "command": [
        "uvx",
        "perseus-ledger"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add perseus-computing-llc-ledger --command uvx --arg perseus-ledger
```

### Hermes

```yaml
mcp_servers:
  perseus-computing-llc-ledger:
    command: "uvx"
    args: ["perseus-ledger"]
```

### Netclaw

```json
{
  "McpServers": {
    "perseus-computing-llc-ledger": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "perseus-ledger"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add perseus-computing-llc-ledger -t stdio -c uvx -a perseus-ledger
```

### Other

```json
{
  "mcpServers": {
    "perseus-computing-llc-ledger": {
      "command": "uvx",
      "args": [
        "perseus-ledger"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-26 (score 74, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-24 (score 72, +1)

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

### 2026-08-22 (score 71, +1)

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

### 2026-08-21 (score 70, +1)

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

### 2026-08-18 (score 69, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-12 (score 65, +15)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-08-11 (score 50, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 45)

First indexed and scored.

## MCP tools (5)

### `ledger_health` (~28 tokens)

Report the Ledger org, balance, workspace month-to-date spend, and provider health. Read-only.

### `ledger_record` (~378 tokens)

Meter one AI call: record provider/model/tokens/cost plus optional task, workspace, external ref, and action provenance into the hash-chained evidence ledger. Scoped write. Action-provenance fields (agent_id, authority_manifest_ref, scope_anchor, action_intent_hash, action_status, approval_ref) are all-or-nothing: supply all of them or none.

Input parameters:

- `action_intent_hash` (string)
- `action_receipt_hash` (string)
- `action_status` (string)
- `agent_id` (string): Agent identity; required with the action-provenance set.
- `approval_ref` (string)
- `authority_manifest_ref` (string)
- `cache_read_tokens` (integer)
- `context_render_hash` (string)
- `context_render_schema` (string): Required with any context-render evidence: context_render_hash, served_memory_provenance_hash, action_receipt_hash.
- `cost_usd` (number): Exact cost in USD if known; estimated from pricing otherwise.
- `evidence_hashes` (array): Hash-only evidence references (sha256 hex); hash-covered into the event.
- `external_ref` (string)
- `input_tokens` (integer)
- `model` (string)
- `output_tokens` (integer)
- `policy_version` (string)
- `provider` (string, required): Provider name (required), e.g. anthropic, openai, bedrock.
- `reasoning_tokens` (integer)
- `result_hash` (string): Hash of the action result — never the result itself.
- `scope_anchor` (string)
- `served_memory_provenance_hash` (string): Served-claim digest from a memory recall.
- `task_type` (string)
- `user_id` (string)
- `workspace` (string)

### `ledger_query` (~76 tokens)

List recent usage events for the org, newest first. Pass `before` (the `_rowid` of the last event from the previous page) to paginate. Read-only.

Input parameters:

- `before` (integer): Cursor: rowid of the last event seen, for pagination.
- `limit` (integer): Max events (1-500).

### `ledger_verify` (~45 tokens)

Walk the usage_events tamper-evidence hash chain and report divergences per org. Read-only.

Input parameters:

- `org` (string): Org id or slug; all orgs if omitted.

### `ledger_receipt` (~117 tokens)

Build a hash-only served-claim evidence receipt binding a source reference to a ledger event, with optional authority/provenance/scope/state context. Contains no prompts, memory bodies, or secrets. Read-only.

Input parameters:

- `authority_ref` (string)
- `event_ref` (string, required): Ledger event hash or external reference.
- `provenance_class` (string)
- `scope_anchor` (string)
- `source_ref` (string, required): Reference to the source being served (e.g. vault entity id).
- `state` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/perseus-computing-llc-ledger/perseus-ledger#diagnostics

## Score history

- 2026-08-26: 74
- 2026-08-25: 72
- 2026-08-24: 72
- 2026-08-23: 71
- 2026-08-22: 71
- 2026-08-21: 70
- 2026-08-20: 69
- 2026-08-19: 69
- 2026-08-18: 69
- 2026-08-17: 65
- 2026-08-16: 65
- 2026-08-15: 65
- 2026-08-14: 65
- 2026-08-13: 65
- 2026-08-12: 65
- 2026-08-11: 50
- 2026-08-10: 45

## Common questions

### What is the Perseus Ledger — verifiable, hash-chained event provenance MCP server?

Perseus Ledger — verifiable, hash-chained event provenance is an MCP server listed in the public MCP registry as io.github.Perseus-Computing-LLC/ledger. Verifiable, hash-chained event provenance for autonomous systems. Local-first, MIT. 5 MCP tools. This page covers its PyPI package (perseus-ledger).

### Is the Perseus Ledger — verifiable, hash-chained event provenance MCP server safe to use?

Perseus Ledger — verifiable, hash-chained event provenance scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 August 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 Perseus Ledger — verifiable, hash-chained event provenance MCP server expose?

Perseus Ledger — verifiable, hash-chained event provenance exposes 5 tools: ledger_health, ledger_record, ledger_query, ledger_verify, ledger_receipt. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.

### Is the Perseus Ledger — verifiable, hash-chained event provenance MCP server still maintained?

Perseus Ledger — verifiable, hash-chained event provenance is still listed as active in the MCP registry. We last reached this channel on 26 August 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 Perseus Ledger — verifiable, hash-chained event provenance MCP server under?

Perseus Ledger — verifiable, hash-chained event provenance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/perseus-ledger/
- Socket report: https://socket.dev/pypi/package/perseus-ledger
- Repository: https://github.com/Perseus-Computing-LLC/ledger
- Changelog RSS feed: https://verifymcp.io/servers/perseus-computing-llc-ledger/perseus-ledger.xml
- Changelog JSON feed: https://verifymcp.io/servers/perseus-computing-llc-ledger/perseus-ledger.json
- HTML version of this page: https://verifymcp.io/servers/perseus-computing-llc-ledger/perseus-ledger