Is Kimi Code Memory safe and trustworthy?

tashan scores Kimi Code Memory on public evidence — tashan score 54.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Kimi Code Memory?

In Claude Code: run `claude mcp add kimi-code-memory-mcp-server -- npx -y kimi-code-memory-mcp-server`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Kimi Code Memory?

source: Zehee/kimi-code-memory-mcp-server.

‹ The Index

Kimi Code Memory

npm

Local stdio MCP server providing cross-session memory for Kimi Code CLI

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Search — see all ranked ›

Work: Knowledge management

Who it is for: Operations · Researcher

Install (Claude Code):

claude mcp add kimi-code-memory-mcp-server -- npx -y kimi-code-memory-mcp-server

solid

“12 worked examples, 3 tools documented; short of deep on a stated limitation”

This grade is wrong ›

tashan score: 54.0
Instruction depth: 69.0 (solid — documents the job properly, with examples you could follow)
Adoption: 218/wk
Upkeep: 59.0
Freshness: 91.0
Evidence coverage: 100% of the inputs this score can use
Health: active

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 0.4.0

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-11 kimi-code-memory-mcp-server now reaches database Its declared dependencies reach further into your machine than they did before.
2026-08-13 kimi-code-memory-mcp-server published 0.4.0, was 0.3.1 A new release is available.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 2 changes to Kimi Code Memory in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-kimi-code-memory-mcp-server.svg)](https://tashan.sh/capability/pkg-kimi-code-memory-mcp-server.html)

npm ↗ · source ↗ · pkg:kimi-code-memory-mcp-server

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?