RCO-A2A - Regulatory Compliance Objects

io.github.greencore-solutionsPublished by GitHub account greencore-solutionsv1.0.2Updated Nov 2, 2026

Signed, deterministic compliance state per object per jurisdiction, resolved upstream

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for the Record of Cleared Orders: writes signed, hash-chained receipts for cleared agentic orders and verifies them by decision ID.

What you can do
  • Write a receipt for a cleared order, authenticated with a per-writer bearer token, returning a decision ID and idempotent on it
  • Verify a receipt by decision ID, publicly returning the receipt, its chain position, its signature and the key needed to check it
  • Inspect the hash chain: each receipt is hash-chained to the previous one and signed with an Ed25519 office key
  • Read receipts from the earlier ledger era, which carry a different key ID, a null signature and the confidential-ledger transaction holding the original hash
When to use it
Use it when an assistant or agent workflow needs to record that a gate cleared an order and produce a verifiable, tamper-evident receipt, or when someone needs to check an existing receipt and its chain position.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. Writing receipts requires an Authorization bearer writer token, one per writer. Verification is public. Network access to the endpoint and the published key set is needed.
Before you install
The write tool needs a writer token sent as an Authorization bearer header; keep it per writer and out of shared configs. Writing adds append-only records to a shared ledger, so mistakes cannot be edited or deleted. Receipts and verification data are served publicly by decision ID, and the ledger is held and copied to storage by the operating office.

Installation

In SourceWeft

  1. Open RCO-A2A - Regulatory Compliance Objects in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.greencore-solutions%2Frco-a2a/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "rco-a2a-regulatory-compliance-objects": {
      "type": "http",
      "url": "https://mcp.rco-a2a.ai/mcp"
    }
  }
}

README

RCO-A2A — Record of Cleared Orders

RCO is the Record of Cleared Orders. A receipt is written when a gate clears an agentic order:

{decision_id, gtin, market, actor_class, rule_version, cleared_at, writer, prev_hash, hash, sig, kid}

Each receipt is hash-chained to the one before it and signed by the office key. Two tools, nothing else:

  • write_receipt — authenticated (Authorization: Bearer <writer token>, one token per writer), returns decision_id. Idempotent on decision_id.
  • verify_receipt(decision_id) — public, returns the receipt, its chain position, its signature and the key to check it.

Door: https://mcp.rco-a2a.ai/mcp (Model Context Protocol, streamable HTTP, stateless, JSON-RPC 2.0). Page and kit: https://rco-a2a.ai/. Verify URL: https://rco-a2a.ai/receipts/{decision_id}. Ledger held by the Agentic Private Office.

The chain

  • hash = sha256: + hex of SHA-256 over the canonical JSON of {actor_class, cleared_at, decision_id, gtin, market, prev_hash, rule_version, writer} — keys sorted, no whitespace, nulls kept.
  • The first receipt's prev_hash is sha256: + 64 zeros.
  • sig = Ed25519 (EdDSA) over the UTF-8 bytes of the hash string, base64url. kid names the key on https://rco-a2a.ai/.well-known/jwks.json (rco-office-2026-10).
  • Receipts loaded from the ledger era (2026-10-15 → 2026-10-27) carry kid gsc-rco-2026-08, sig null, and the Azure Confidential Ledger transaction that holds their original hash. Fields the ledger never held are null.

Connect

MCP client configuration (any client that speaks streamable HTTP):

json
{ "mcpServers": { "rco-a2a": { "type": "streamable-http", "url": "https://mcp.rco-a2a.ai/mcp" } } }

Verify one receipt from a shell:

bash
curl -s https://mcp.rco-a2a.ai/mcp -H 'content-type: application/json' -H 'accept: application/json' \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"verify_receipt","arguments":{"decision_id":"dec_b73fe75bff87ef889d8ca304"}}}'

or GET https://rco-a2a.ai/receipts/dec_b73fe75bff87ef889d8ca304.

Check a signature (Python):

python
import json, base64, requestsfrom cryptography.hazmat.primitives.asymmetric.ed25519 import Ed25519PublicKeyr = requests.get("https://rco-a2a.ai/receipts/" + DECISION_ID).json()k = next(k for k in requests.get("https://rco-a2a.ai/.well-known/jwks.json").json()["keys"] if k["kid"] == r["receipt"]["kid"])pad = lambda s: s + "=" * (-len(s) % 4)Ed25519PublicKey.from_public_bytes(base64.urlsafe_b64decode(pad(k["x"]))).verify(base64.urlsafe_b64decode(pad(r["receipt"]["sig"])), r["receipt"]["hash"].encode())

Errors

Typed, inside the tool result (isError: true): not_authorised · invalid_receipt · invalid_decision_id · not_found · store_unavailable · store_error · chain_contention.

Source

worker/ — the Cloudflare Worker (index.js routes and kit, mcp.js the two tools, chain.js the record and its chain, export.js the nightly copy to the office's S3 bucket). schema.sql — the D1 table, append-only (triggers refuse UPDATE and DELETE). public/ — the office page and the five record pages. rails/ — the history loader and the D1 rail. No secret is in this repository.

MIT. © 2026 Agentic KG Holdings.

Source: README.md at commit f1d7f04

Tools

0
SourceWeft has not read this server's tools yet.

Version history

3
  1. v1.0.2LatestSep 17, 2026
  2. v1.0.1Sep 17, 2026
  3. v1.0.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts