
Tremelay
io.github.CharitonMedia由 GitHub 账号 CharitonMedia 发布v1.0.3更新于 Oct 24, 2026
Local MCP broker: agents call credentials through a daemon without seeing secrets.
概览
本地凭据代理:让 AI 代理通过限定范围、会过期的授权使用 API 密钥和 SSH 密钥,而始终看不到密钥本身。
- 可以做什么
- 列出、查看并调用授予某个代理的能力,使其能用已存凭据执行代理式 HTTP 请求
- 通过 ssh-agent 套接字完成 SSH 签名,私钥始终留在守护进程内
- 在命令行管理保险库、凭据、代理与授权,包括签发、轮换和吊销代理令牌
- 查看并校验记录允许与拒绝尝试的哈希链审计日志
- 适用场景
- 当你希望代理用真实凭据调用 API 或通过 SSH 推送,但不想把令牌粘贴进配置文件、环境变量或 MCP 服务器设置,并且想让每个代理只拥有范围窄、可吊销的授权时使用。
- 运行要求
- 作为本地进程运行在用户机器上;清单列出各平台的 MCP Bundle 包,README 说明用固定版本的 Go 工具链安装。需要本地保险库文件、以保险库路径启动的守护进程,以及口令(在终端提示输入,或通过 TREMELAY_PASSPHRASE 提供)。每个代理需要自己的 bearer 令牌文件。无需账号、服务器或网络传输。
安装
在 SourceWeft 中
- 打开 控制台中的 Tremelay,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Tremelay
A local credential broker, so your AI agents can use your credentials without ever seeing them.
You already give agents real authority: read these issues, push this branch, call that API. Today that means pasting a token into a config file, an environment variable, or an MCP server, and hoping nothing logs it, echoes it, or wanders off to the wrong host with it.
Tremelay splits possession of a secret from authority to use it. You keep
credentials in a local encrypted vault. Each agent gets its own identity and its own
narrow, expiring, revocable grants — "GET anything under
https://api.github.com/repos/you/yourrepo with this token", "authenticate to
git.example.com as git with this SSH key". The agent asks Tremelay to perform
the operation; Tremelay performs it with the credential and returns only the result
the grant allows. The agent never receives the secret, there is no getSecret tool
to call, and every attempt — allowed or denied — lands in a hash-chained audit log.
The broker possesses secrets. Agents possess capabilities.
Agents connect over MCP (list_capabilities, describe_capability,
invoke_capability), or over an ssh-agent socket for SSH signing. Everything is
local: one SQLite vault file, one user-only socket or named pipe, no server, no account, no telemetry.
Demo
A real session against a throwaway vault. The secret is the literal string
dummy-demo-secret. Every command except vault create also writes one
vault_unlock id=… result=allowed line to stderr; those are trimmed here,
nothing else is.
Both denials exited non-zero, and no row carries a secret. The passphrase came
from TREMELAY_PASSPHRASE; interactively you get a no-echo prompt instead.
Install
Tremelay needs the pinned Go toolchain (1.26.9, see go.mod); go install
switches to it for you.
From a clone, make build or go build -o tremelay ./cmd/tremelay does the same
thing. Check the build with tremelay version (or tremelay --version).
The v1.0.3 release
carries per-platform archives named tremelay_<version>_<os>_<arch>.tar.gz (or
.zip on Windows). Each archive unpacks to a binary named tremelay
(tremelay.exe on Windows) plus LICENSE, along with a CycloneDX SBOM and a
SHA256SUMS file — a checksum detects a corrupt download, not a substituted
release. It also carries one MCP Bundle per platform,
tremelay-mcp_<version>_<os>_<arch>.mcpb, for clients that install MCP Bundles
(see the generic MCP quickstart).
Signed releases are not in v1. make release-dry builds those artifacts
locally; see ADR 0027. Download the archive
you want and SHA256SUMS into one directory, then check that archive by name:
On macOS, shasum -a 256 -c - in place of sha256sum -c -.
Name the file you downloaded. sha256sum -c --ignore-missing SHA256SUMS over
the whole list exits 0 when your archive is the one that failed to download
and some other listed file is present.
Quickstarts
Copy-paste setup from install to first successful call, one page per client: docs/quickstarts/ (Claude Code, Codex, Hermes, generic MCP).
The shape is the same everywhere. tremelay daemon --vault PATH prompts for
your passphrase at a terminal (non-empty TREMELAY_PASSPHRASE works without a
prompt but is not recommended; see passphrase from the
environment) and then
serves agents on a user-only local socket; tremelay agent create --token-file FILE gives each agent its own bearer
token file, and tremelay agent token issue|rotate|revoke manage it later without
recreating the agent; tremelay mcp --daemon --token-file FILE is the stdio command the
client launches. tremelay lock, the idle timeout, or losing the process
zeroises the key. See the headless daemon guide, or
local stdio MCP for the per-launch pinentry path
instead. For SSH, tremelay ssh-agent publishes an
SSH_AUTH_SOCK that signs with a key that never leaves the daemon.
What it does not do
Read this before you trust it with anything.
- One human. Single user, single vault. No multi-user, no orgs, no shared vaults, no team policy.
- One machine. A user-only Unix socket or Windows named pipe, and stdio;
there is no network or remote MCP transport.
tremelay ssh-agentis Linux and macOS only and fails closed on Windows. - The agent still reads broker responses. An
http_brokergrant returns the status code, an allowlisted set of response headers, and up to 32 KiB of the body with the credential redacted in its common encodings (raw, URL, base64, hex, JSON-escaped). The agent never sees the credential, but it does see the data that credential unlocks — and anything in that body can be prompt injection (H1). A hostile upstream that deliberately re-encodes or splits the credential is not caught; grant only origins you trust with the credential. - No file uploads through the broker. A brokered request with a multipart
body (
multipart/form-data, file uploads) is refused asdenied_malformed. Send JSON or a urlencoded form instead. - An unlocked daemon trusts your uid. While it is unlocked, any code running as you can use your agents' granted capabilities. It still cannot read a credential, change a grant, or learn your passphrase, and everything it does is audited — but that is the boundary.
- No OAuth refresh brokering, no database session brokering, no browser form fill, no TOTP, no provider-assisted rotation. These are in VISION.md and on the roadmap, not in v1.
- No third-party audit. No independent security review and no signed releases yet. The audit chain is tamper-evident to you; nobody else checkpoints it.
credential getprints the raw secret. That is the human control plane, by design — it is not reachable from any agent interface.- Legacy GitHub issue grants block unlock (H2). A vault that still holds a
pre-v1
github_issue_stategrant will not unlock until that grant is revoked with the pre-v1 binary.
Security
- SECURITY_INVARIANTS.md — the rules that outrank convenience.
- THREAT_MODEL.md — who the adversary is, including the agent.
- SECURITY.md — reporting a vulnerability.
Docs
ARCHITECTURE.md · VISION.md · ADRs · vault lifecycle · HTTP broker · SSH signing · measured client integrations · what is in v1 · milestone history
tremelay --help prints the full command list.
Contributing
CONTRIBUTING.md. Apache License 2.0; see LICENSE.
来源:README.md,提交 09d7216
工具
0版本历史
2- v1.0.3最新Oct 16, 2026
- v1.0.2Oct 16, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。