A
licenseA
qualityC
maintenanceProvides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.
4
26 npm
1
MIT
RCO Records
by allooloo
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RCO Recordsverify receipt rco:4xvpzgxxmno5bfxxmv5h"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
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)Verify URL:
https://rco-records.ai/receipts/{id}
Operator: Allooloo Technologies Corp. — https://allooloo.ai
What is in this repository
Path | What |
| Receipt v1 — the frozen spec — and the v0 history format |
| reference |
| reference |
| reference |
| 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.
Related MCP server: APEX PSI MCP Server
Verify a receipt
node sdk/typescript/cli.ts rco:4xvpzgxxmno5bfxxmv5hpython sdk/python/rco_verify.py rco:4xvpzgxxmno5bfxxmv5hverify(receipt, jwks) is a pure function: recompute hash (and id for v1), check sig against kid. A receipt verifies forever without asking Allooloo anything.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
Signed receipt per cleared agentic order, by decision id. Two tools: write_receipt, verify_receipt.
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides cryptographic truth infrastructure for AI agents, enabling them to seal content with SHA-256 and Ed25519, verify receipts, anchor them to Bitcoin via OpenTimestamps, generate citations, and audit chains of receipts.559 npm1MIT
- AlicenseNot gradedqualityBmaintenanceIssue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.0Inno Setup
- AlicenseNot gradedqualityBmaintenanceProvides tools to evaluate an AI agent's step before execution, returning signed ALLOW/DENY receipts, and to verify receipt chain integrity.Apache 2.0