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 12 min ago. It exposes 5 tools. Last commit 29 Oct 2026.

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

Uptime history 71 days of history · worst day 28%

71 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

128 ms

Response time

average over 24h

Stars

last commit 29 Oct 2026

What changed 64

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

5 Nov a tool changed version2 times that day

5 Nov a tool changed the parameters it asks for write_receipt

4 Nov a tool changed version2 times that day

3 Nov a tool changed version

2 Nov a tool changed version4 times that day

31 Oct a tool changed version3 times that day

30 Oct 3 tools appeared get_statement, issue_auditor_key, list_receipts

30 Oct 2 tools changed the parameters they ask for3 times that day verify_receipt, write_receipt

30 Oct a tool changed version3 times that day

30 Oct 2 tool descriptions were rewritten verify_receipt, write_receipt

and 50 more, back to 30 August 2026

What the code does

We read the source, 2 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable rails/load_history.py:33

    with open(os.path.join(OUT, f'{i // N:03d}.sql'), 'w', encoding='utf-8') as f:

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "rco-a2a": {
      "type": "http",
      "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.

issue

issue_auditor_key

Issue a read-only sub-key on your own slice for your auditor (list_receipts and get_statement only). Authorization: Bearer <customer key>. The key value is returned once.

receipt

write_receipt

Write one v1 receipt for a read a gate has cleared. Authenticated: Authorization: Bearer <writer token>. Idempotent on (writer, subject, subject_type, market, rule_version, cleared_at, answer_hash). Returns the receipt.

receipts

list_receipts

Your own receipts only — the rows whose caller is your customer key — by seq range (from_seq, to_seq, after_seq) or date range (from, to: YYYY-MM-DD, to inclusive), limit ≤ 500. Authorization: Bearer <customer key>. Refuses without a key.

statement

get_statement

A signed statement of your slice for a month (month: YYYY-MM) or a date range (from, to: YYYY-MM-DD, to exclusive): count, first and last seq, slice digest, the chain tip at issue, Ed25519 signature by Allooloo. Authorization: Bearer <customer key>.

verify

verify_receipt

Return one receipt by id (rco:… for v1, dec_… for v0) with the verification result (hash, id, signature) and the public key (JWK) that checks it. Public.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_record

removed 16 Oct 2026

list_issuers

removed 16 Oct 2026

list_rule_sets

removed 16 Oct 2026

publish_record

removed 16 Oct 2026

resolve_compliance

removed 16 Oct 2026

get_receipt

removed 29 Oct 2026

Endpoints

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

Alternatives to RCO-A2A - Regulatory Compliance Objects

same job, measured the same way

Delta Registry — Regulatory & Compliance Monitoring (28 tools)

by stefanoseggio

28 pay-per-event tools for regulatory, sanctions, procurement, and corporate-registry monitoring.

answering

openfang-rail

by 89rat

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

57 tools answering

AI Compliance Monitor

by vdineshk

Regulatory intelligence for AI agents across jurisdictions

4 tools answering

Compliance Shield

by mdfifty50-boop

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

56 installs/wk local only

ClevSec EU compliance tools

by clevsec

Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR and the Cyber Resilience Act.

31 tools answering

MCP Agentcore

by geiant

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

3 tools answering

EuroComply — EU Regulatory Compliance

by eurocomply

EU regulatory compliance data: 17 regulations, deadlines, enforcement actions. EU-hosted.

12 tools answering

Atomadic MCP

by atomadic

Atomadic MCP: 68 deterministic tools for agent identity, escrow, SLA, EU AI Act compliance.

68 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_statement, issue_auditor_key, list_receipts, verify_receipt, write_receipt. 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 128 ms. The bar chart above shows every period we have measured.

Did RCO-A2A - Regulatory Compliance Objects ever remove tools?

Yes. get_record, list_issuers, list_rule_sets, publish_record and 2 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

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 in the form 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 128 ms on average, which is faster than 88% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is RCO-A2A - Regulatory Compliance Objects open source?

The code is open source: it is published under the MIT licence, written in CSS and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.rco-a2a.ai, which runs on its operator's own terms.