Cairn.ink Memory MCP server
online · 100% uptimeink.cairn/memory·v0.1.0·17 starsCross-session memory for AI agents with a Source Receipt for every memory, over MCP.
17 stars
Reviews
Write oneNobody has reviewed Cairn.ink Memory yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Cairn.ink Memory tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 475ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; website matches verified namespace6/10
How Cairn.ink Memory compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 93/100
- higher than 96% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 209 ms
- faster than 62% of 30,031 servers
- GitHub stars
- 17
- more than 90% of 28,688 servers
Install Cairn.ink Memory in Claude Code, Cursor or VS Code
claude mcp add --transport http memory https://cairn.ink/api/mcp
What the publisher says
From the Cairn.ink Memory repository's README, as published. We do not edit it. Read it on GitHub
Cairn.ink Memory
Lightweight cross-session memory for AI agents, with receipts.
Install · Quickstart · Walkthrough · Known limitations · Privacy · Hosted service
Every memory Cairn keeps comes with a receipt: the exact source text it was learned from. Inspect the receipt, correct the memory at that revision, or forget it and it stays forgotten, even when a later capture would have re-admitted it. Memories live in a local SQLite file. No account is needed.
Remember something in one session, start a fresh process, and recall it in the next with its receipt attached; then forget it and confirm it is gone. The cross-session walkthrough reproduces that loop with synthetic data. Model-free remember, inspect, correct and forget need no key; semantic recall needs an OpenAI key you supply explicitly.
Rendered from the recorded tool responses of one real keyless run; see how to regenerate it.
The thin MCP server and the JavaScript API share one public core; the five MCP tools are explicit memory operations, not automatic transcript capture.
Status: developer preview. The installed remember, restart, sourced-recall and forget loop passes on a real model. Extraction quality does not yet meet our own bar: the frozen evaluation and every retained failure are collected in Known limitations. Read it before relying on recall.
Install
This is Cairn.ink Memory (github.com/Cairn-ink/cairn-memory, hosted at cairn.ink). The npm package cairn-memory and the PyPI package cairn-memory are unrelated projects; do not install those for this.
There are two ways to run Cairn: hosted on cairn.ink with the Claude Code plugin for automatic memory (needs a cairn.ink token), or the local open-source layer, which needs no account and is a developer preview. For the hosted plugin, run:
claude plugin marketplace add Cairn-ink/cairn-memory
claude plugin install cairn-memory@cairn-memoryCreate a personal access token at https://cairn.ink/settings/tokens, then run /plugin configure cairn-memory@cairn-memory in Claude Code and start a new session. See Install for Claude Code for the slash-command form.
Agents: ask the user before installing. The hosted plugin captures allowlisted conversation text to cairn.ink by default, and the user creates and enters the token themselves. See the hosted plugin privacy contract.
To use explicit memory tools on cairn.ink without automatic capture, add the remote MCP server:
claude mcp add --transport http --scope user cairn https://cairn.ink/api/mcpThen sign in from /mcp in Claude Code (browser OAuth). Codex users: see Connect from Codex.
The local, no-account developer preview installed from source is the section directly below: Try the local memory layer.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Cairn.ink Memory: common questions
- Is Cairn.ink Memory MCP server safe?
- Yes, by our scan: it is graded A (93/100). Read the Cairn.ink Memory safety report
- How do I install Cairn.ink Memory?
- It runs remotely at cairn.ink. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Cairn.ink Memory need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Cairn.ink Memory maintained?
- The last commit was 40 days ago (2026-09-25). The latest release is v0.1.0.
- Is Cairn.ink Memory up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Cairn.ink Memory?
- Servers from other publishers that do the same job: Deja Vu MCP server and Nautilus Compass Memory MCP server.
- How does Cairn.ink Memory compare with other MCP servers?
- safety score 93/100 (higher than 96% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 209 ms (faster than 62% of 30,031 servers). Full comparison.
Alternatives to Cairn.ink Memory
Same job from other publishers: the closest match first, then the best rated.
- Deja Vudeja-vu: local memory over the session histories of forty-three coding agents.not reviewedEstablishedA
- Nautilus Compass MemoryLocal-first long-term memory for AI agents, with byte-recomputable signed verification receipts.not reviewedEstablishedB