Alethech

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 API Key 社区 / 第三方 ClaudeCursorVS CodeCodex
查看接入方式

可验证的代理记忆——每次记忆提交均经Ed25519签名并哈希链接,采用故障关闭验证(84+次提交,0次无效)。通过TF-IDF实现完全离线召回(运行时零LLM令牌),sha256工件审计封入链中,持久化孤儿提交快照且零秘密泄露,实测42秒灾难恢复演练。包含stdio MCP服务器(pip install...

一句话选型结论

按资料字段整理

Alethech 属于文档知识类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude、Cursor、VS Code 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
npx skills add eddyflores100-lang/alethech --skill alethech --global

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、VS Code,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Alethech当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

12.0 KB
来自项目仓库与上游目录的原文,未做删改

alethech

> Verifiable agent continuity protocol — local-first, zero-LLM, zero-blockchain.
> The art of un-concealing transmission integrity.
>
> Copyright (c) 2026 AliceLabs LLC.

Listed in TeleAI-UAGI/Awesome-Agent-Memory (Emerging projects) after a maintainer audit of the claims against the code.

Now in the official MCP Registry: io.github.eddyflores100-lang/alethech — the read-only alethech-mcp bridge, discoverable by any registry-aware MCP client.

If alethech is useful to you, a ★ star is how other people — and their agents — find it.

From Greek ἀλήθεια (aletheia, "truth as un-concealment") + τέχνη (techne, "art, craft").
The art of revealing that a memory was not modified after being signed.

This is the reference implementation of the protocol specified in docs/implementacion-nucleo-minimo.md (rev 2 + rev 3 identity layer).

what this is

alethech provides cryptographically verifiable, portable memory continuity for AI agents. It signs memory commits with Ed25519, links them in a hash-linked DAG, rotates keys without losing identity, and can seal a verified history into one encrypted .aleth file for transfer between compatible runtimes and devices.

What this repo IS:
- A cryptographic protocol implementation (Ed25519 + SHA-256 + JCS RFC 8785)
- An encrypted portable memory container (.aleth, scrypt + AES-256-GCM)
- A neutral verified adapter view for plugins and chat integrations
- A read-only MCP stdio bridge (python -m alethech.mcp_memory, or alethech-mcp after pip install alethech) exposing verified memory context and verification tools — credentials and paths stay configuration, never tool arguments
- 9 CLI commands (init, commit, evidence, verify, export, import, migrate, key rotate, key revoke)
- A test suite with mutation-guard paths (each guarantee has a test that fails when the check is defeated)
- MIT licensed, published on PyPI as alethech

What this repo is NOT:
- The protocol core is not a hosted retrieval platform; the portable skill adds local encrypted memory workflows and bounded lexical recall
- It is NOT the legacy memex project (Python/ChromaDB memory server)
- It has no Docker, no auto-update, no LLM calls, no required cloud
- It depends only on cryptography and click — no mem0ai, no chromadb, no ollama

The legacy memex codebase (167 commits, AliceLabs Proprietary License) is preserved in a separate repository: eddyflores100-lang/memex-legacy. It is not part of this repo and not installed by pip install alethech.

the property

> This memory set forms part of a cryptographically verifiable history associated with a determined identity, whose commits can be independently verified with respect to their integrity, cryptographic authorship, and provenance relations.
>
> When a reference checkpoint exists, it can additionally be verified that the presented history continues from that checkpoint.

The protocol does NOT prove that the agent's claims are true — only that they were signed by the identity that claims them. The truth being un-concealed is the truth about transmission integrity, not about content.

status

Released version 0.9.5 — portable encrypted memory (.aleth v2 with ALETH002 recovery across Python, TypeScript, and Rust) and chat capture into portable memory are live. CI runs the Python suite on 3.10–3.13 plus cross-language conformance and .aleth interoperability across Python, Rust, and TypeScript. No LLM, no required cloud, no blockchain, no consensus.

install the portable memory skill```bash

npx skills add eddyflores100-lang/alethech --skill alethech --global


Ask your agent to save a checkpoint, resume a project, or carry memory to another
AI/device. First save creates encrypted local memory automatically. No API key,
account, LLM model download, server or MCP configuration is required. Python 3.10+
and a script-capable Agent Skills host are needed; missing protocol dependencies
are installed once in a private environment. Later memory operations run offline.
Optional cloud-folder backup copies ciphertext only and preserves changed remote
revisions. Browser-only chats use the existing extension/offline viewer.

See portable skill setup and limits and the
primary-source alternatives review.

## install```bash
pip install alethech

For development:```bash
git clone https://github.com/eddyflores100-lang/alethech.git
cd alethech
pip install -e ".[dev]"


## usage```bash
alethech init                              # generate identity + genesis commit
alethech commit --content <json-file>      # create signed MemoryCommit
alethech evidence --tool <name>            # create signed EvidenceCommit
  --input <file> --output <file>
alethech verify                            # verify the whole store, offline
alethech export --output <dir>             # portable package
alethech import --input <dir>              # import external memory
alethech key rotate                        # rotate operational key
alethech key revoke --key-id <id>          # revoke a key
alethech migrate --to v0.2                  # migrate identity layer

capture a chat, carry the file

Use the Alethech toolbar icon to capture the loaded conversation, review it, and
create an encrypted .aleth with a new local identity and recovery code. Carry
that file to another device, chat or IDE. The extension imports it and inserts
selected context into an empty chat editor only on request; it never sends.
For any text-capable client, export context.txt. MCP clients can use the local
read-only memory connector. A single offline alethech.html also opens/creates
files without installing an extension or registering an account.

See the complete capture and transfer guide and
IDE/MCP setup. Capture requires only activeTab and
scripting, with no global host or storage permission. Rendered chat capture
cannot retrieve a provider's hidden memories or unloaded conversation history.

portable encrypted memory (.aleth)

Alethech 0.9 development adds a single encrypted file designed for drag-and-drop transfer:```python
from alethech import Alethech

agent = Alethech.initialize("./working-store")
agent.commit({"fact": "portable memory"})
agent.seal("memory.aleth", "your-passphrase")

Plugin-style path: dropped file -> unlock -> verify -> neutral context

context = Alethech.drop_context("memory.aleth", "your-passphrase")


The `.aleth` container uses scrypt + AES-256-GCM. Its authenticated payload can be opened byte-exactly by the Python, Rust, and TypeScript implementations in CI. The portable file may carry the encrypted operational signing key so history can continue on another device, but it excludes `root.key` and `recovery.key`.

See `docs/ALETH_CONTAINER_SPEC.md` and `docs/ADAPTER_CONTRACT.md`.

## what it does NOT do

- It does NOT prove that the agent's claims are true. Only that they were signed by the identity that claims them.
- It does NOT detect rollback without an external checkpoint.
- The local working store is NOT encrypted at rest; the portable `.aleth` container is encrypted.
- It does NOT delegate permissions between agents.
- It does NOT call any LLM.

## what the name means

**alethech** comes from:

- **aletheia (ἀλήθεια)** — Greek for "truth", more precisely "un-concealment" (Heidegger's reading: truth as the act of revealing what was hidden)
- **techne (τέχνη)** — Greek for "art, craft, technique"

So alethech = "the art of un-concealing". The protocol un-conceals:
- whether a memory was modified after being signed
- who signed it
- what signed timestamp was recorded (NOT physical signing time — only the timestamp recorded in the artifact)
- what its provenance is
- whether the chain of custody is intact

It does NOT un-conceal whether the content is true — that's the agent's responsibility, not the protocol's.

## tests```bash
python -m pytest tests/

The Python test suite covers:
- crypto primitives (Ed25519, SHA-256, base64url, base32)
- JCS canonicalization (RFC 8785) — 56 conformance vectors including:
- integer/float serialization per ECMAScript Number.prototype.toString()
- -0 serializes as "0" (per RFC 8785 erratum, NOT preserved)
- scientific notation format (positive exponents keep '+', negative strip leading zeros)
- decimal vs scientific threshold (1e21 / 1e-6)
- UTF-16 key ordering with surrogate pairs
- string escaping (control chars, non-ASCII preservation)
- NaN/Infinity rejection
- agent_id derivation (cryptographic binding to public_key)
- MemoryCommit signing, tamper detection, wrong-key rejection
- EvidenceCommit signing (supports both legacy and V2 identity)
- all 9 CLI commands (init, commit, evidence, verify, export, import, migrate, key rotate, key revoke)
- checkpoint emission + rollback detection + causal continuity (ancestry check)
- identity_mismatch detection
- export/import roundtrip preservation
- tampered manifest rejection
- key rotation with cutoff_head reachability guarantee
- ancestry_check mutation guard (3 code-level defeats)
- recall-seam defeats (2 data-level mutations: active-keys tampering, cutoff_head mutation)
- root_id binding (RootAuthority ↔ IdentityRecord ↔ ControlEvent)
- checkpoint continuity (checkpoint HEAD must be ancestor of current HEAD)
- IdentityRecordV2 signature verification (against root public key)
- import causal continuity (ancestry check before writing)
- import hardening (symlinks, path traversal, archive bombs, artifact hash verification)

repository structure```

alethech/ # this repo — cryptographic protocol only
├── alethech/ # source: crypto, objects, store, verify, cli, canonical
│ └── integrations/ # langchain + memex hooks
├── alethech-rs/ # Rust SDK (31 tests, cross-validation)
├── alethech-ts/ # TypeScript SDK (15 tests, Web Crypto API)
├── tests/ # Python behavioral, adversarial, mutation and conformance tests
├── conformance/ # 15 adversarial conformance vectors
├── docs/ # protocol specification
├── examples/ # basic_usage.py + memory_writeback.sh (ops pattern)
├── INTEGRATION.md # how to integrate with memex via MemexAlethechHook
├── INTEGRATION-VIGIL.md # fail-closed memory verification for watchdogs
├── CHANGELOG.md # version history
├── SECURITY.md # threat model + vulnerability policy
├── CONTRIBUTING.md # dev setup + PR process
├── CODE_OF_CONDUCT.md # Contributor Covenant
├── CITATION.cff # academic citation
├── LICENSE # MIT
├── README.md # this file
└── pyproject.toml # package metadata and dependencies: cryptography + click


## cross-language validation

The protocol is implemented in three independent languages:

| Language | Tests | Dependencies |
|---|---|---|
| Python | CI suite | cryptography + click |
| Rust | 31 | ed25519-dalek, sha2, serde |
| TypeScript | 15 | 0 (Web Crypto API only) |

All three use the same NIST SHA-256 test vectors, RFC 4648 base32 vectors, and RFC 8785 JCS conformance vectors. The cross-language claim is backed by an executable harness:```bash
python conformance/cross_language_check.py

This runs all three implementations against the same shared fixtures in conformance/ and asserts byte-exact agreement on canonical bytes for accepted fixtures. The default run is fail-closed: exit 0 = all three ran and agree, 1 = disagreement, 2 = an implementation/runtime is unavailable. CI builds the Rust helper and executes the three-runtime harness. See conformance/CROSS_LANGUAGE.md for the contract and how to add a 4th implementation.

license

MIT.

related repositories

  • eddyflores100-lang/memex-legacy — Legacy Memex codebase (167 commits, AliceLabs Proprietary License). Python/ChromaDB memory system with MCP integration. Preserved for historical reference. NOT installed by pip install alethech.

Copyright (c) 2026 AliceLabs LLC. MIT License.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Alethech 怎么安装?

在客户端按下面的安装命令接入:npx skills add eddyflores100-lang/alethech --skill alethech --global。装完在客户端配置里引用同一个包或端点。

Alethech 怎么在 Claude、Cursor、VS Code 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Alethech 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Alethech 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Alethech 支持哪些客户端?

资料标注支持 Claude、Cursor、VS Code、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Alethech 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Alethech 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Alethech 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。