Chronicle MCP
PYPI · CHRONICLE-MCP-SERVER
Local, private AI chat history search & memory: BM25 over your Cursor, Claude and ChatGPT chats.
Available components
Last scanned (19 hours ago)
Scores higher than 89% of PyPI 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Leviathan0x0/Chronicle-MCP). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3500 tokens (~350/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Provenance: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- The attested source repository moved: Leviathan0x0/Chronicle-MCP security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.0.0 → 1.6.2 functional
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 pypi/chronicle-mcp-server@1.6.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Leviathan0x0/Chronicle-MCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Leviathan0x0/Chronicle-MCP/.github/workflows/publish.yml@refs/tags/v1.6.2 |
| Rekor log index | 3331212650 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:0bb21bea99f34c3db5058d3df185d483282b5d70eb484a7a2aec8916d68b553c |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| 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 →
compile_project_insights Compile Project Insights ~469
Derive structured insight from archived chats: action items, a topic index, a two-chat comparison, or a Markdown project brief. Use it when you need a digest rather than raw text; to find chats use search_history and to read them use get_chat_logs. insight_type 'action_items': TODOs, checkboxes and 'next' tasks from file_name (or the first of target_chats), returned as a list of strings. 'knowledge_index': chats grouped by topic, returned as {topic: [files], built_at}, or file counts when summary_only=true (use that on large archives); rebuild=true rescans every file. 'compare_chats': shared and unique topics of file_name_a and file_name_b (or the first two target_chats) as Markdown. 'project_brief': merges summaries and action items of target_chats (or file_name) into exports/<brief_title>.md and returns its path. Side effects: 'project_brief' writes or overwrites an export file; 'knowledge_index' rewrites the cached index file. Chat files are never modified.
| Name | Type | Req | Description |
|---|---|---|---|
| brief_title | string | – | Heading and export file name for 'project_brief' (an existing brief with this title is overwritten). |
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| file_name | – | – | Single chat file for 'action_items' (or a one-chat 'project_brief'), such as 'my-chat.json'. |
| file_name_a | – | – | First chat file for 'compare_chats'. |
| file_name_b | – | – | Second chat file for 'compare_chats'. |
| insight_type | string | yes | Which insight to produce (see the tool description). |
| rebuild | boolean | – | For 'knowledge_index': rescan all chats instead of returning the cached index. |
| summary_only | boolean | – | For 'knowledge_index': return file counts per topic instead of full file lists. |
| target_chats | – | – | Chat file names: all of them for 'project_brief', the first two for 'compare_chats', the first for 'action_items'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_chat_logs Read Chat Logs ~456
List archived chats, or read one chat as a message range, a short summary, or metadata. Use it after search_history to open a hit, or with no chat_id to browse the archive page by page. To search by topic use search_history instead. Without chat_id: returns a page header '[Page N of M (Total chats: T)]' followed by file names. With chat_id: view_type 'content' returns messages start_msg..end_msg as plain text with a '... of N total' header, truncating each message to max_msg_len characters and collapsing code blocks to one-line summaries unless summarize_code=false; 'summary' returns the opener and closer; 'metadata' returns {file_name, title, message_count, file_size_bytes, last_modified, saved_at, client}. Older chats are shown pruned to save tokens. Keep ranges small (the default is 20 messages): max_msg_len=0 with a wide range can return a whole transcript. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | – | – | Chat file or chunk id to read, such as 'my-chat.json' or 'my-chat__part_2.json'. Omit to list chats. |
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| end_msg | integer | – | Last message to return (inclusive) for view_type='content'. |
| max_msg_len | integer | – | Per-message character cap for view_type='content'; 0 means no cap (can be very large). |
| page | integer | – | Page number (1-based) when listing chats without chat_id. |
| per_page | integer | – | Chats per page when listing without chat_id. |
| start_msg | integer | – | First message to return (1-based) for view_type='content'. |
| summarize_code | boolean | – | Replace fenced code blocks with a one-line language and line-count summary to save tokens. |
| view_type | string | – | What to return for chat_id: message text ('content'), file statistics ('metadata') or a short 'summary'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_handoff_status Get Handoff Status ~168
Check whether this workspace has unfinished work handed off by an earlier agent. Call it at the start of a session on a project, before editing; to record a handoff use save_handoff_receipt. Returns {blocked, blocked_by_receipt, active_chain (newest first), newest_receipt_id, next_safe_action}; with no receipts it returns {blocked: false, reason, active_chain: []}. When blocked is true, follow next_safe_action (stale receipts tell you to re-verify first). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| Name | Type | Req | Description |
|---|---|---|---|
| active_chain | array | – | – |
| blocked | boolean | – | – |
| blocked_by_receipt | – | – | – |
| newest_receipt_id | – | – | – |
| next_safe_action | – | – | – |
| reason | – | – | – |
No examples provided.
maintain_storage Maintain Storage ~369
Housekeeping for the archive: compress old chats, find or remove duplicates, change settings, or report server capabilities. Use it for storage and configuration only, not for reading or searching chats. op_type 'compress': gzips chats older than days_old (default from settings, 30) in place and returns {compressed, skipped_recent, days_threshold}; compressed chats stay readable and searchable. 'deduplicate': finds chats with identical content; with dry_run=true (default) it only lists them, with dry_run=false it permanently deletes the duplicates, returning {dry_run, duplicates, unique_count}. 'configure': updates settings (see 'settings') and returns which keys changed. 'capabilities': read-only summary of tools, prompts, version and client paths. Destructive only for deduplicate with dry_run=false; ask the user before doing that.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| days_old | – | – | For 'compress': minimum age in days; omit to use compression_days_threshold (30 by default). |
| dry_run | boolean | – | For 'deduplicate': true lists duplicates only; false deletes them permanently. |
| op_type | string | yes | Maintenance operation (see the tool description). |
| settings | – | – | For 'configure' only. Allowed keys: auto_save_message_threshold (int, messages before manage_session_state save persists), compression_days_threshold (int), summary_pruning_days_threshold (int), clie… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
manage_session_state Manage Session State ~461
Save, auto-save, merge, export or delete archived conversations, and watch the archive for changes. Use it to persist the current conversation; to import outside history use sync_workspace_data. action 'register_auto_save': remember conversation_name and messages so they are written when the client disconnects (call it early and re-call it to refresh). 'trigger_auto_save': write the registered session now. 'save': write messages to <conversation_name>.json, overwriting a chat with that name; below the auto_save_message_threshold (default 20) it is skipped unless force_save=true. 'merge': append new_messages to file_name, skipping duplicates. 'export_markdown': write exports/<name>.md. 'delete': permanently delete file_name; refused unless confirm=true, so ask the user first. 'watch_folder': report {new_files, modified_files, total_tracked} since the last call (only updates the watch checkpoint). Returns a confirmation string, or the report object for 'watch_folder'.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Operation to perform (see the tool description). |
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| confirm | boolean | – | Must be true for 'delete' to proceed; deletion is permanent. |
| conversation_name | – | – | Conversation title for 'save' and 'register_auto_save' (also the file name); used as file_name for other actions when file_name is omitted. |
| file_name | – | – | Existing chat file for 'merge', 'export_markdown' and 'delete', such as 'my-chat.json'. |
| force_save | boolean | – | For 'save': write even when the message count is below the auto-save threshold. |
| messages | – | – | Chat messages as objects with 'role' ('user', 'assistant' or 'system') and 'content' (text). 'text' is accepted in place of 'content'; extra keys such as 'timestamp' are kept. |
| new_messages | – | – | Messages to append for 'merge' (same shape as 'messages'); falls back to 'messages'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
save_handoff_receipt Save Handoff Receipt ~488
Record what this agent run did and what the next agent must do, as a handoff receipt for the current workspace. Use it before stopping or handing work to another agent or model; read the current state with get_handoff_status. A receipt with status 'open' (the default) marks the workspace as blocked until a later receipt supersedes it with status 'closed' and a closure (closed_by, closed_at, closure_basis). It becomes stale automatically when any file listed in invalidation.stale_if changes after it was saved. Receipts are stored as new JSON files in the archive (never overwritten), indexed, and ranked first in search_history. Returns the saved file name and its receipt_id (pass that as 'supersedes' later).
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| closure | – | – | Required to close: {'closed_by': str, 'closed_at': ISO-8601 str, 'closure_basis': str, 'closure_evidence': str}. |
| evidence | object | yes | Proof: {'checks_run': [{'command': str, 'exit_code': int, 'stdout_summary': str}], 'missing_evidence': [str] (checks skipped or not yet run)}. |
| invalidation | object | yes | When to distrust this receipt and what to do next: {'stale_if': [{'file_path': str} or {'glob_pattern': str}], 'next_safe_action': str (a direct instruction for the next agent)}. |
| obligations | object | yes | What was promised: {'promise': str (the goal), 'scope': [str] (areas or files in scope)}. |
| receipt_id | – | – | Explicit receipt id. Defaults to '<workspace-hash>_<unix-time>'. |
| status | string | – | 'open' (work outstanding, blocks the workspace) or 'closed' (finished; needs 'closure'). |
| supersedes | – | – | receipt_id of the earlier receipt this one replaces, forming a chain. |
| work_state | object | yes | What was done: {'touched_surfaces': [{'file_path': str, 'summary': str, 'why': str}], 'dependencies': [str]}. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_history Search Chat History ~429
Search the local chat archive and return matching transcript chunks. Use this first to recall past work on a topic; then read a hit with get_chat_logs. For extracted action items, comparisons or briefs use compile_project_insights instead. Methods: 'semantic' (default) ranks chunks with Okapi BM25 plus recency decay and returns [{file, score}]; 'keyword' returns chunk ids containing every keyword; 'date_range' returns [{file_name, last_modified}] for chats saved between start_date and end_date; 'related' returns [{file, score}] for chats similar to file_name. Chunk ids look like 'name__part_2.json' and can be passed to get_chat_logs as chat_id. Active handoff receipts are ranked first. Read-only for chat data; it refreshes the local search index cache. An empty archive returns a single placeholder entry such as 'No stored chats found.'.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Archive namespace (a subfolder of the chats directory). Built-in: 'default', 'cursor', 'chatgpt', 'claude'; any other name creates its own subfolder. Omit to use 'default'. |
| end_date | – | – | Inclusive end date (YYYY-MM-DD, UTC) for method='date_range'. Required with start_date. |
| file_name | – | – | Reference chat file for method='related' (for example 'my-chat.json'). Falls back to 'query'. |
| keywords | – | – | Exact terms for method='keyword'; all must appear. Overrides 'query' for that method. |
| limit | integer | – | Maximum results for 'keyword' and 'date_range' searches. |
| method | string | – | Search strategy (see the tool description). |
| query | string | – | Free-text query for 'semantic' search; for 'keyword' it is split on spaces when 'keywords' is omitted. |
| start_date | – | – | Inclusive start date (YYYY-MM-DD, UTC) for method='date_range'. Required with end_date. |
| top_k | integer | – | Maximum results for 'semantic' and 'related' searches. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
sync_workspace_data Import Chats ~392
Import conversations into the archive from pasted content, a local file, or an editor's transcript folder, normalizing ChatGPT, Claude, Cline/Continue JSON, JSONL and Markdown formats. Use it to bring outside history in; to save the current conversation use manage_session_state(action='save'). source_type 'raw_content': payload is the chat JSON (string or object); 'local_path': payload is a file path inside the archive, the current directory, the temp directory or a configured transcripts folder (other paths are refused); 'agent_transcripts': scans the transcripts folder for 'client' ('cursor', 'continue', 'cline', 'copilot', or source_dir) and imports up to 'limit' newest files, skipping ones already imported; 'cursor_agent_transcripts' is a deprecated alias for Cursor. Writes new JSON files into the archive and updates the search index; never deletes. Imports with an existing title overwrite that chat. Returns a confirmation string for single imports, or {imported: [{file, status, dest}], errors, total_scanned} for folder syncs.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Archive namespace to import into; for 'agent_transcripts' it also picks the source editor ('cursor', 'continue', 'cline', 'copilot'). Omit for 'default'. |
| limit | integer | – | Maximum newest transcript files to scan for folder syncs. |
| payload | – | – | Chat JSON for 'raw_content', a file path for 'local_path', or a folder path for 'agent_transcripts' (same as source_dir). |
| source_dir | – | – | Override folder to scan for 'agent_transcripts'; must be inside an allowed root. |
| source_type | string | yes | Where to import from (see the tool description). |
| title | – | – | Archive name for 'raw_content' or 'local_path' imports. Defaults to a timestamped or source-derived name. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
How do I install the Chronicle MCP server?
Chronicle MCP runs locally as a PyPI package, launched with uvx chronicle-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · chronicle-mcp-server
claude mcp add leviathan0x0-chronicle-mcp -- uvx chronicle-mcp-server
What is the Chronicle MCP server?
Chronicle MCP is listed in the public MCP registry as io.github.Leviathan0x0/chronicle-mcp. Local, private AI chat history search & memory: BM25 over your Cursor, Claude and ChatGPT chats. This page covers its PyPI package (chronicle-mcp-server).
Is the Chronicle MCP server safe to use?
Chronicle MCP scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Chronicle MCP server expose?
Chronicle MCP exposes 8 tools: search_history, get_chat_logs, sync_workspace_data, compile_project_insights, maintain_storage, and 3 more. Their descriptions and schemas cost roughly 3,232 tokens of context every time the server is loaded.
Is the Chronicle MCP server still maintained?
Chronicle MCP 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.
What licence is the Chronicle MCP server under?
Chronicle MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Chronicle MCP server?
VerifyMCP ran 16 checks on Chronicle MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.