Ledger MCP server
{
"mcpServers": {
"arcaeon-ledger": {
"command": "uvx",
"args": [
"arcaeon-ledger"
]
}
}
}{
"mcpServers": {
"arcaeon-ledger": {
"command": "uvx",
"args": [
"arcaeon-ledger"
]
}
}
}{
"mcpServers": {
"arcaeon-ledger": {
"command": "uvx",
"args": [
"arcaeon-ledger"
]
}
}
}{
"servers": {
"arcaeon-ledger": {
"command": "uvx",
"args": [
"arcaeon-ledger"
]
}
}
}{
"mcpServers": {
"arcaeon-ledger": {
"command": "uvx",
"args": [
"arcaeon-ledger"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx arcaeon-ledgerversion 0.5.6
What it does
Ledger is an MCP server that exposes hash-chained action logging for agents. Every record is cryptographically linked to the previous one, so tampering—editing, deleting, or reordering rows—breaks the chain and can be detected. It is for developers building agents who need tamper-evident, portable audit records with zero dependencies.
- Log agent actions and verify the log has not been altered since creation.
- Attach authority blocks to prove who performed each action and whether they were authorized.
- Integrate log verification into CI/CD gates to prevent shipping with tampered or incomplete audit trails.
Tools this server exposes
| Tool | Does |
|---|---|
| append | Add a new record to the log with optional authority metadata binding the actor and their permissions. |
| verify | Check the hash chain integrity of the log and report whether tampering was detected and at which line. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.