# RCO-A2A - Regulatory Compliance Objects (remote · mcp.rco-a2a.ai)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.rco-a2a.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/greencore-solutions-rco-a2a/mcp.md), [page](https://verifymcp.io/servers/greencore-solutions-rco-a2a/mcp)

## Channel facts

- Endpoint: `https://mcp.rco-a2a.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 481 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RCO-A2A - Regulatory Compliance Objects MCP server?

RCO-A2A - Regulatory Compliance Objects is a hosted endpoint at https://mcp.rco-a2a.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http greencore-solutions-rco-a2a 'https://mcp.rco-a2a.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "greencore-solutions-rco-a2a": {
      "url": "https://mcp.rco-a2a.ai/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.greencore-solutions-rco-a2a]
url = "https://mcp.rco-a2a.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "greencore-solutions-rco-a2a": {
      "type": "remote",
      "url": "https://mcp.rco-a2a.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add greencore-solutions-rco-a2a --url 'https://mcp.rco-a2a.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  greencore-solutions-rco-a2a:
    url: "https://mcp.rco-a2a.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "greencore-solutions-rco-a2a": {
      "Transport": "http",
      "Url": "https://mcp.rco-a2a.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add greencore-solutions-rco-a2a -t streamable-http -u 'https://mcp.rco-a2a.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 78, +1)

- [functional] Server version: 1.0.1 → 1.0.2
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-09-15 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `resolve_compliance` (~99 tokens)

Resolve compliance state

Return the current signed Regulatory Compliance Object for an object in a jurisdiction. Deterministic. Inside the resolved universe (SPEC v1.2 pairs.json + the jurisdiction doors' own objects) an unknown object returns a pre-resolved, signed CPG-404 record; outside it the typed error record_not_found is returned - nothing is signed at request time. Never narrative.

Input parameters:

- `jurisdiction` (string, required)
- `object_id` (string, required)

Output parameters:

- `case_study` (boolean)
- `conditions` (array)
- `eco_ref`
- `evidence_refs` (array)
- `issuer` (object)
- `jurisdiction`
- `key_id` (string)
- `object_id` (string)
- `rco_version`
- `record_id` (string)
- `resolved_at` (string)
- `rule_set` (object)
- `signal`
- `signature` (string): Detached JWS Compact Serialization (RFC 7515) with unencoded payload (RFC 7797): BASE64URL(protected header {alg:ES256, b64:false, crit:[b64], kid}) '..' BASE64URL(ES256 raw R||S). Signing input = AS…
- `state`
- `supersedes`
- `valid_until` (string)
- `verification_url` (string)

### `get_record` (~38 tokens)

Get record by id

Return any RCO by record_id, including superseded records - the audit trail, retained byte-identical.

Input parameters:

- `record_id` (string, required)

Output parameters:

- `case_study` (boolean)
- `conditions` (array)
- `eco_ref`
- `evidence_refs` (array)
- `issuer` (object)
- `jurisdiction`
- `key_id` (string)
- `object_id` (string)
- `rco_version`
- `record_id` (string)
- `resolved_at` (string)
- `rule_set` (object)
- `signal`
- `signature` (string): Detached JWS Compact Serialization (RFC 7515) with unencoded payload (RFC 7797): BASE64URL(protected header {alg:ES256, b64:false, crit:[b64], kid}) '..' BASE64URL(ES256 raw R||S). Signing input = AS…
- `state`
- `supersedes`
- `valid_until` (string)
- `verification_url` (string)

### `list_rule_sets` (~49 tokens)

List rule sets

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.

Input parameters:

- `jurisdiction` (string, required)

Output parameters:

- `jurisdiction`
- `rule_sets` (array)

### `list_issuers` (~33 tokens)

List issuers

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

Output parameters:

- `issuers` (array)
- `key_id` (string)
- `registry_version` (string)
- `signature` (string)
- `trust_anchor` (object)
- `updated` (string)
- `verification_url` (string)

### `publish_record` (~174 tokens)

Publish record (issuer)

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.

Input parameters:

- `record` (object, required)

Output parameters:

- `card_url` (string)
- `idempotent` (boolean)
- `ledger` (object)
- `note` (string)
- `published` (boolean)
- `record_id` (string)
- `record_url` (string)
- `slot` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/greencore-solutions-rco-a2a/mcp#diagnostics

## Score history

- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73
- 2026-09-06: 72
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 69
- 2026-08-31: 68
- 2026-08-30: 68

## Common questions

### What is the RCO-A2A - Regulatory Compliance Objects MCP server?

RCO-A2A - Regulatory Compliance Objects is an MCP server listed in the public MCP registry as io.github.greencore-solutions/rco-a2a. Signed, deterministic compliance state per object per jurisdiction, resolved upstream. This page covers its hosted endpoint (https://mcp.rco-a2a.ai/mcp).

### Is the RCO-A2A - Regulatory Compliance Objects MCP server safe to use?

RCO-A2A - Regulatory Compliance Objects scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the RCO-A2A - Regulatory Compliance Objects MCP server expose?

RCO-A2A - Regulatory Compliance Objects exposes 5 tools: resolve_compliance, get_record, list_rule_sets, list_issuers, publish_record. Their descriptions and schemas cost roughly 393 tokens of context every time the server is loaded.

### Does the RCO-A2A - Regulatory Compliance Objects MCP server require authentication?

No. We connected to RCO-A2A - Regulatory Compliance Objects without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RCO-A2A - Regulatory Compliance Objects MCP server still maintained?

RCO-A2A - Regulatory Compliance Objects is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.rco-a2a.ai/mcp
- Repository: https://github.com/greencore-solutions/rco-a2a
- Website: https://rco-a2a.ai/
- Changelog RSS feed: https://verifymcp.io/servers/greencore-solutions-rco-a2a/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/greencore-solutions-rco-a2a/mcp.json
- HTML version of this page: https://verifymcp.io/servers/greencore-solutions-rco-a2a/mcp