Alethech

What alethech does

The alethech MCP server provides a read-only MCP view of memory managed by the alethech protocol. It is designed for agents that need to inspect memory context together with evidence that the history has not been modified after signing. The underlying protocol uses Ed25519 signatures, SHA-256 hashing, JSON Canonicalization Scheme (JCS), and a hash-linked directed acyclic graph of commits.

Verification establishes integrity, cryptographic authorship, recorded timestamps, provenance relationships, and continuity from a reference checkpoint when one exists. It does not establish that the contents of a memory are factually true. The bridge also does not retrieve hidden provider memories or unloaded conversation history.

This places the alethech MCP server in the Knowledge & Memory category, but it should not be treated as a general-purpose memory store or semantic retrieval system. It supplies a verified adapter view of an existing local alethech history.

How it works

The bridge runs over MCP stdio and reads the configured local alethech state. Its exposed capabilities cover verified memory context and verification operations; the server is read-only, so agents cannot use it to create commits, change keys, import data, or mutate the working store through MCP.

Alethech histories can include signed memory and evidence commits connected through a hash-linked structure. The protocol supports identity key rotation without abandoning the identity, while revocation and other lifecycle operations are handled outside the read-only bridge through the command-line interface. A history can also be sealed into an encrypted .aleth container using scrypt and AES-256-GCM, although the MCP connector itself is described as a local read-only memory connector.

The implementation makes no LLM calls and does not require a cloud service or blockchain. Verification can be performed offline. The repository reports Python support from 3.10 through 3.13 and cross-language interoperability for portable containers across Python, Rust, and TypeScript.

Setup and configuration

Install the published package with:

pip install alethech

After installation, the stdio entry point is alethech-mcp. The module form is also available:

python -m alethech.mcp_memory

Configure the MCP client to launch that command and provide the local paths and credentials through server configuration. The README specifically states that credentials and paths remain configuration rather than MCP tool arguments. No required environment variable names are documented in the supplied material.

The package also provides CLI operations for initializing a store, committing content, creating evidence, verifying a store, exporting and importing memory, migrating identity data, and rotating or revoking keys. Those commands are separate from the MCP bridge and are useful when preparing or maintaining the memory that the bridge reads.

Limitations and notes

The alethech MCP server is read-only and does not replace the alethech CLI or protocol implementation. The local working store is not encrypted at rest; encryption applies to the portable .aleth container. The portable file excludes root.key and recovery.key, although it may include the encrypted operational signing key needed to continue a history elsewhere.

Verification cannot detect rollback without an external checkpoint, and signatures prove who signed an artifact rather than whether its claims are true. The project has no required cloud dependency, Docker setup, automatic update mechanism, or LLM integration. It is MIT licensed and published on PyPI as alethech.