Cairn Remembers
PYPI · CAIRN-REMEMBERS
Local memory your AI tools share: decisions, notes and corrections that carry across sessions.
Available components
Last scanned (18 minutes ago)
Scores higher than 59% 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 Security50
- Malware scan not yet available for this package.Unverified
- 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 1 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 (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 41 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 885 tokens (~110/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −1
- Provenance: unverified → fail ▼ security
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Provenance: fail → unverified ▼ security
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ 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/cairn-remembers@0.3.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| 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 →
cairn_fetch ~141
Token-saving retrieval: ONE query returns a compact context pack of only the memories/files that matter, fitted to a token budget. Call this INSTEAD of re-reading files or scrolling history — it replaces the re-reading tax with a targeted answer. Top hits come back as capped previews (~1800 chars), the rest as gists — cairn_read returns any node's complete text (raise max_chars for very long nodes).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | optional: only return memories from this account/galaxy (case-insensitive) |
| budget_tokens | integer | – | max tokens in the pack |
| query | string | yes | what you need to know |
No output schema declared.
No examples provided.
cairn_logs ~162
The LIVE tail of the vault — newest nodes first, ALL kinds including conversation turns, embedded or not. This is how you see what just happened (fetch/search can't see un-embedded nodes until the nightly sleep). Filter by kind, session prefix, or a contains substring; follow up with cairn_read for full text (raise max_chars for very long nodes).
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | case-insensitive substring to search live text |
| kind | string | – | only this kind (e.g. conversation_turn, decision) |
| limit | integer | – | rows to return (max 60) |
| session | string | – | session id prefix (e.g. codex-) |
| unembedded_only | boolean | – | only nodes the nightly embed hasn't reached |
No output schema declared.
No examples provided.
cairn_note ~111
Write a memory to the vault — ambient capture. Use for decisions, insights, ideas, open items, warnings, procedures discovered while working. The vault remembers across sessions and models. Write the complete salient fact, decision, warning, or open item WITHOUT truncating it — but do not paste transcripts (turns are captured separately). For a large artifact, save the file and note its path and purpose.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| tags | array | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
cairn_orient ~38
Session-start context: the most recent compiled PROTOCOL digest plus open items. Call once at the beginning of a session to inherit prior context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cairn_read ~153
Read specific nodes IN FULL by id — the follow-up to the gists that recent/search/fetch return; this is the verbatim layer (long turns carry their complete text here). Accepts full ids or unambiguous prefixes, up to 8 per call; max_chars dials the per-node body budget. Unlike fetch/search this needs no embeddings, so it reads nodes written moments ago.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | node ids (or prefixes) to read |
| max_chars | integer | – | per-node canonical-body budget in chars (default 24000; total body across ids caps at max(60000, this)) — raise it to pull a very long turn whole, lower it to skim |
No output schema declared.
No examples provided.
cairn_recent ~59
The working set: recent decisions, open items, and warnings across the vault — what's live right now. Returns gists — pass ids to cairn_read for full text (raise max_chars for very long nodes).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
cairn_search ~82
Ranked hybrid search across the whole vault. Returns ids + gists + scores (cheap) — an index, not the text. Pass the ids that matter to cairn_read for their full text — raise max_chars for very long nodes (cairn_fetch for a budgeted context pack).
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
cairn_wander ~139
The creative complement to cairn_fetch. Walks the memory graph outward from the query's best hits, preferring WEAK ties that cross topic boundaries — surfaces adjacent ideas and unseen connections (a past project, an old conversation, an idea from a different domain) that similarity search will never return. Use when brainstorming, stuck, or asked for fresh angles. Returns gists — cairn_read pulls any hit in full (raise max_chars for very long nodes).
| Name | Type | Req | Description |
|---|---|---|---|
| hops | integer | – | how far to wander (1-5) |
| k | integer | – | – |
| query | string | yes | what you're working on or thinking about |
No output schema declared.
No examples provided.
How do I install the Cairn Remembers MCP server?
Cairn Remembers runs locally as a PyPI package, launched with uvx cairn-remembers. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · cairn-remembers
claude mcp add cairnremembers-cairn-remembers -- uvx cairn-remembers
What is the Cairn Remembers MCP server?
Cairn Remembers is an MCP server listed in the public MCP registry as io.github.CairnRemembers/cairn-remembers. Local memory your AI tools share: decisions, notes and corrections that carry across sessions. This page covers its PyPI package (cairn-remembers).
Is the Cairn Remembers MCP server safe to use?
Cairn Remembers scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 Cairn Remembers MCP server expose?
Cairn Remembers exposes 8 tools: cairn_fetch, cairn_wander, cairn_search, cairn_note, cairn_orient, and 3 more. Their descriptions and schemas cost roughly 885 tokens of context every time the server is loaded.
Is the Cairn Remembers MCP server still maintained?
Cairn Remembers 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 Cairn Remembers MCP server under?
Cairn Remembers declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.