RCO Records - Record of Cleared Orders

io.github.allooloo/rco-recordsVersion 2.6.6

The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.

Status

Responds150 msNov 14, 2026, 14:44 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:44 UTC
Latency: 150 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.rco-records.ai/mcpResponds150 msNov 14, 2026, 14:44 UTC

No sign-in

Claude Code

claude mcp add --transport http rco-records https://mcp.rco-records.ai/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: rco-records
Remote MCP server URL: https://mcp.rco-records.ai/mcp

Cursor

{
  "mcpServers": {
    "rco-records": {
      "url": "https://mcp.rco-records.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"rco-records","type":"http","url":"https://mcp.rco-records.ai/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

5 tools

Tools of RCO Records - Record of Cleared Orders
	Description		Read-only	Idempotent	Open world
`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>.	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>.	No	No	No	No
`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.	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.	No	No	No	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	No	Yes	No

Details

Registry status: Active
Published: Nov 13, 2026
Updated: Nov 13, 2026
Website: https://rco-records.ai/⁠ (opens in a new tab)
Repository: https://github.com/allooloo/rco-records⁠ (opens in a new tab)
Categories (suggested): Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing