RCO-A2A - Regulatory Compliance Objects

Last 30 days

Status and outage history · Atom feed

Uptime

100%

Response time

306 ms typical, 418 ms slowest 5%

Last check

21 min ago

Next check

in 5 h

How to call it

Add it to any MCP client that supports remote servers.

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

5 tools

• resolve_compliance

  The light: can this product be sold in this market. Returns the current signed Regulatory Compliance Object for object_id × market — state green (cleared), yellow (cleared with a condition) or red (not cleared) — or state none when no record exists (nothing is signed at request t

• get_record

  Any record by record_id, including superseded history (August ids stay valid and byte-identical; VECTOR-era ids carry the market code).

• list_rule_sets

  The versioned, hashed, signed rule set for a market of record (the markets the GSC hubs trade in), or apex.

• list_issuers

  Return the signed consortium issuer registry document, verbatim as published at consortium-10060.org/issuers.json.

• publish_record

  Publish a signed Regulatory Compliance Object to the partner rail (rco-a2a-cpg.ai). The ONLY write path in the suite, and it accepts only what already verifies: the record must be schema-valid RCO v1.3, its issuer must be a cpg-rail issuer active in the signed consortium registry

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks