Allooloo Receipts is an MCP server published by io.github.allooloo, hosted at mcp.rco-records.ai. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 5 tools, including verify_receipt, list_receipts, get_statement, issue_auditor_key, write_receipt.
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
14 connections through 5 shared values. Tap any node.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Check any receipt by its id: the hash, the signature and its place in the chain. Public, no key needed.
| Parameter | Type | Description |
|---|---|---|
| id * | string | rco:… or dec_… |
{
"name": "verify_receipt",
"description": "Check any receipt by its id: the hash, the signature and its place in the chain. Public, no key needed.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "rco:… or dec_…"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}The audit trail of a firm's own AI agents: every cleared read, in order, under the firm's key.
| Parameter | Type | Description |
|---|---|---|
| to | string | |
| from | string | |
| limit | integer | |
| to_seq | integer | |
| from_seq | integer | |
| after_seq | integer |
{
"name": "list_receipts",
"description": "The audit trail of a firm's own AI agents: every cleared read, in order, under the firm's key.",
"inputSchema": {
"type": "object",
"properties": {
"to": {
"type": "string"
},
"from": {
"type": "string"
},
"limit": {
"type": "integer"
},
"to_seq": {
"type": "integer"
},
"from_seq": {
"type": "integer"
},
"after_seq": {
"type": "integer"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}A signed statement of a firm's receipts for a period, for books and records and for its auditor.
| Parameter | Type | Description |
|---|---|---|
| to | string | |
| from | string | |
| month | string |
{
"name": "get_statement",
"description": "A signed statement of a firm's receipts for a period, for books and records and for its auditor.",
"inputSchema": {
"type": "object",
"properties": {
"to": {
"type": "string"
},
"from": {
"type": "string"
},
"month": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}A firm gives its auditor a key to read and verify the firm's receipts independently.
| Parameter | Type | Description |
|---|---|---|
| name | string |
{
"name": "issue_auditor_key",
"description": "A firm gives its auditor a key to read and verify the firm's receipts independently.",
"inputSchema": {
"type": "object",
"properties": {
"name": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}Called by Allooloo's own MCPs when a read is cleared. One receipt per cleared read.
| Parameter | Type | Description |
|---|---|---|
| caller | string | who asked, when the gate knows it: x402:<wallet address>; stored only as its sha256 |
| market | string | ISO country or exchange code of the read |
| subject * | string | what was read: the identifier (an ISIN, LEI, GTIN, ticker, record id …) |
| caller_key | string | the customer key the reader presented to the gate (RCO-Key); the door checks it and stores sha256("key:" + key id) as caller |
| cleared_at | string | RFC 3339 UTC; stored to the second; the door's clock when absent |
| answer_hash | string | sha256:<hex> of the canonical answer bytes the agent received |
| rule_version * | string | the rule set and version the gate cleared under |
| subject_type * | string | isin | lei | gtin | ticker | cmr | fo-record | … (open list) |
RCO-10060 defines a signed receipt for a cleared read of a listed issuer's record. The receipt identifies the subject, the jurisdiction, the clearance rule, the stated time of the read and the hash of the signed answer supplied, and links that event into a verifiable receipt chain. The RCO MCP signs receipts under its own key; the producing node separately signs its content under the record key. A consumer verifies the receipt, matches the answer hash and verifies the record, and so holds attributable evidence of both the content and the read. RCO preserves the record of the read without holding the content or judging its truth. Receipt v1: {v, id, seq, writer, caller, subject, subject_type, market, rule_version, cleared_at, answer_hash, prev_hash, hash, sig, kid}. Tools: write_receipt (writer credential), verify_receipt (public), list_receipts, get_statement and issue_auditor_key (the firm's own key). Errors are typed. Nothing is answered from memory.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
{
"name": "write_receipt",
"description": "Called by Allooloo's own MCPs when a read is cleared. One receipt per cleared read.",
"inputSchema": {
"type": "object",
"required": [
"subject",
"subject_type",
"rule_version"
],
"properties": {
"caller": {
"type": "string",
"description": "who asked, when the gate knows it: x402:<wallet address>; stored only as its sha256"
},
"market": {
"type": "string",
"description": "ISO country or exchange code of the read"
},
"subject": {
"type": "string",
"description": "what was read: the identifier (an ISIN, LEI, GTIN, ticker, record id …)"
},
"caller_key": {
"type": "string",
"description": "the customer key the reader presented to the gate (RCO-Key); the door checks it and stores sha256(\"key:\" + key id) as caller"
},
"cleared_at": {
"type": "string",
"description": "RFC 3339 UTC; stored to the second; the door's clock when absent"
},
"answer_hash": {
"type": "string",
"description": "sha256:<hex> of the canonical answer bytes the agent received"
},
"rule_version": {
"type": "string",
"description": "the rule set and version the gate cleared under"
},
"subject_type": {
"type": "string",
"description": "isin | lei | gtin | ticker | cmr | fo-record | … (open list)"
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}