Skip to content

RCO-A2A - Regulatory Compliance Objects

by greencore-solutions · remote · no sign-in to list tools · v1.0.2 · published by GitHub user greencore-solutions

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

Changes · 1
CompareRegistry entry

2 tools: 1 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 1Claude Code: ask
  • write_receiptHubs only (x-hub-key): lodge one receipt for a gate decision — the hash on the Confidential Ledger, the receipt kept and served by decision_id.No findings

    Why it is in this group

    • The name "write_receipt" says "write": a word for a change.
    Description, as the server wrote it
    Hubs only (x-hub-key): lodge one receipt for a gate decision — the hash on the Confidential Ledger, the receipt kept and served by decision_id. Idempotent on decision_id.

    Annotations the server declares

    • title: Write receipt (hubs)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Claude Code: allow
  • get_receiptThe signed receipt of one gate decision on a GSC hub, by decision_id: what was cleared, for whom, under which rule, when — with the hub signature and the ledger transaction id.No findings

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    The signed receipt of one gate decision on a GSC hub, by decision_id: what was cleared, for whom, under which rule, when — with the hub signature and the ledger transaction id. No caller data, no PII, no amounts.

    Annotations the server declares

    • title: Get receipt
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rco-a2a__get_receipt"
    ],
    "ask": [
      "mcp__rco-a2a__write_receipt"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as rco-a2a. Review it before you use it.