# RCO-A2A - Regulatory Compliance Objects

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

- name: io.github.greencore-solutions/rco-a2a
- version: 1.0.2
- connection class: R0 (autonomous)
- trust: 94/100
- quality: 75/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.greencore-solutions%2Frco-a2a
- tools: https://api.protogrid.dev/v1/servers/io.github.greencore-solutions%2Frco-a2a/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 100
- liveness: 100
- freshness: 85
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-33d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 75/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 511 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 11 tool changes in 30 days
- fail `stability.rug_pull`: 3 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 511 tokens to load them all
- tool set hash: 99a0f016ab24395167f879629c808ad8
- tools last changed: 2026-10-16T01:04:58.810Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.greencore-solutions/rco-a2a.svg)](https://protogrid.dev/servers/io.github.greencore-solutions/rco-a2a)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-16 `resolve_compliance` removed
  - 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 time). Deterministic. Never narrative.
- 2026-10-16 `publish_record` removed
  - 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, its verification_url must equal that issuer's registry JWKS URL, its detached JWS must verify against that JWKS, and its record_id (and any supersession) must be consistent. GSC never authors a partner record and never holds a partner private key: GSC verifies, receipts to Azure Confidential Ledger, and serves. A submitted record is never modified. Idempotent: republishing a byte-identical record returns the same receipt. Typed errors only.
- 2026-10-16 `list_rule_sets` removed
  - The versioned, hashed, signed rule set for a market of record (the markets the GSC hubs trade in), or apex.
- 2026-10-16 `list_issuers` removed
  - Return the signed consortium issuer registry document, verbatim as published at consortium-10060.org/issuers.json.
- 2026-10-16 `get_record` removed
  - Any record by record_id, including superseded history (August ids stay valid and byte-identical; VECTOR-era ids carry the market code).
- 2026-10-16 `write_receipt` added
  - 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.
- 2026-10-16 `get_receipt` added
  - 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.
- 2026-10-12 `publish_record` changed (inputSchema)
- 2026-10-12 `list_rule_sets` changed (description, inputSchema) **meaning changed**
  - before: List the versioned rule sets in force and formerly in force for a jurisdiction: id, version, hash, effective dates, artifact URL. Never the regulation text.
  - after: The versioned, hashed, signed rule set for a market of record (the markets the GSC hubs trade in), or apex.
- 2026-10-12 `get_record` changed (description, outputSchema) **meaning changed**
  - before: Return any RCO by record_id, including superseded records - the audit trail, retained byte-identical.
  - after: Any record by record_id, including superseded history (August ids stay valid and byte-identical; VECTOR-era ids carry the market code).

Full history: https://api.protogrid.dev/v1/servers/io.github.greencore-solutions%2Frco-a2a/changes

## Remotes

- https://mcp.rco-a2a.ai/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (2)

- `get_receipt`: 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.
- `write_receipt`: 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.
