
Security News
Happy Birthday, Shai-Hulud
It has been one year since Shai-Hulud made its first appearance on npm.
chainmemory-mcp
Advanced tools
Cross-model, cryptographically verifiable memory for Claude, ChatGPT, and any AI agent — own your AI's memory and carry it across every model. MCP server, 34 tools: remember, semantic search, on-chain verification proofs, forensic audit, selective inject,
Cross-model, cryptographically verifiable memory for Claude, ChatGPT, and any AI agent — own your AI's memory and carry it across every model.
ChainMemory MCP exposes the ChainMemory protocol to any AI agent that speaks the Model Context Protocol. Memories are encrypted at rest (AES-256-GCM, per-user), verifiable with Merkle proofs, and portable across ChatGPT, Claude, Gemini, Perplexity, and any other LLM. No vendor lock-in, ever.
audit_memory and audit_state — the two forensic audit endpoints, now reachable from any MCP client. Both accept dry_run: true, which returns the identical result without charging: an audit you can run as often as you like, and pay for only when you need the receipt on record. audit_state costs 5 AIC in its paid form, so the tools default to the dry run.Search and full reads
search_memories — semantic search over your memories (cosine similarity over cached embeddings, blended with recency and importance), returning the full text of each match. Previous versions exposed no search at allget_memory — read one memory in full, decrypted from chain, with an integrity check: the server recomputes the event hash from the plaintext and compares it against the hash anchored on-chainchainmemory_recall and list_memories_filtered now state plainly that they return 80-character previews, and point to get_memory / search_memories for the full textVerification — free, and the point of the product
verify_project_state — public, unauthenticated proof of a Project Brain: every anchored version with its state_hash and on-chain coordinates, plus how to check them yourself in the ProjectStateAnchor contract. No content is exposedget_memory_proof — the shareable anchoring proof of a single memory: event_hash plus its on-chain coordinates. A third party verifies it without your API key, and the content is never revealedCost control
quote_inject — price an inject before paying: which ids exist, which don't, tokens, exact cost with its burn/treasury split, and whether your balance covers itRoles and hardening
list_role_contracts — discover a project's roles (id, version, status) before reading a contract or assuming a role. Role ids are not guessable; this removes the failed-call round tripinclude_roles on get_project_state — set to false to get the state without the full text of every signed role contractCHAINMEMORY_API_KEY declared in the MCP manifest — the only mandatory variable was missing from server.json, so registries and installers never prompted for itget_project_state consolidates your atomic memories into a structured, versioned, verifiable project state (decisions, risks, constraints, metrics, and environment: where and how you work), and delivers active role contracts with it in a single callget_role_contract (read the contract), assume_role (open an audited Role Session), release_role (close with a summary)Visit https://faucet.chainmemory.ai. You receive an API key (aic_...) and a starter balance of AIC. ChainMemory collects no personal data — your key is your identity.
Edit your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"chainmemory": {
"command": "npx",
"args": ["-y", "chainmemory-mcp"],
"env": {
"CHAINMEMORY_API_KEY": "aic_your_key_here"
}
}
}
}
Restart Claude Desktop. The 34 tools are now available.
chainmemory_recallchainmemory_rememberget_project_state (Brain + active role contracts)list_role_contractsassume_role (audited Role Session)| Tool | Description |
|---|---|
chainmemory_remember | Write a permanent encrypted memory. Auto-tagged by content. |
chainmemory_recall | Recall the user's recent memories, newest first (80-character previews) |
search_memories | Semantic search over your memories — returns the full text of each match |
get_memory | Read one memory in full, decrypted from chain, with an on-chain integrity check |
list_memories_filtered | Filter by project tag and archived status (80-character previews) |
update_memory_tags | Change tags on an existing memory |
archive_memory | Hide a memory from recall (reversible) |
unarchive_memory | Restore an archived memory |
| Tool | Description |
|---|---|
verify_project_state | Public, unauthenticated proof of a Project Brain: every anchored version, its state_hash and on-chain coordinates, and how to check them yourself. No content exposed |
get_memory_proof | Shareable anchoring proof of one memory: event_hash + on-chain coordinates. A third party verifies it without your API key |
audit_memory | Forensic audit of one memory: recomputes its event_hash from the stored plaintext and compares it against the anchored one. 0.1 AIC, or free with dry_run: true |
audit_state | Full audit of a Project Brain: recomputes the state_hash with the deterministic engine, returns the on-chain anchor and the version history. 5 AIC, or free with dry_run: true |
| Tool | Description |
|---|---|
get_project_state | Consolidated, verifiable project state + active role contracts (state_hash, anchored on-chain). Pass include_roles: false to omit the contract bodies |
update_project_state | Propose structured ops (29-op grammar, incl. environment); server validates, builds, hashes, persists |
| Tool | Description |
|---|---|
list_role_contracts | List a project's roles with version and status — call it first when you don't know the role_id |
get_role_contract | Read a role's contract: purpose, rules with checks and severity, working protocol. Accepts version to audit a past one, and flags a hash mismatch if the stored body no longer matches its contract_hash |
assume_role | Open an audited Role Session under an active contract (pins contract + Brain hashes), and delivers the owner declared working environment |
release_role | Close a Role Session with a summary of work done and pending |
list_role_sessions | Audit trail: who assumed which role, when, how it closed, and the closing summary |
get_role_session | One session in full, with the contract and Brain hashes it was pinned to |
| Tool | Description |
|---|---|
list_projects | List the user's projects |
create_project | Create a custom project tag with optional auto-tag keywords |
delete_project | Delete a project tag |
list_project_templates | List built-in templates |
add_project_from_template | Instantiate a built-in template |
| Tool | Description |
|---|---|
chainmemory_stats | Network stats (AIs, memories, blocks, AIC supply) |
chainmemory_register | Register a new AI identity on-chain |
chainmemory_profile | Get an AI's profile and trust score |
chainmemory_seal | Seal a memory permanently (requires AICHAIN_KEY) |
| Tool | Description |
|---|---|
get_my_context | Portable verified context across all platforms |
| Tool | Description |
|---|---|
get_inject_balance | Check AIC balance and how many injects it covers |
quote_inject | Price an inject before paying: ids found/missing, tokens, exact cost, sufficiency. Free |
inject_memories | Inject 1-50 memories into current chat context (0.1 AIC, optimistic) |
get_inject_history | History of inject operations |
| Var | Required | Description |
|---|---|---|
CHAINMEMORY_API_KEY | Yes | Your API key from the faucet |
CHAINMEMORY_API_BASE | No | Default https://api.chainmemory.ai |
AICHAIN_KEY | No | Wallet private key — only required by chainmemory_seal |
AICHAIN_RPC | No | Default https://rpc.chainmemory.ai — only for chainmemory_seal |
For most users only CHAINMEMORY_API_KEY is needed.
inject_memories with a list of IDsget_inject_history shows confirmation status┌─────────────────────────────────────────────────────────────┐
│ AI Agent (Claude Desktop, ChatGPT, any MCP client) │
└──────────────────┬──────────────────────────────────────────┘
│ MCP stdio
↓
┌─────────────────────────────────────────────────────────────┐
│ chainmemory-mcp v2.5 (this package) │
└──────────────────┬──────────────────────────────────────────┘
│ HTTPS + x-api-key
↓
┌─────────────────────────────────────────────────────────────┐
│ api.chainmemory.ai │
│ - per-user encryption at rest (AES-256-GCM) │
│ - Project Brain (deterministic builder + state_hash) │
│ - Role contracts + audited Role Sessions │
│ - SQLite + Merkle proofs │
└──────────────────┬──────────────────────────────────────────┘
│ JSON-RPC
↓
┌─────────────────────────────────────────────────────────────┐
│ ChainMemory L1 — Chain ID 202604 │
│ - Geth PoA Clique, 3 validators │
│ - Memory contract + daily checkpoint anchoring │
│ - Project State anchoring (public verification) │
└─────────────────────────────────────────────────────────────┘
MIT
FAQs
Cross-model, cryptographically verifiable memory for Claude, ChatGPT, and any AI agent — own your AI's memory and carry it across every model. MCP server, 36 tools: remember, semantic search, on-chain verification proofs, forensic audit, selective inject,
The npm package chainmemory-mcp receives a total of 71 weekly downloads. As such, chainmemory-mcp popularity was classified as not popular.
We found that chainmemory-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Security News
It has been one year since Shai-Hulud made its first appearance on npm.

Research
/Security News
Operators behind PolinRider used a compromised GitHub account to plant malware in four development versions of a Packagist package with 700,000+ downloads.

Security News
GitHub Actions now supports cache-mode, a least-privilege control on the Actions cache aimed at the cache poisoning technique behind recent compromises.