RCO Records - Record of Cleared Orders
Server Details
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- allooloo/rco-records
- GitHub Stars
- 0
- Server Listing
- RCO Records
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: aggregated signed statements, individual receipt listing, public receipt verification, receipt writing, and auditor key issuance. The boundaries between get_statement and list_receipts are made explicit by the descriptions (signed aggregate vs. raw receipt rows), so an agent can confidently select the right tool.
All tool names follow a consistent snake_case verb_noun pattern: get_statement, issue_auditor_key, list_receipts, verify_receipt, write_receipt. There are no naming style deviations or ambiguous shorthand.
Five tools are well-scoped for a record-of-cleared-orders service: read side (statements, receipts), write side (receipts), verification, and delegated auditor access. Each tool earns its place without bloat.
The surface covers the core lifecycle: writing receipts, listing one's own receipts, obtaining signed statements, public verification, and issuing auditor sub-keys. Minor gaps exist around key revocation/rotation and perhaps richer administrative operations, but core agent workflows are well covered.
Available Tools
5 toolsget_statementAInspect
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 .
Inputs: to, from, month.
issue_auditor_keyAInspect
Issue a read-only sub-key on your own slice for your auditor (list_receipts and get_statement only). Authorization: Bearer . The key value is returned once.
Inputs: name.
list_receiptsARead-onlyIdempotentInspect
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 . Refuses without a key.
Inputs: to, from, limit, to_seq, +2 more.
verify_receiptARead-onlyIdempotentInspect
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.
Inputs: id (required).
write_receiptAIdempotentInspect
Write one v1 receipt for a read a gate has cleared. Authenticated: Authorization: Bearer . Idempotent on (writer, subject, subject_type, market, rule_version, cleared_at, answer_hash). Returns the receipt.
Inputs: subject (required), rule_version (required), subject_type (required), caller, +4 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Signed, append-only receipts of an AI agent's decisions and outcomes, with public proof links.
Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable.
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
Market evidence with receipts: every claim resolves to a real stored record you can fetch back.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables verifying signed provenance receipts by ID or full receipt object and listing an agent's receipt hash-chain newest first for auditing.MIT
- FlicenseNot gradedqualityDmaintenanceCryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.-
- AlicenseAqualityDmaintenanceEvery agent action is recorded in a SHA-256 hash chain. Prove to clients that your agent did what it said it did. Record, query, verify, and export agent activity.337 npm3MIT

emilia-mcp-serverofficial
AlicenseAqualityAmaintenanceThe accountability layer for AI agents — a named human's signed yes before an agent does anything irreversible (payment, record change, deploy), then an offline-verifiable Trust Receipt. Apache-2.0, formally verified.3550Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.