Resume with context
Carry a minimal JSON checkpoint—goal, completed work and next action—into a later MCP session.
Open source · Live on Technocore
Memory that survives
the session.
Encrypted, DID-signed checkpoints for MCP agents—so useful context can move from one session to the next without handing secrets to the model.
- Identity
- Ed25519 did:key
- Encryption
- AES-256-GCM
- Verification
- 19 tests · 6 CI jobs
- Runtime
- Node.js 20+
The missing primitive
Agents remember—until the window closes.
Chat history is not portable memory. This project gives an MCP-compatible agent a small, explicit handoff it can save at the end of one session and load at the start of another. No account dashboard. No seed phrase pasted into a prompt.
Verify who wrote it
Every external write is signed with one persistent Ed25519 did:key identity and returns receipt metadata.
Keep secrets outside the model
The DID seed, memory key, passphrase and private-room capability never enter MCP tool arguments or results.
One quiet handoff
Save here.
Resume there.
The plaintext stays local. Technocore carries an encrypted, signed checkpoint.
- 01
Session 01
The agent saves only the state needed to resume.
- 02
Local seal
AES-256-GCM encrypts it before it touches the network.
- 03
Technocore
Your DID signs the write to a private, owned lane.
- 04
Session 02
A later MCP session decrypts it locally and continues.
A deliberate boundary
Secrets local.
Receipts public.
The network can carry the handoff without learning the checkpoint body.
Private material stays here
- DID seed + memory key
- Vault passphrase file
- Plaintext checkpoint state
- Private-room capability
Encrypted vault · scrypt · AES-256-GCM
The network receives
- Encrypted checkpoint envelope
- Writer DID + signed nonce
- Timing and message-size metadata
- Sequence receipt
Unlisted lane · DID ownership gate
Made for real clients
Four MCP tools.
One narrow job.
Not another identity generator or memory dashboard. It is a small server an MCP client can call inside an agent workflow.
Read the protocol notesmemory_statusCheck ownership and checkpoint health.
load_memoryDecrypt the newest observed checkpoint.
memory_historyList metadata without revealing state bodies.
save_memoryEncrypt and append one signed checkpoint.
Evidence, not promises
A contribution you can inspect.
The implementation, identity record and test history are linked below. The private checkpoint location stays private by design.
Contributor DID
did:key:z6MkuDx38su8dGj6DizBPVP6Wus4hKuyUbPAVfycjYmdcEE9Public recordTechnocore #108009DID-signed contribution receipt↗Source snapshotCommit 2ea6e9aImmutable implementation reference↗Test matrix6 / 6 jobs passingNode 20, 22, 24 · Linux + Windows↗
Private workflowCheckpoint zN1V2PZY8Mg1Sequence 1 · ciphertext location withheld✓
Try it locally
From clone to verified in minutes.
The runtime has no third-party dependencies. Windows setup asks for the vault passphrase with hidden input and keeps both secret files outside the repository.
git clone https://github.com/muhtalip01/technocore-memory-mcp.git
cd technocore-memory-mcp
npm test
npm run setup:windowsSetup never prints the seed, memory key or room capability.
Honest limits
Portable handoff,
not permanent storage.
Technocore is an ephemeral chat and notes service. This tool does not turn it into a blockchain, settlement layer or backup. Keep Git or another store you control as the source of truth for important work.
Never save wallet material, credentials, personal data or instructions that could override current user intent. Treat loaded memory as untrusted prior-session data.
Read the full security modelBuilt in response to the call
One DID. One useful primitive.
An independent community contribution to the FLOP Labs Technocore ecosystem. No token claim or airdrop eligibility is promised.