RCO-A2A is a remote MCP server publishing signed, deterministic product-compliance state per product × jurisdiction, resolved before your agent asks.
Add the server to any MCP client that speaks streamable HTTP. No account, no authentication on reads.
{"mcpServers": {"rco-a2a": {"url": "https://mcp.rco-a2a.ai/mcp"}}}
In Claude: Settings → Connectors → Add custom connector → URL https://mcp.rco-a2a.ai/mcp.
resolve_compliance — the current signed record for a product × jurisdiction (arguments: object_id like gtin:00990832300082, jurisdiction like FR-ECO-10060).
get_record — any record by record_id, including superseded history.
list_rule_sets — the versioned, hashed, signed jurisdiction rule sets.
list_issuers — the signed issuer registry from consortium-10060.org.
publish_record — the controlled issuer write path (consortium-admitted issuers, own ES256 key, per-issuer subscription key at the APIM door; not usable anonymously).
Full typed contract: /schema/v1.4/resolve_compliance.tool.json. Records verify from the issuer's public JWKS; GSC records use the dpuone.ai keyring. Every issued record carries an Azure Confidential Ledger receipt at /ledger/<record_id>.json on its rail.
1. "Resolve the compliance state for GTIN 00990832300082 in FR-ECO-10060 and tell me who issued it." (resolve_compliance)
2. "Show the full record history for that product in Italy, including any superseded records." (get_record)
3. "List the rule sets for the German jurisdiction and give me the version and hash of the current one." (list_rule_sets)
4. "Which issuers are admitted on the partner rail right now, and what is their status?" (list_issuers)
The write path is documented in the publish-record skill and partner onboarding.