io.github.SirinivasK/chron
NPM · CHRON-MCP
Timestamped audit log for every AI conversation — stored locally in SQLite, owned by you.
Available components
Last scanned (27 minutes ago)
Scores higher than 35% of npm servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects drizzle-orm 0.30.10, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 145 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 345 tokens (~69/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/chron-mcp@0.1.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-gpj5-g38j-94v9 | CVE-2026-39356 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 145 packages
| Packages resolved | 145 |
|---|---|
| Stale | 41 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_session_history ~45
Retrieve the full timestamped audit log for a session, oldest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Return only the most recent N messages |
| session_id | string | yes | – |
No output schema declared.
No examples provided.
list_sessions ~49
List all audit sessions ordered by most recently active. Returns id, title, ai_tool, message_count, created_at, updated_at.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Return only the most recent N sessions |
No output schema declared.
No examples provided.
log_exchange ~100
Record a user+assistant exchange from historical or batch imports only. Do NOT use for live conversations — both timestamps are captured at the same instant with no real gap. For live sessions always call log_message twice: once for the user message, once for the assistant response.
| Name | Type | Req | Description |
|---|---|---|---|
| assistant_content | string | yes | The exact assistant response |
| session_id | string | yes | Session ID returned by start_session |
| user_content | string | yes | The exact user message |
No output schema declared.
No examples provided.
log_message ~71
Record a single message (user or assistant) with the current local datetime and timezone offset. Call before responding for user messages, and before sending for assistant messages.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full message text |
| role | string | yes | – |
| session_id | string | yes | Session ID returned by start_session |
No output schema declared.
No examples provided.
start_session ~80
Create a new audit session or resume an existing one by title. Call this at the start of every conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_tool | string | – | AI tool name: "claude", "cursor", "windsurf", etc. |
| title | string | yes | Descriptive session title, e.g. "Contract review — 2026-05-08" |
No output schema declared.
No examples provided.
How do I install the io.github.SirinivasK/chron MCP server?
io.github.SirinivasK/chron runs locally as an npm package, launched with npx -y chron-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · chron-mcp
claude mcp add sirinivask-chron -- npx -y chron-mcp
What is the io.github.SirinivasK/chron MCP server?
io.github.SirinivasK/chron is an MCP server listed in the public MCP registry as io.github.SirinivasK/chron. Timestamped audit log for every AI conversation, stored locally in SQLite, owned by you. This page covers its npm package (chron-mcp).
Is the io.github.SirinivasK/chron MCP server safe to use?
io.github.SirinivasK/chron scores 68 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.SirinivasK/chron MCP server expose?
io.github.SirinivasK/chron exposes 5 tools: start_session, log_message, log_exchange, list_sessions, get_session_history. Their descriptions and schemas cost roughly 345 tokens of context every time the server is loaded.
Is the io.github.SirinivasK/chron MCP server still maintained?
io.github.SirinivasK/chron is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.