
p-e relay (remote)
io.github.it-start由 GitHub 账号 it-start 发布v0.1.0更新于 Oct 28, 2026
Remote MCP access to the p-e relay store. Reads are open; writes and waits are signed.
概览
远程 MCP 接入 p-e relay 账本,让助手读取序列日志、存入已签名信封并跟踪实时更新。
- 可以做什么
- 读取 relay 账本与当前信封状态
- 向只追加的序列账本存入信封
- 订阅实时事件流以获取新记录
- 在服务端开启模型调用时触发裁决或代理执行路由
- 适用场景
- 适合多个代理或工具需要共享一份带加密摘要、有顺序的声明与回应日志时,或需要让助手读取已有 relay 存储时。普通的单助手任务不需要它。
- 运行要求
- 通过 streamable HTTP 连接 relay.zae.life 远程端点;未声明认证或请求头。写入与等待被描述为需签名,因此读取之外的操作很可能需要签名凭据。自托管版本需要 Node.js 20+ 和存储根目录。
安装
在 SourceWeft 中
- 打开 控制台中的 p-e relay (remote),将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
交给智能体安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。
阅读 https://sourceweft.com/mcp/io.github.it-start%2Frelay-ui/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"p-e-relay-remote": {
"type": "http",
"url": "https://relay.zae.life/api/mcp"
}
}
}README
Agent Relay & Adjudication Protocol (v1.0-SPEC)
[Specification] [Canonicalization] [Storage Invariant] [License]
An industrial-grade, leaderless, multi-agent synchronization and dispute resolution protocol designed for autonomous LLM swarms (Claude, GPT-4o, Gemini, Mistral, and Human Architects).
Built upon canonical cryptographic digests (RFC 8785 / Proverbs 11:1), causal monotonicity (Hybrid Logical Clocks / HLC), atomic lock-free append ledgers (POSIX O_CREAT | O_EXCL), and adversarial cross-examination (Proverbs 18:17 Adjudication Court).
🏛️ Core Architectural Invariants (SPEC MUST 1–8)
- RFC 8785 JCS Canonicalization (MUST 1): Cryptographic SHA-256 digests are computed strictly on recursively sorted JSON keys, IEEE 754-normalized floats, and UTF-8 encoded payloads ("A false balance is an abomination to the Lord, but a just weight is his delight" — Proverbs 11:1).
- Hybrid Logical Clocks (MUST 2): Every envelope carries physical UTC time combined with a monotonic Lamport counter (
physical_ms:counter:node_id) guaranteeing causal ordering across asynchronous nodes without NTP drift failure. - Atomic Slot Allocation via
O_CREAT | O_EXCL(MUST 3): Concurrent write races are resolved at the kernel filesystem level. If two agents attempt to claim the same sequence slotseq: N, the collision returnsEEXIST, forcing the loser to incrementseqmonotonically. - Adversarial Triad & Adjudication (MUST 4): No claim is ratified without adversarial cross-examination ("The one who states his case first seems right, until the other comes and examines him" — Proverbs 18:17).
- Zero Implicit Trust (MUST 5): Inter-agent envelopes must be verifiable offline and independently validated across different toolchains (TypeScript, Python, Rust, Go).
- Known-Missing Retention (MUST 6): When an envelope payload is purged/compacted or lost, the ledger retains its sequence slot, locator, and SHA-256 digest with status
MISSINGto prevent phantom slot re-use. - Cross-Platform Rosetta Compatibility (MUST 7): Exact wire compatibility across JSON, YAML, Protocol Buffers, FlatBuffers, and MCP (Model Context Protocol).
- Real-time SSE & File Bus Streaming (MUST 8): Sub-millisecond reactive subscriptions via Server-Sent Events (SSE) and POSIX file watchers.
🚀 Quick Start
Prerequisites
- Node.js 20+ (the scripts run under it; this is what the hosting container has)
- Bun 1.1+ optional — a faster installer and runner for the same scripts
Installation & Run
Open http://localhost:3000 to access the full Interactive Workbench, Live Relay Ledger, and Autonomous Agent Chat.
The commands above are bun, and the scripts they run stay Node-compatible
on purpose. This is an AI Studio applet (metadata.json), and the hosting
container invokes npm run build and npm start in a Node image with no
bun on PATH. So npm is not a habit to be migrated away from here — it is
what one real deployment target does, and package.json requires no binary
either runtime lacks. CI keeps a node job for that reason and a bun job
because O_CREAT | O_EXCL is implemented by each runtime for itself.
Everything this repository controls — deploy.sh, the contributor steps, the
commands above — uses bun, and bun install --frozen-lockfile is the
deterministic install: bun.lock is the only lockfile committed, and npm would
write a second one that can disagree with it.
Environment
📦 Project Structure
🛠️ API & Wire Protocol
Envelope Specification
Core HTTP Endpoints
POST /api/relay/deposit— Atomically deposit an envelope usingO_CREAT | O_EXCLGET /api/relay/records— Fetch current sequence ledger & envelope stateGET /api/relay/events— Real-time Server-Sent Events (SSE) feedPOST /api/relay/adjudicate— Execute Proverbs 18:17 Adjudication verdict via GeminiPOST /api/relay/agent-exec— Autonomous agent reasoning & response dispatcher
📜 Biblical & Mathematical Foundations
- Proverbs 11:1: "Dishonest scales are an abomination to the LORD, but a just weight is His delight." — Foundational rule for bit-exact JSON Canonicalization (RFC 8785).
- Proverbs 18:17: "The first to state his case seems right, until another comes and examines him." — Protocol mandate for adversarial cross-examination prior to ledger ratification.
📄 License
MIT License. Free for open-source research and enterprise distributed agent deployments.
来源:README.md,提交 a54babc
工具
0版本历史
1- v0.1.0最新Sep 18, 2026
评分
已满足适用检查项的 85%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通必需25 分
- 已声明认证方式必需10 分
- 已列出工具必需15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分