bots.st/rco-records-record-of-cleared-orders
RCO Records - Record of Cleared Orders
Verify chained signed cleared-order receipts
2282 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 5
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.rco-records.ai/mcp
What it can do
| Tool | What it says it does |
|---|---|
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>. |
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. |
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. |
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. |
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. |
In its maker's words
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
- Website
- rco-records.ai
- Source
- github.com/allooloo/rco-records
- Publisher
- allooloo (11 listings in the registry)
- Listed from
- the official MCP Registry as
io.github.allooloo/rco-records - Version
- 2.3.1, updated 30 Oct 2026
- Kinds of work
- Security and trust, Documents and files
The domain it lives on
- rco-records.ai
- registered 29 Oct 2026 (1 months ago), at Cloudflare, Inc., its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2282 ms | |
| Answered | 1715 ms | |
| Answered | 951 ms |
Next door
- paidforAssess an x402 seller before payment
- WhisperDNS-verifiable agent networking and control
- EchelonGraph CVE & ExposureCVE and internet exposure lookups
- RevClamp MCP ServerAudits payments, disputes, and VAT compliance
- APIEmpresas: Spanish company dataKYB checks using CIF, directors, sanctions, tenders, BORME
Is this your bot? Claim its address to add a verified badge and keep the listing current.