io.github.tenlean/claude-checkpoint-mcp
NPM · CLAUDE-CHECKPOINT-MCP
MCP server that checkpoints Claude Code session context to survive crashes and token limits
Available components
Last scanned (8 hours ago)
Scores higher than 38% 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 565 tokens (~282/item across 2 items; 2 tools + 0 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 13 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ 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
- 12 Oct 26 38
First indexed and scored.
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 17 Oct 2026 · Analysed npm/claude-checkpoint-mcp@0.1.0
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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
load_session_checkpoint Load session checkpoint ~113
Load the project's .claude-checkpoint and return a compact brief of the previous session's goal, progress, next steps, touched files and recent commands, plus which files changed since it was saved. Call at the start of a session or when the user asks to resume.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | brief: compact markdown for resuming (recommended). full: the complete checkpoint JSON. |
| projectRoot | string | – | Absolute path of the project. Defaults to the client's workspace root or the server's working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| checkpoint | object | – | – |
| drift | – | – | – |
| found | boolean | yes | – |
| fromBackup | boolean | – | – |
| path | string | yes | – |
| updatedAt | string | – | – |
| warnings | array | yes | – |
No examples provided.
save_session_checkpoint Save session checkpoint ~322
Save the current session's goal, progress, touched files and recent commands to a .claude-checkpoint file in the project, so a new session can resume after a crash, /clear, or context limit without re-exploring. Call after finishing a milestone, before risky operations, and when the conversation is getting long. Git branch, HEAD and uncommitted files are captured automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions | array | – | Key decisions, constraints, and dead ends to avoid repeating. |
| goal | string | yes | The primary objective of the session, in one or two sentences. |
| mode | string | – | replace: overwrite the checkpoint. merge: update the existing one, appending commands, decisions and files. |
| modifiedFiles | array | – | Files you changed, with an optional note. Uncommitted git changes are detected automatically; list files here to annotate them or to include committed ones. |
| nextSteps | array | – | Concrete next actions, in order, for whoever resumes. |
| projectRoot | string | – | Absolute path of the project. Defaults to the client's workspace root or the server's working directory. |
| recentCommands | array | – | Recent significant terminal commands (builds, tests, migrations), oldest first, with exit codes and a short note on the outcome. Secrets are redacted automatically. |
| summary | string | – | Where things stand: what works, what is broken, what you were in the middle of. |
| tasks | array | – | Sub-goals with their status. In merge mode, tasks with the same description are updated. |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | number | yes | – |
| counts | object | yes | – |
| mode | string | yes | – |
| path | string | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the io.github.tenlean/claude-checkpoint-mcp server?
io.github.tenlean/claude-checkpoint-mcp runs locally as an npm package, launched with npx -y claude-checkpoint-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 · claude-checkpoint-mcp
claude mcp add tenlean-claude-checkpoint-mcp -- npx -y claude-checkpoint-mcp
What is the io.github.tenlean/claude-checkpoint-mcp server?
io.github.tenlean/claude-checkpoint-mcp is listed in the public MCP registry as io.github.tenlean/claude-checkpoint-mcp. MCP server that checkpoints Claude Code session context to survive crashes and token limits. This page covers its npm package (claude-checkpoint-mcp).
Is the io.github.tenlean/claude-checkpoint-mcp server safe to use?
io.github.tenlean/claude-checkpoint-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.tenlean/claude-checkpoint-mcp server expose?
io.github.tenlean/claude-checkpoint-mcp exposes 2 tools: save_session_checkpoint, load_session_checkpoint. Their descriptions and schemas cost roughly 435 tokens of context every time the server is loaded.
Is the io.github.tenlean/claude-checkpoint-mcp server still maintained?
io.github.tenlean/claude-checkpoint-mcp is still listed as active in the MCP registry. We last reached this channel on 17 October 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 io.github.tenlean/claude-checkpoint-mcp server under?
io.github.tenlean/claude-checkpoint-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.