Perseus Ledger — verifiable, hash-chained event provenance
PYPI · PERSEUS-LEDGER · 2 COMPONENTS · SCANNED AUG 26
Verifiable, hash-chained event provenance for autonomous systems. Local-first, MIT. 5 MCP tools.
Available components
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. How we score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 36% of tool parameters carry a description.Partial
Tool Safety–
Not scored yet: our latest scan of this package recorded no findings here. That is usually because the category is newer than the scan, or because we have not captured the MCP schema this package serves yet. It fills in the next time we score it.
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
pypi · perseus-ledger
claude mcp add perseus-computing-llc-ledger -- uvx perseus-ledger
{
"mcpServers": {
"perseus-computing-llc-ledger": {
"command": "uvx",
"args": [
"perseus-ledger"
]
}
}
} {
"servers": {
"perseus-computing-llc-ledger": {
"command": "uvx",
"args": [
"perseus-ledger"
]
}
}
} codex mcp add perseus-computing-llc-ledger -- uvx perseus-ledger
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"perseus-computing-llc-ledger": {
"type": "local",
"command": [
"uvx",
"perseus-ledger"
],
"enabled": true
}
}
} openclaw mcp add perseus-computing-llc-ledger --command uvx --arg perseus-ledger
mcp_servers:
perseus-computing-llc-ledger:
command: "uvx"
args: ["perseus-ledger"] {
"McpServers": {
"perseus-computing-llc-ledger": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"perseus-ledger"
]
}
}
} assistant mcp add perseus-computing-llc-ledger -t stdio -c uvx -a perseus-ledger
{
"mcpServers": {
"perseus-computing-llc-ledger": {
"command": "uvx",
"args": [
"perseus-ledger"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Aug 26 +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.
- 22 Aug 26 +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.
- 21 Aug 26 +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.
- 18 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 12 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 45
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Aug 2026 · Analysed pypi/perseus-ledger@1.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
ledger_health ~28
Report the Ledger org, balance, workspace month-to-date spend, and provider health. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ledger_query ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | integer | – | Cursor: rowid of the last event seen, for pagination. |
| limit | integer | – | Max events (1-500). |
No output schema declared.
No examples provided.
ledger_receipt ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authority_ref | string | – | – |
| event_ref | string | yes | Ledger event hash or external reference. |
| provenance_class | string | – | – |
| scope_anchor | string | – | – |
| source_ref | string | yes | Reference to the source being served (e.g. vault entity id). |
| state | string | – | – |
No output schema declared.
No examples provided.
ledger_record ~378
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | – | – |
No output schema declared.
No examples provided.
ledger_verify ~45
Walk the usage_events tamper-evidence hash chain and report divergences per org. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| org | string | – | Org id or slug; all orgs if omitted. |
No output schema declared.
No examples provided.
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 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 25 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.