mcpField
R
RCO-A2A - Regulatory Compliance Objects

RCO-A2A - Regulatory Compliance Objects

Remote
rco-a2a.aiLegal & Government0Updated 4d ago

About RCO-A2A - Regulatory Compliance Objects

RCO-A2A is an MCP server for publishing and retrieving signed records of cleared decisions. It serves compliance teams, regulators, counterparties, and licensed participants who need machine-verifiable decision receipts.

Key features

  1. 01Retrieve a receipt by decision ID
  2. 02Write receipts from authorised issuers
  3. 03Verify detached JWS signatures
  4. 04Record receipt hashes in a ledger
  5. 05List daily receipts and counts

Use cases

  1. 01Audit a cleared decision
  2. 02Provide a receipt to a regulator
  3. 03Check an issuer’s signed decision
  4. 04Review receipts lodged on a UTC day

MCP support

The MCP server exposes `get_receipt` for readers and `write_receipt` for authorised writers. Reads need no account; writing requires an authorised door or a firm's agent using the write path.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.rco-a2a.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

2
ParameterTypeRequiredDescription
decision_idstringYes

Details

From the project README

RCO-A2A

rco-a2a.ai — RCO, the Record of Cleared Orders: the signed receipt of one cleared decision, read by decision id. mcp.rco-a2a.ai

Owner of record: Agentic KG Holdings (the Agentic Private Office, github.com/Agentic-Private-Office), from 2026-10-23. The standard is MIT-licensed and implemented by both companies' doors (GreenCore Solutions Corp. and Allooloo Technologies Corp.), and by any licensed firm's agent with a write key. Reads are free; write keys are issued by the office at no charge to implementers.

RCO is the Record of Cleared Orders: a signed, machine-verifiable record of one cleared decision. When an agent's door clears a decision — an issuer resolved, a product cleared under a rule, a signal returned — it leaves one receipt. The receipt is the thing a compliance officer is asked for, and the thing a licensed participant's agent must be able to produce. The standard's page is https://rco-10060.org/.

The earlier reading of RCO (a "regulatory compliance object", a product's compliance state per jurisdiction) is retired. Its five v1 tools are not on the wire; its schemas stay under schema/v1.2 … v1.4 as history.

Canonical endpoint: https://mcp.rco-a2a.ai/mcp (streamable-http, JSON-RPC 2.0, typed errors).

The receipt

FieldWhat it holds
decision_idthe id the decision was given by the door that made it
object identifierwhat was cleared: a GTIN, an ISIN, a product id — the identifier says what kind of order it was
actor_classfor which actor class (never a person)
rule object and versionunder which rule the decision was made
records readwhich records were read, each with its signature (kid)
signalACM-200 · ACM-403 · ACM-404 · ACM-451 (https://acm-68000.org/)
timewhen
issuing doorwhich door issued it
signaturethe issuing door's detached JWS, verifiable against its published keyring
ledgerthe Azure Confidential Ledger (gsc-rco-ledger) transaction id under which the receipt's hash was written

One schema for every object type. No caller data, no personal data, no amounts.

Tools

ToolWhoWhat it does
get_receipt(decision_id)anyone, no accountReturn the signed receipt of one cleared decision.
write_receipt(receipt)authorised doors (a key issued by the office), or a firm's own agent paying per receipt under x402 (no key: the door answers 402 with the offer)Write a receipt: the door verifies the issuer's signature against its keyring, writes the hash to the ledger and keeps the receipt. Idempotent on decision_id.

The same receipt is a page at https://rco-a2a.ai/receipts/{decision_id} and JSON at https://rco-a2a.ai/receipts/{decision_id}.json.

Writers and readers

  • Writers: the hub gates of A2A Grocery, A2A Cosmetics and A2A Peptides; Allooloo's resolver (getissuer) and market nodes; any licensed firm's own agent through the write path with a key.
  • Readers: anyone — the firm's audit function, its regulator, its counterparty.

Verify a receipt

  1. Signature: take kid from the signature's protected header and fetch that key from the issuing door's keyring (named in the receipt); verify the detached JWS over the canonical JSON of the receipt (keys sorted, compact, UTF-8) without signature, signature_check, ledger, receipt_url, page, writer and x402_settlement (the last two are the door's labels, added after the check). Hub receipts: without hub_signature, hub_signature_check, ledger, receipt_url, page.
  2. Ledger: the receipt's ledger.transaction_id on gsc-rco-ledger.confidential-ledger.azure.com; the hash preimage is the RFC 8785 canonical JSON of the receipt without ledger, receipt_url, page and the signature check. Ledger identity certificate: https://identity.confidential-ledger.core.azure.com/ledgerIdentity/gsc-rco-ledger

Verification proves what the issuer stated; it does not make the operator a regulator.

The day's set

GET https://mcp.rco-a2a.ai/receipts/day/<YYYY-MM-DD>.json — every receipt lodged that UTC day and its ledger receipt; the office copies it nightly to its ark (rco-ark, Object Lock). Counts: GET https://mcp.rco-a2a.ai/receipts/stats.json.

Examples

examples/get_receipt.py reads one live receipt (Python 3 standard library) and prints it:

python examples/get_receipt.py gate_dec1d9aaa478b3ef94e4

The walks of the retired v1 tools are kept as history under examples/v1-retired/; they do not run against the current door.

Doors by what they resolve

GTINs → https://gtinfetch.ai/mcp · listed issuers → https://mcp.getissuer.ai/mcp · receipts → https://mcp.rco-a2a.ai/mcp

Sources on the wire

https://rco-a2a.ai · https://rco-10060.org · https://status.rco-a2a.ai · https://acm-68000.org

Registry listing: io.github.Agentic-Private-Office/rco-a2a. Anthropic connector directory: rco-a2a.


© 2026 Agentic KG Holdings · reference operator · MIT licence. The door runs on GreenCore Solutions Corp. compute; the ledger, keys and door are unchanged by the ownership line.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.