#

Tamper-evident audit logs

for AI agents. Cryptographically signed, Bitcoin-anchored, and verifiable offline — even if TrustNotch is gone.

Three steps from action to proof #

1. Signed receipt on submissionAn agent submits an action over HTTP. TrustNotch returns an Ed25519-signed receipt immediately — a cryptographic commitment to the exact content logged.

2. Merkle-batched & Bitcoin-anchoredEntries are batched into an RFC 6962 Merkle tree. Each batch root is anchored to Bitcoin via OpenTimestamps, giving every entry a tamper-evident timestamp rooted in the world's most audited ledger.

3.   ### Verify offline, independentlyAnyone can verify any entry with the open-source [`trustnotch` verifier](/how-verification-works/) —
              no trust in TrustNotch required.
              The receipt, Merkle inclusion, and Bitcoin anchor are all checked
              locally. A proof keeps verifying even if TrustNotch disappears.

Get started #

Quickstart Get a key, record an entry, fetch its proof, and verify it yourself.

[MCP Server Connect Claude Desktop and other MCP clients to TrustNotch.](/trustnotch-mcp/)

[PyPI: trustnotch-mcp The MCP server package. Install with](https://pypi.org/project/trustnotch-mcp/)

`pip` or run with `uvx`. [PyPI: trustnotch The standalone offline verifier.](https://pypi.org/project/trustnotch/)

pip install trustnotch.