ChainMemory
Verifiable, portable AI memory. Optional vault: encrypted on your machine, 12 words only you hold.
The current version, v2.10.0, was published to the official MCP registry on 2026-10-10. It is distributed as chainmemory-mcp on npm, filed under Security by this index, and declares 7 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using ChainMemory in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“No malicious instructions”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - Still current: the description we screened is unchanged, re-checked against the registry
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-10-30).
Contracts can change after screening, with no version bump. The gate pins ChainMemory’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for ChainMemory](https://mcpindex.ai/server/io-github-chaelynet-chainmemory) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-chaelynet-chainmemory">Independent trust record for ChainMemory</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-chaelynet-chainmemory)<a href="https://mcpindex.ai/server/io-github-chaelynet-chainmemory"><img src="https://mcpindex.ai/api/v1/badge/io-github-chaelynet-chainmemory" alt="mcpindex verdict" height="20" /></a>CHAINMEMORY_API_KEYChainMemory API key. REQUIRED for every tool except chainmemory_seal. Get one at https://faucet.chainmemory.ai
CHAINMEMORY_SEED_PHRASE12-word BIP-39 phrase for the blind vault. Optional: without it the server works exactly as before. With it, sealed:true encrypts a memory on your machine and computes its search vector here, so sealed memories can still be found, and searches send the query's vector instead of its text. Generate one with chainmemory_new_seed. It never leaves your machine and cannot be recovered.
CHAINMEMORY_API_BASEAPI base URL (default: https://api.chainmemory.ai)
CHAINMEMORY_MODELS_DIRFolder for the 45 MB search model used with the blind vault (default: ~/.chainmemory/models). Downloaded once from models.chainmemory.ai and checked against its SHA-256 anchored on ChainMemory's chain.
CHAINMEMORY_ALLOW_FULLSet to 1 to let get_project_brief return the FULL level (addresses, ports, server paths and security rules) when you ask for it. Leave it empty to keep every brief at the public level, which is safe to paste anywhere. Works only with the owner's key, and ChainMemory logs every full-level request.
AICHAIN_KEYNOT NEEDED for normal use — leave it empty. Only the chainmemory_seal tool reads it, to sign a contract call yourself instead of letting the API anchor the memory (which chainmemory_remember already does). If you do set it, it is a wallet private key: use a dedicated wallet holding only a few AIC, never your main one. No other tool uses it.
AICHAIN_RPCRPC endpoint used only by chainmemory_seal (default: https://rpc.chainmemory.ai). Leave it empty unless you set AICHAIN_KEY.
Sourced, scored comparisons of crypto exchanges, wallets, savings accounts and brokerages.
Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.
Primary-source lithium & battery-metals mining data (AISC, reserves, filings) via x402.