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 分