RCO Records - Record of Cleared Orders

io.github.allooloo由 GitHub 帳號 allooloo 發布v2.3.1更新於 Nov 7, 2026

The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.

已驗證Streamable HTTP可網頁執行資料庫金融安全與監控

概覽

AI 產生的概覽

遠端 MCP 服務,為受監管記錄中已放行的讀取寫入、列出並驗證具簽章的鏈式回執,並提供簽章對帳單與稽核金鑰。

可以做什麼
  • 為已通過閘門放行的讀取寫入一筆 v1 簽章回執,依寫入方、主體、市場、規則版本、放行時間與答案雜湊維持冪等
  • 依 id 驗證回執,回傳雜湊、簽章及可驗證的公開金鑰
  • 依序號區間或日期區間列出自己的回執,單次最多 500 筆
  • 取得按月或依日期區間的簽章對帳單,含筆數、首末序號、切片摘要與鏈尖
  • 簽發唯讀稽核子金鑰,僅能用於列出回執與取得對帳單
適用情境
適合受監管的代理或機構需要為助理所依據的內容留下可歸責證據的情境:每次已放行讀取都有可供第三方與外部稽核方驗證的紀錄,且無須交出原始內容。
執行需求
遠端 streamable HTTP 端點,不需在本機安裝套件。write_receipt 需要寫入方 bearer 權杖,list_receipts、get_statement 與 issue_auditor_key 需要客戶金鑰,並需網路連線。verify_receipt 為公開介面,無須憑證。
安裝前請注意
寫入、列出與取得對帳單都需要 bearer 憑證;簽發的稽核金鑰值只回傳一次,請妥善保存。回執會寫入由 Allooloo 營運的鏈式紀錄,事後無法修改。此服務只記錄讀取事件與答案雜湊,不保存內容本身。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 RCO Records - Record of Cleared Orders,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.allooloo%2Frco-records/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "rco-records-record-of-cleared-orders": {
      "type": "http",
      "url": "https://mcp.rco-records.ai/mcp"
    }
  }
}

README

RCO Records — Record of Cleared Orders

RCO — the record of what the agent relied on. Every read, receipted.

Every answer the Allooloo record gives a regulated agent is receipted: one signed receipt per cleared read, chained to the one before, verifiable by anyone against a published key. The receipt is the agent's alibi.

Standard held by Allooloo Technologies Corp. · Open standard, MIT licence. — https://allooloo.ai

What is in this repository

PathWhat
SPEC.mdReceipt v1 — the frozen spec — and the v0 history format
sdk/typescript/verify.tsreference verify(), verifyChain(), carry() — WebCrypto only
sdk/python/rco_verify.pyreference verify(), verify_chain() — needs cryptography
sdk/go/verify.goreference Verify() — standard library only
worker/, public/, wrangler.toml, schema.sql, rails/the door as it runs (Cloudflare Worker + D1)

The spec and the reference verify() ship under MIT (LICENSE). Nothing else is licensed: the chain, the keys, the door and the Register are operated by Allooloo, not licensed.

Verify a receipt

bash
node sdk/typescript/cli.ts rco:4xvpzgxxmno5bfxxmv5h
bash
python sdk/python/rco_verify.py rco:4xvpzgxxmno5bfxxmv5h

verify(receipt, jwks) is a pure function: recompute hash (and id for v1), check sig against kid. A receipt verifies forever without asking Allooloo anything.

來源:README.md,提交 22ad261

工具

5

write_receipt

Write one v1 receipt for a read a gate has cleared. Authenticated: Authorization: Bearer <writer token>. Idempotent on (writer, subject, subject_type, market, rule_version, cleared_at, answer_hash). Returns the receipt.

輸入參數callermarketsubject必填caller_keycleared_atanswer_hashrule_version必填subject_type必填

verify_receipt

Return one receipt by id (rco:… for v1, dec_… for v0) with the verification result (hash, id, signature) and the public key (JWK) that checks it. Public.

輸入參數id必填

list_receipts

Your own receipts only — the rows whose caller is your customer key — by seq range (from_seq, to_seq, after_seq) or date range (from, to: YYYY-MM-DD, to inclusive), limit ≤ 500. Authorization: Bearer <customer key>. Refuses without a key.

輸入參數tofromlimitto_seqfrom_seqafter_seq

get_statement

A signed statement of your slice for a month (month: YYYY-MM) or a date range (from, to: YYYY-MM-DD, to exclusive): count, first and last seq, slice digest, the chain tip at issue, Ed25519 signature by Allooloo. Authorization: Bearer <customer key>.

輸入參數tofrommonth

issue_auditor_key

Issue a read-only sub-key on your own slice for your auditor (list_receipts and get_statement only). Authorization: Bearer <customer key>. The key value is returned once.

輸入參數name

版本歷史

2
  1. v2.3.1最新Oct 31, 2026
  2. v2.3.0Oct 30, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分