io.github.constripacity/claude-replay
PYPI · CLAUDE-REPLAY · SCANNED SEP 20
Session checkpoint & recovery for Claude Code: resume, search, tag, and export recorded sessions.
Available components
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 hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 33 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 639 tokens (~63/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 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
How do I install the io.github.constripacity/claude-replay MCP server?
io.github.constripacity/claude-replay runs locally as a PyPI package, launched with uvx claude-replay. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · claude-replay
claude mcp add constripacity-claude-replay -- uvx claude-replay
{
"mcpServers": {
"constripacity-claude-replay": {
"command": "uvx",
"args": [
"claude-replay"
]
}
}
} {
"servers": {
"constripacity-claude-replay": {
"command": "uvx",
"args": [
"claude-replay"
]
}
}
} codex mcp add constripacity-claude-replay -- uvx claude-replay
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"constripacity-claude-replay": {
"type": "local",
"command": [
"uvx",
"claude-replay"
],
"enabled": true
}
}
} openclaw mcp add constripacity-claude-replay --command uvx --arg claude-replay
mcp_servers:
constripacity-claude-replay:
command: "uvx"
args: ["claude-replay"] {
"McpServers": {
"constripacity-claude-replay": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"claude-replay"
]
}
}
} assistant mcp add constripacity-claude-replay -t stdio -c uvx -a claude-replay
{
"mcpServers": {
"constripacity-claude-replay": {
"command": "uvx",
"args": [
"claude-replay"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 20 Sept 2026 · Analysed pypi/claude-replay@0.4.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| 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 →
replay_checkpoint ~35
Force a checkpoint of the current session right now, with an optional note.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional note describing the checkpoint |
No output schema declared.
No examples provided.
replay_diff ~56
Compare two sessions side by side: metric deltas (tool calls, errors, duration, files) and which files each touched.
| Name | Type | Req | Description |
|---|---|---|---|
| session_a | string | yes | First session ID |
| session_b | string | yes | Second session ID |
No output schema declared.
No examples provided.
replay_export ~77
Render a session as a self-contained trace (html, json, or md) and return the output path.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Export format (default: html) |
| output | string | – | Output directory (default: ~/.claude-replay/exports) |
| session_id | string | – | Session ID (default: most recent) |
No output schema declared.
No examples provided.
replay_insights ~53
Per-session insight metrics: how it ended, duration, tool-call count, error count/rate, files touched, and the most-used tools.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | Session ID (default: most recent) |
No output schema declared.
No examples provided.
replay_resume ~54
Generate a structured resume brief for a session (default: the most recent). Paste the result into a new Claude Code session to continue where it left off.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | – | Session ID (default: most recent) |
No output schema declared.
No examples provided.
replay_search ~142
Full-text search across recorded sessions (event payloads, objective, name, and tags), with optional filters. Ranked by match count. Omit the query to browse by filters alone.
| Name | Type | Req | Description |
|---|---|---|---|
| cause | string | – | Only sessions with this death cause |
| limit | integer | – | Max sessions (default: 20) |
| project | string | – | Only sessions whose project dir contains this |
| query | string | – | Text to search for (optional if filtering) |
| since | string | – | Only sessions started after this ISO date |
| tool | string | – | Only sessions that used this tool |
| until | string | – | Only sessions started before this ISO date |
No output schema declared.
No examples provided.
replay_sessions ~38
List recent sessions with status, model, duration, and checkpoint count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max sessions to list (default: 10) |
No output schema declared.
No examples provided.
replay_stats ~80
Cross-session analytics across all recorded sessions: total tool calls, overall error rate, why sessions end (death-cause breakdown), the tool mix, and per-project rollups. Optional limit / project filter.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Only the N most recent sessions (default: all) |
| project | string | – | Only sessions whose project dir contains this |
No output schema declared.
No examples provided.
replay_status ~23
Current session summary: objective, status, checkpoint/event counts, last activity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
replay_tag ~81
Name or tag a session for later retrieval. Sets a name and/or adds/removes tags on a session (default: the most recent).
| Name | Type | Req | Description |
|---|---|---|---|
| add | array | – | Tags to add |
| name | string | – | Human-friendly name |
| remove | array | – | Tags to remove |
| session_id | string | – | Session ID (default: most recent) |
No output schema declared.
No examples provided.
What is the io.github.constripacity/claude-replay MCP server?
io.github.constripacity/claude-replay is an MCP server listed in the public MCP registry as io.github.constripacity/claude-replay. Session checkpoint & recovery for Claude Code: resume, search, tag, and export recorded sessions. This page covers its PyPI package (claude-replay).
Is the io.github.constripacity/claude-replay MCP server safe to use?
io.github.constripacity/claude-replay scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.constripacity/claude-replay MCP server expose?
io.github.constripacity/claude-replay exposes 10 tools: replay_status, replay_checkpoint, replay_resume, replay_sessions, replay_export, and 5 more. Their descriptions and schemas cost roughly 639 tokens of context every time the server is loaded.
Is the io.github.constripacity/claude-replay MCP server still maintained?
io.github.constripacity/claude-replay is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.