Security & Testing

rco-a2a.ai

Manages regulatory compliance objects and rule sets across jurisdictions, enabling record retrieval, audit trails, and secure publishing of signed compliance data.

1 endpoint5 known toolsFirst detected August 30, 2026Last detected August 30, 2026

ENDPOINT 1

https://mcp.rco-a2a.ai/mcp

No auth detected

MCP server metadata

Name: rco-a2a
Version: 1.0.0

Capabilities

tools

Server instructions

Read-only. resolve_compliance(object_id, jurisdiction) returns the current signed RCO or a pre-resolved signed CPG-404 inside the resolved universe; typed errors outside it. Records verify from https://dpuone.ai/.well-known/jwks.json (kid gsc-rco-2026-08), rooted in the signed issuer registry at https://consortium-10060.org/issuers.json.

Known tools 5

resolve_compliance

Return the current signed Regulatory Compliance Object for an object in a jurisdiction.

Inferred read-only

get_record

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

Inferred read-only

list_rule_sets

List the versioned rule sets in force and formerly in force for a jurisdiction: id, version, hash, effective dates, artifact URL.

Inferred read-only

list_issuers

Return the signed consortium issuer registry document, verbatim as published at consortium-10060.

Inferred read-only

publish_record

Publish a signed Regulatory Compliance Object to the partner rail (rco-a2a-cpg.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: rco-a2a
Remote MCP URL: https://mcp.rco-a2a.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "rco-a2a",
  "transport": "streamable-http",
  "url": "https://mcp.rco-a2a.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.