chron-mcp 0.1.0 → 0.1.2

package/.claude-plugin/plugin.json

@@ -0,0 +1,19 @@
+{
+  "name": "chron",
+  "description": "Audit-grade timestamped logs for every AI conversation — stored locally, owned by you.",
+  "version": "0.1.1",
+  "author": {
+    "name": "Nivaya",
+    "email": "ksrinivas07530@gmail.com"
+  },
+  "homepage": "https://github.com/nivaya/chron",
+  "repository": "https://github.com/nivaya/chron",
+  "license": "MIT",
+  "keywords": [
+    "audit",
+    "logging",
+    "mcp",
+    "timestamps",
+    "ai-conversations"
+  ]
+}

package/LICENSE

@@ -0,0 +1,18 @@
+Copyright (c) 2026 Nivaya. All rights reserved.
+
+This source code is made publicly visible for transparency and review purposes only.
+
+You may NOT, without explicit written permission from the copyright holder:
+
+- Copy, clone, or download this source code for reuse
+- Fork this repository
+- Modify, adapt, or create derivative works
+- Redistribute or sublicense the source code or any portion of it
+- Use this source code as the basis for another product or service
+
+You MAY:
+
+- Use the published npm package (chron-mcp) as an end user
+- Read and review the source code
+
+For licensing inquiries, contact: ksrinivas07530@gmail.com

package/README.md

@@ -1,6 +1,8 @@
-# Chron
-
-> A timestamped audit trail for every AI conversation — stored locally, owned by you.
+<div align="center">
+  <img src="assets/chron-icon-png-transperent.png" alt="Chron" width="96" />
+  <h1>Chron</h1>
+  <p>A timestamped audit trail for every AI conversation — stored locally, owned by you.</p>
+</div>
 
 AI tools show when you sent a message. Chron logs when the AI responded too — and keeps a permanent, queryable record of every exchange across every tool you use.
 
@@ -204,4 +206,6 @@ No cloud, no telemetry, no data leaving your machine. Change the location with `
 
 ## License
 
-MIT
+Copyright (c) 2026 Nivaya. All rights reserved.
+
+Source code is public for transparency only. Cloning, forking, modification, and redistribution are not permitted without explicit written permission. See [LICENSE](LICENSE) for full terms.

package/package.json

@@ -1,10 +1,17 @@
 {
   "name": "chron-mcp",
-  "version": "0.1.0",
+  "version": "0.1.2",
+  "mcpName": "io.github.nivaya/chron",
   "description": "Audit-grade timestamped logs for every AI conversation",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/nivaya/chron.git"
+  },
   "main": "dist/index.js",
   "vitest": {
-    "include": ["tests/**/*.test.ts"],
+    "include": [
+      "tests/**/*.test.ts"
+    ],
     "globals": true
   },
   "bin": {
@@ -13,6 +20,8 @@
   "files": [
     "dist",
     "skills",
+    ".claude-plugin",
+    "assets",
     "README.md"
   ],
   "engines": {
@@ -34,13 +43,13 @@
     "claude",
     "cursor"
   ],
-  "license": "MIT",
+  "license": "SEE LICENSE IN LICENSE",
   "dependencies": {
     "@libsql/client": "^0.17.3",
     "@modelcontextprotocol/sdk": "^1.12.0",
     "drizzle-orm": "^0.30.10",
     "express": "^4.18.2",
-    "uuid": "^9.0.0",
+    "uuid": "^11.1.1",
     "zod": "^3.22.4"
   },
   "devDependencies": {

package/skills/chron/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: chron
+description: Use Chron to log every AI conversation with precise timestamps to a local SQLite database. Invoke at session start and on every exchange.
+---
+
+# Chron — AI Audit Log Skill
+
+Chron creates an audit trail of every AI conversation. Every message is logged with a precise local datetime (with timezone offset) to a local SQLite database the user owns.
+
+## Prerequisites
+
+Chron requires the MCP server to be running. If not yet configured:
+
+```bash
+# Claude Code
+claude mcp add chron npx -y chron-mcp
+```
+
+For other tools, add to your MCP config:
+```json
+{
+  "mcpServers": {
+    "chron": {
+      "command": "npx",
+      "args": ["-y", "chron-mcp"]
+    }
+  }
+}
+```
+
+## Session Start
+
+Call `start_session` with a descriptive title (e.g. "Contract review — 2026-05-08") and set `ai_tool` to your tool name (e.g. "claude", "cursor", "windsurf").
+
+Call `get_session_history` for the returned `session_id`. If prior messages exist, display:
+> "Resuming session: [N messages] since [first_message_date]"
+
+## Every Exchange
+
+1. Call `log_message(session_id, role="user", content=<exact user message>)` → returns T1
+2. Compose your response body (plain text only — no timestamp header)
+3. Call `log_message(session_id, role="assistant", content=<response body>)` → returns T2
+4. Output header + body:
+
+```
+[user: YYYY-MM-DD HH:MM:SS ±HH:MM | assistant: YYYY-MM-DD HH:MM:SS ±HH:MM]
+
+<response body>
+```
+
+T1 and T2 are real server timestamps — T2 − T1 is the actual generation time. The DB stores clean body content without the header.
+
+**Do not use `log_exchange` for live conversations** — it captures both timestamps at the same instant and cannot show a real gap. Use it only for batch imports of historical messages.
+
+## If Chron MCP is unavailable
+
+State once: "Chron is not connected — this conversation will not be logged."
+Continue normally. Do not retry repeatedly.