
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 分