CLIO Chronolog runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 11 Aug 2026.
Record and retrieve agent interactions in a ChronoLog log store.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
completed = subprocess.run(command, check=False)
full_path = os.path.join(download_path, filename)
slice_obj = eval(f"np.s_[{slice_spec}]")
baseline = dict(os.environ)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to CLIO Chronolog
same job, measured the same wayInteraction profile registry for AI agents. Log interactions, query behavioral lenses.
Interaction profile registry for AI agents. Log interactions, query behavioral lenses.
Verifiable action logs for AI agents. Every action is recorded in a SHA-256 hash chain.
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
Read relations, invoices, tasks and documents; create tasks and log interactions in AdminPulse.
Septic maintenance record: log inspections and pump-outs; next due date under EPA intervals. No AI.
Inspect GOV.UK guidance, check quotations, and monitor recorded HMRC changes. Free agent trial.
CLIO Chronolog — questions
Answers built from our own checks of this server.