RCO-A2A - Regulatory Compliance Objects MCP Server

by greencore-solutions Your server? Claim it

answering

RCO-A2A - Regulatory Compliance Objects is answering right now. Last checked 9 min ago. It exposes 5 tools. Last commit 17 Sep 2026.

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

Uptime history 20 days of history

20 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

281 ms

Response time

average over 24h

Stars

last commit 17 Sep 2026

What changed 11

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 August 2026. No other catalogue keeps this.

17 Sep 5 tools changed the parameters they ask for6 times that day get_record, list_issuers, list_rule_sets and 2 more

17 Sep a tool changed version2 times that day

30 Aug 2 tools changed the parameters they ask for list_rule_sets, resolve_compliance

30 Aug a tool appeared publish_record

and 2 more, back to 30 August 2026

Nothing serious here today

Today is the operative word: we check RCO-A2A - Regulatory Compliance Objects every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add rco-a2a --transport http https://mcp.rco-a2a.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "rco-a2a": {
      "url": "https://mcp.rco-a2a.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.rco-a2a]
url = "https://mcp.rco-a2a.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "rco-a2a": {
      "url": "https://mcp.rco-a2a.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "rco-a2a": {
      "url": "https://mcp.rco-a2a.ai/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

issuers

list_issuers

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

publish

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, 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.

record

get_record

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

resolve

resolve_compliance

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.

rule

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.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.rco-a2a.ai/mcp	streamable-http	answering	289 ms	9 min ago

Alternatives to RCO-A2A - Regulatory Compliance Objects

same job, measured the same way

openfang-rail

by 89rat

Deterministic banking, LEI, VAT, SWIFT & compliance checks via MCP with signed XDR-1 receipts.

35 tools answering

AI Compliance Monitor

by vdineshk

Regulatory intelligence for AI agents across jurisdictions

4 tools answering

VITNA — Agent Compliance Preflight

by costrinity

Pre-action allow/deny for AI agents. 24 statutes, 13 jurisdictions: EU AI Act, GDPR, DPDP.

104 installs/wk 23 tools answering

Compliance Shield

by mdfifty50-boop

ZATCA, UAE CT, EU AI Act regulatory compliance for AI agents

41 installs/wk local only

MCP Agentcore

by geiant

AI governance MCP server for EU AI Act compliance and jurisdiction verification

3 tools answering

Compliance Registry

by complianceregistry

First A2A registry where AI agents discover & transact with compliance firms - audits, permits.

6 tools answering

Vizier Guard

by vassiliylakhonin

Deterministic authorization and security guard for AI agent actions with signed receipts.

local only

VoiceLogPro

by kindrat86

Construction daily-log generation, jurisdiction compliance requirements, construction FAQs.

3 tools answering

RCO-A2A - Regulatory Compliance Objects — questions

Answers built from our own checks of this server.

What can RCO-A2A - Regulatory Compliance Objects do?

It exposes 5 tools, read directly from the server on our last check. Among them: get_record, list_issuers, list_rule_sets, publish_record, resolve_compliance. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is RCO-A2A - Regulatory Compliance Objects working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 281 ms. The bar chart above shows every period we have measured.

How do I connect RCO-A2A - Regulatory Compliance Objects?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does RCO-A2A - Regulatory Compliance Objects need an API key?

No. RCO-A2A - Regulatory Compliance Objects completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is RCO-A2A - Regulatory Compliance Objects?

It answers our handshake in 281 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is RCO-A2A - Regulatory Compliance Objects open source?

Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.