io.github.emretheus/claude-remind-mcp
NPM · CLAUDE-REMIND-MCP · SCANNED SEP 20
Search past Claude Code conversations. Local BM25 over JSONL with one-click claude --resume.
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 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to emretheus/claude-remind-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 132 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 846 tokens (~211/item across 4 items; 4 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% 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 4 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.emretheus/claude-remind-mcp server?
io.github.emretheus/claude-remind-mcp runs locally as an npm package, launched with npx -y claude-remind-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-remind-mcp
claude mcp add emretheus-claude-remind-mcp -- npx -y claude-remind-mcp
{
"mcpServers": {
"emretheus-claude-remind-mcp": {
"command": "npx",
"args": [
"-y",
"claude-remind-mcp"
]
}
}
} {
"servers": {
"emretheus-claude-remind-mcp": {
"command": "npx",
"args": [
"-y",
"claude-remind-mcp"
]
}
}
} codex mcp add emretheus-claude-remind-mcp -- npx -y claude-remind-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"emretheus-claude-remind-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"claude-remind-mcp"
],
"enabled": true
}
}
} openclaw mcp add emretheus-claude-remind-mcp --command npx --arg -y --arg claude-remind-mcp
mcp_servers:
emretheus-claude-remind-mcp:
command: "npx"
args: ["-y", "claude-remind-mcp"] {
"McpServers": {
"emretheus-claude-remind-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"claude-remind-mcp"
]
}
}
} assistant mcp add emretheus-claude-remind-mcp -t stdio -c npx -a -y claude-remind-mcp
{
"mcpServers": {
"emretheus-claude-remind-mcp": {
"command": "npx",
"args": [
"-y",
"claude-remind-mcp"
]
}
}
} 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 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.
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 npm/claude-remind-mcp@0.1.1
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | emretheus/claude-remind-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/emretheus/claude-remind-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 1498264238 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e2bce351c33d0bbad83924fce25625a944af6bbc9d28041a66e97181010c8207b6a63be79a607955376d9a2b7b0f6bb66bf0d5f1188932d99f4bc4369 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
remind_message ~210
Fetch the full text of a specific past message, plus optional surrounding turns. Returns up to ~10 KB; the matched message is flagged with `isFocus: true` inside the returned window. When to use: only after `remind_search` returns a `messageUuid` whose snippet looks promising but is truncated. Don't call this for every search hit — pick the one or two most relevant first. If you want a structural overview of the whole session (tools, files, errors), call `remind_session` instead. To read the entire session, omit `messageUuid` (capped at 50 messages).
| Name | Type | Req | Description |
|---|---|---|---|
| contextAfter | integer | – | Messages after the focus message. |
| contextBefore | integer | – | Messages before the focus message. |
| messageUuid | string | – | Optional. If provided, returns this message plus context window. If omitted, returns all indexed messages of the session (capped at 50). |
| sessionId | string | yes | Full or prefix of the session UUID. |
No output schema declared.
No examples provided.
remind_resume ~124
Resolve a (full or 8-char prefix) session id into a ready-to-run `claude --resume <id>` command, plus the session's cwd and git branch. When to use: only when you already have a sessionId in hand and need just the resume command. `remind_search` already returns `resumeCommand` on every hit, so prefer that. This tool exists for cases where the user pastes a bare sessionId or a previous tool flow stored only the id.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Full or prefix of the Claude session UUID. |
No output schema declared.
No examples provided.
remind_search ~377
Search past Claude Code sessions for solutions to recurring problems. Returns BM25-ranked hits with a snippet, a `solvedHint`, a `messageUuid`, and a ready-to-paste `claude --resume <id>` command. When to use: at the start of a task to check for prior work on the same codebase; or when the user mentions an error, tool, or feature they may have already solved. One call is usually enough — only re-call with a different query if the first returned no useful hits. Query tips: use specific concrete terms — exact error strings (`ExpiredTokenException`, `LoginRefreshRequired`), tool/lib names (`BuildKit`, `Cognito`, `Tailwind`), or real file paths (`tailwind.config`, `shared_auth/jwt.py`). Avoid generic words that flood the corpus (e.g. `AWS`, `auth`, `docker` on their own). Good: `ExpiredTokenException SendSSHPublicKey`. Bad: `AWS auth issue`. Cost: ~1–2 KB per call at default (5 hits, 1000-char snippets). Use `format: "compact"` (400 chars) for cheap scans, `format: "full"` (2000 chars) when you need to read in place. After finding a relevant hit, call `remind_message` with its `messageUuid` to read the full content.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Snippet length: compact=400, detailed=1000, full=2000 chars. |
| limit | integer | – | – |
| project | string | – | Optional. Substring match against the session's cwd (e.g. 'my-app'). |
| query | string | yes | Free-text search query. |
| sinceDays | integer | – | Optional. Only include sessions updated within the last N days. |
No output schema declared.
No examples provided.
remind_session ~135
Get a structured summary of one past session: title, message count, tool names used, files touched, error count, time span, solved hint, and the last user message. Cheap (~1 KB). When to use: when a `remind_search` hit looks relevant and you need the bigger picture (was this session productive? which tools/files were involved?) before drilling into specific messages. Requires a `sessionId` — the 8-char prefix from a search hit is enough. To read message bodies, use `remind_message` instead.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | Full or prefix of the Claude session UUID. |
No output schema declared.
No examples provided.
What is the io.github.emretheus/claude-remind-mcp server?
io.github.emretheus/claude-remind-mcp is listed in the public MCP registry as io.github.emretheus/claude-remind-mcp. Search past Claude Code conversations. Local BM25 over JSONL with one-click claude --resume. This page covers its npm package (claude-remind-mcp).
Is the io.github.emretheus/claude-remind-mcp server safe to use?
io.github.emretheus/claude-remind-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.emretheus/claude-remind-mcp server expose?
io.github.emretheus/claude-remind-mcp exposes 4 tools: remind_search, remind_message, remind_session, remind_resume. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the io.github.emretheus/claude-remind-mcp server still maintained?
io.github.emretheus/claude-remind-mcp 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.
What licence is the io.github.emretheus/claude-remind-mcp server under?
io.github.emretheus/claude-remind-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.