session-recap
NPM · SESSION-RECAP
Recap AI coding sessions (Claude Code, Codex, dsh, OpenCode): intent, decisions, open threads.
Available components
Last scanned (7 hours ago)
Scores higher than 30% of npm servers
Category Developer Tools
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 516 tokens (~172/item across 3 items; 3 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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 53
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 5 Nov 2026 · Analysed npm/session-recap@0.6.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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
list_sessions List AI coding sessions ~122
Lists saved sessions of Claude Code, Codex, dsh and OpenCode on this machine, newest first: agent, id, title, project folder, last activity. Filter by words in the title, by project folder, or by agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Only this agent; "any" for all (default) |
| cwd | string | – | Only sessions of this project folder (absolute path) |
| limit | number | – | At most this many (default 20) |
| query | string | – | Words in the title, or a session id |
No output schema declared.
No examples provided.
recap_session Recap a session ~239
Recaps a coding session: intent, key decisions, what changed, open threads, where to resume. With no session given, the newest session of the calling agent in `cwd`. Returns a stored recap when the session has not changed since. Otherwise, if session-recap has a model configured it writes the recap; if not, it returns the condensed transcript and instructions, and you write the recap yourself and store it with save_recap.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | The agent whose sessions to look in; default: the caller |
| cwd | string | – | The project folder you are working in (absolute path) |
| format | string | – | "recap" (default: intent, decisions, changes, open threads, resume), "standup", "handoff" or "pr" |
| mode | string | – | "agent": you write it; "model": session-recap writes it; "auto" (default): model if configured |
| refresh | boolean | – | Write it again even if a stored recap is current |
| session | string | – | A session id or words in its title; empty for the current session |
No output schema declared.
No examples provided.
save_recap Store a recap you wrote ~94
Stores the recap you wrote for a session after recap_session returned its transcript, so the next recap of that session is reused or updated from it. Pass the agent, id and prompts recap_session gave you.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | – |
| id | string | yes | – |
| markdown | string | yes | The recap, in the format recap_session asked for |
| prompts | number | yes | The prompt count recap_session reported |
No output schema declared.
No examples provided.
How do I install the session-recap MCP server?
session-recap runs locally as an npm package, launched with npx -y session-recap 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 · session-recap
claude mcp add brucexcluding-session-recap -- npx -y session-recap mcp
What is the session-recap MCP server?
session-recap is an MCP server listed in the public MCP registry as io.github.BruceXcluding/session-recap. Recap AI coding sessions (Claude Code, Codex, dsh, OpenCode): intent, decisions, open threads. This page covers its npm package (session-recap).
Is the session-recap MCP server safe to use?
session-recap scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting 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 session-recap MCP server expose?
session-recap exposes 3 tools: list_sessions, recap_session, save_recap. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.
Is the session-recap MCP server still maintained?
session-recap 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 session-recap MCP server under?
session-recap 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 session-recap MCP server?
VerifyMCP ran 14 checks on session-recap, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about session-recap: Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.