Chron

io.github.SirinivasKPublished by GitHub account SirinivasKv0.1.7Updated Oct 24, 2026

Timestamped audit log for every AI conversation — stored locally in SQLite, owned by you.

Overview

AI-generated overview

Chron keeps a timestamped local audit log of every AI conversation, stored in a SQLite database on your own machine.

What you can do
Chron records AI conversations as timestamped audit entries in a local SQLite database. The registry description says the log is stored locally and owned by you. No tool list is published, so the exact read, search, or export operations the assistant can call are not documented in the supplied material.
When to use it
Worth considering when you want a durable, locally held record of assistant conversations for later review, auditing, or personal reference, and you prefer that record to stay on your own machine rather than in a hosted service.
Requirements
Runs as a local process over stdio, installed from the npm package chron-mcp, so Node.js and npm are needed. It is desktop only. The environment variable CHRON_DB_PATH sets the path to the SQLite database file. No authentication is declared.
Before you install
The server writes conversation content to a local SQLite file, so anything discussed with the assistant may be persisted on disk in plain form; consider where CHRON_DB_PATH points and who can read that file. No credentials are requested by the manifest.

Installation

In SourceWeft

  1. Open Chron in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.7LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.