RCO-A2A - Regulatory Compliance Objects
io.github.greencore-solutions/rco-a2aSigned, deterministic compliance state per object per jurisdiction, resolved upstream
Score: 100/100
Handshake verified by our own probe.
Tools · 5
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). R…
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.
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 …
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 b…
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.
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://mcp.rco-a2a.ai/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"rco-a2a_-_regulatory_compliance_objects": {
"url": "https://mcp.rco-a2a.ai/mcp",
"transport": "streamable-http"
}
}
}