Skip to content
IsoKron

Open source · MCP server

A local MCP server that tells your agent when its notes went stale

kronicle-lite keeps runbooks and decisions in a hash-chained SQLite store, signs every search hit, and tells the agent what changed since it last looked.

Try the demo (a temporary directory, removed afterwards)
npx -y kronicle-lite demo
Run as an MCP server (stdio)
npx -y kronicle-lite serve

For developers whose agents work from notes that change: runbooks, decisions, procedures and instruction files.

Apache-2.0 · TypeScript · Node.js 20 or later · Built and maintained by IsoKron

What it does

  • A hash chain you can check. Every write is an event on a SHA-256 chain that anyone can recompute from a public starting point; verify-chain exits 1 on any mismatch.
  • Signed receipts. Every recall hit comes with a signed receipt that later answers whether it is still current: VERIFIED, SUPERSEDED, TOMBSTONED or UNVERIFIED.
  • An orient call. get_system_state takes the agent’s last cursor and returns what changed since, with a list of things it may have relied on that are now wrong, in words.
  • Honest labels. Each hit is marked can_act, inspect_only or never_act with the reason, and an empty answer says what was searched and what was not.
  • Secrets refused. Common secret shapes, such as API keys, tokens, private keys and connection strings, are refused before they reach the append-only chain.
  • Local. One process, one SQLite file, no accounts. It runs over stdio, or over loopback Streamable HTTP with a bearer token for clients that cannot start a process.

What it looks like

The demo stores a runbook, lets an agent read the deploy target, then changes the runbook behind its back. On its next orient call, before it acts, the agent is told what changed, and its old receipt no longer verifies as current.
npx -y kronicle-lite demo (steps 3 and 4)
3. Someone changes the runbook behind the agent's back.   $ sed -i 's/stg-west-2/stg-east-1/' runbook.md && kronicle-lite put runbook runbook.md   runbook rev 2: 1 block changed; head seq 9 4. The agent orients again with its cursor, before deploying.   Retractions (1): reconcile before acting   - [behavioral] seq 9: You previously relied on "Deploys go to the staging cluster `stg-west-2` first." (runbook › Deploy runbook › Deploy target); current truth is "Deploys go to the staging cluster `stg-east-1` first." (seq 9). Reconcile before proceeding.     changed: Deploys go to the staging cluster [-`stg-west-2`-]{+`stg-east-1`+} first.   verify(old receipt) → SUPERSEDED (superseded_by_newer_head); current block 417cd813…

Output of the demo, run on 14 November 2026. The demo goes on to edit the database file by hand, which verify-chain catches and rebuild repairs from the chain.

Used in our audits

Every Write-Safety Audit records its evidence in a kronicle-lite hash chain: the frozen harness, each run and the report, anchored and independently timestamped at each milestone. You check the Evidence Pack you receive with kronicle-lite’s verify-audit command, on your own machine.

To have your own server tested this way, see MCP server audits.

How to verify an Evidence Pack, step by step

Questions

Is kronicle-lite a memory server?

No. It sits beside one. Keep using whatever you use for knowledge graphs or semantic recall, and put the notes whose staleness would hurt in kronicle-lite.

Does anything leave my machine?

Not unless you ask. The store is a local SQLite file and needs no account. Anchoring a checkpoint off the machine is optional (checkpoint --push); it sends the checkpoint’s root, range, signature and public key, never events or content.

Which MCP clients does it work with?

Any client that can start a stdio server. For a client that cannot, serve --http serves Streamable HTTP on loopback with a bearer token. The README has setup snippets for common clients.

Where this fits

An IsoKron audit tests whether your MCP server’s writes change the right data under concurrency, stale data, retries and partial failure, plus a targeted security review and the tool catalog’s token cost.

Request an audit or a build

Tell us which server and what you need. We reply to confirm the scope, the price and the dates.