RCO Records - Record of Cleared Orders
RemoteAbout RCO Records - Record of Cleared Orders
RCO Records provides signed receipts for reads made by the Allooloo record for regulated agents. Each receipt is linked to the previous one and can be verified against a published key.
Key features
- 01Write signed receipts for cleared reads
- 02Chain receipts to preceding records
- 03Verify receipts using published keys
- 04Reference verification SDKs in TypeScript, Python, and Go
Use cases
- 01Record evidence behind an agent response
- 02Verify a receipt independently by ID
- 03Check receipt signatures and chains
MCP support
Its streamable HTTP MCP endpoint provides `write_receipt` for bearer-token-authenticated writers and public `verify_receipt`.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.rco-records.ai/mcpclaude mcp add --transport http allooloo-rco-records https://mcp.rco-records.ai/mcp{"mcpServers":{"allooloo-rco-records":{"type":"http","url":"https://mcp.rco-records.ai/mcp"}}}Open in Cursor{"servers":{"allooloo-rco-records":{"type":"http","url":"https://mcp.rco-records.ai/mcp"}}}Open in VS Code{"mcpServers":{"allooloo-rco-records":{"type":"http","url":"https://mcp.rco-records.ai/mcp"}}}{"mcpServers":{"allooloo-rco-records":{"serverUrl":"https://mcp.rco-records.ai/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMERCO 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.
- Page, spec, verify: https://rco-records.ai/
- Door (MCP, streamable HTTP): https://mcp.rco-records.ai/mcp —
write_receipt(bearer token per writer),verify_receipt(public) - Keyring: https://rco-records.ai/.well-known/jwks.json
- Verify URL:
https://rco-records.ai/receipts/{id}
Operator: Allooloo Technologies Corp. — https://allooloo.ai
What is in this repository
| Path | What |
|---|---|
SPEC.md | Receipt v1 — the frozen spec — and the v0 history format |
sdk/typescript/verify.ts | reference verify(), verifyChain(), carry() — WebCrypto only |
sdk/python/rco_verify.py | reference verify(), verify_chain() — needs cryptography |
sdk/go/verify.go | reference 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
node sdk/typescript/cli.ts rco:4xvpzgxxmno5bfxxmv5h
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.