What does a memory substrate need to expose to be portable across agent runtimes?

The Model Context Protocol standardises tool discovery but says little about state, identity, or trust. A memory server is a good stress test of what the protocol leaves unspecified.

An explicit memory contract can preserve semantics across clients, provided identity and scope are enforced outside tool discovery.

• MCP server exposing MemKit read/write operations
• Scoped access per client with provenance preserved across runtimes
• Explicit handling of context-budget limits at the protocol boundary

Evaluation in progress: portability checks across multiple MCP clients.

• No identity story beyond what the host runtime provides

Working MCP server used to drive MemKit from multiple agent runtimes.

• Per-client scoping tied to Agent Guard grants

• Protocol-level identity and audit for tool servers