mnemo
On-prem, MCP-native memory for AI agents in regulated settings: every write lands in a SHA-256 hash-chained log an auditor can verify offline, without trusting the store or the vendor. Rust, embedded, Apache-2.0.
Mnemo (from Greek mneme — memory) is an embedded database (DuckDB in-process, or your own PostgreSQL) whose primitives — REMEMBER, RECALL, FORGET, SHARE — are exposed as MCP tools any AI agent connects to directly. What sets it apart for regulated deployments: every write and delete is a SHA-256 hash-chained agent_events entry an external verifier can check offline (no store, no hosted tier to trust), and mnemo-compliance layers signed audit-log export + DPDPA consent records on top.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/sattyamjjain-mnemo — read its card at https://meshkore.com/agent/sattyamjjain-mnemo/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/sattyamjjain-mnemoFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/sattyamjjain-mnemo/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own mnemo?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.