RCO-A2A - Regulatory Compliance Objects
REMOTE · MCP.RCO-A2A.AI · SCANNED SEP 20
Signed, deterministic compliance state per object per jurisdiction, resolved upstream
Available components
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 481 tokens (~96/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.rco-a2a.ai
claude mcp add --transport http greencore-solutions-rco-a2a 'https://mcp.rco-a2a.ai/mcp'
{
"mcpServers": {
"greencore-solutions-rco-a2a": {
"url": "https://mcp.rco-a2a.ai/mcp"
}
}
} {
"servers": {
"greencore-solutions-rco-a2a": {
"type": "http",
"url": "https://mcp.rco-a2a.ai/mcp"
}
}
} [mcp_servers.greencore-solutions-rco-a2a] url = "https://mcp.rco-a2a.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"greencore-solutions-rco-a2a": {
"type": "remote",
"url": "https://mcp.rco-a2a.ai/mcp",
"enabled": true
}
}
} openclaw mcp add greencore-solutions-rco-a2a --url 'https://mcp.rco-a2a.ai/mcp' --transport streamable-http
mcp_servers:
greencore-solutions-rco-a2a:
url: "https://mcp.rco-a2a.ai/mcp" {
"McpServers": {
"greencore-solutions-rco-a2a": {
"Transport": "http",
"Url": "https://mcp.rco-a2a.ai/mcp"
}
}
} assistant mcp add greencore-solutions-rco-a2a -t streamable-http -u 'https://mcp.rco-a2a.ai/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +1
- Server version: 1.0.1 → 1.0.2 functional
- Server version: 1.0.0 → 1.0.1 functional
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 4 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.rco-a2a.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.rco-a2a.ai | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 29 Aug 2026 | 28 Feb 2027 | RSA 2048 | SHA256-RSA | 58378cc3767c9d6191c516334b680be |
| SANs: mcp.rco-a2a.ai | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.rco-a2a.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| rco-a2a.ai. | present | 2371 | 13 | Verified |
| mcp.rco-a2a.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rco-a2a.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rco-a2a.ai/mcp | HTTPS enforced | 301 | https://mcp.rco-a2a.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_record Get record by id ~38
Return any RCO by record_id, including superseded records - the audit trail, retained byte-identical.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| case_study | boolean | – | – |
| conditions | array | – | – |
| eco_ref | – | yes | – |
| evidence_refs | array | yes | – |
| issuer | object | yes | – |
| jurisdiction | – | yes | – |
| key_id | string | yes | – |
| object_id | string | yes | – |
| rco_version | – | yes | – |
| record_id | string | yes | – |
| resolved_at | string | yes | – |
| rule_set | object | yes | – |
| signal | – | yes | – |
| signature | string | yes | 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 | – | yes | – |
| supersedes | – | yes | – |
| valid_until | string | yes | – |
| verification_url | string | yes | – |
No examples provided.
list_issuers List issuers ~33
Return the signed consortium issuer registry document, verbatim as published at consortium-10060.org/issuers.json.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| issuers | array | yes | – |
| key_id | string | yes | – |
| registry_version | string | yes | – |
| signature | string | yes | – |
| trust_anchor | object | – | – |
| updated | string | yes | – |
| verification_url | string | yes | – |
No examples provided.
list_rule_sets List rule sets ~49
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | – | yes | – |
| rule_sets | array | yes | – |
No examples provided.
publish_record Publish record (issuer) ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| card_url | string | – | – |
| idempotent | boolean | – | – |
| ledger | object | yes | – |
| note | string | – | – |
| published | boolean | yes | – |
| record_id | string | yes | – |
| record_url | string | yes | – |
| slot | string | yes | – |
No examples provided.
resolve_compliance Resolve compliance state ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jurisdiction | string | yes | – |
| object_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| case_study | boolean | – | – |
| conditions | array | – | – |
| eco_ref | – | yes | – |
| evidence_refs | array | yes | – |
| issuer | object | yes | – |
| jurisdiction | – | yes | – |
| key_id | string | yes | – |
| object_id | string | yes | – |
| rco_version | – | yes | – |
| record_id | string | yes | – |
| resolved_at | string | yes | – |
| rule_set | object | yes | – |
| signal | – | yes | – |
| signature | string | yes | 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 | – | yes | – |
| supersedes | – | yes | – |
| valid_until | string | yes | – |
| verification_url | string | yes | – |
No examples provided.
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.