Remote MCP · Endpoint

RCO-A2A - Record of Cleared Orders MCP server

No. RCO-A2A - Record of Cleared Orders answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.Agentic-Private-Office/rco-a2a
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
5 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Signed receipt per cleared agentic order, by decision id. Two tools: write_receipt, verify_receipt.
Listing
From the official MCP registry (active).
Recent checks of RCO-A2A - Record of Cleared Orders
CheckedResultHandshake
37 minutes agoHandshake completed59 ms
4 days agoHandshake completed198 ms
7 days agoHandshake completed360 ms
16 days agoHandshake completed71 ms
16 days agoHandshake completed54 ms
18 days agoHandshake completed65 ms
19 days agoHandshake completed117 ms
20 days agoHandshake completed98 ms
21 days agoHandshake completed70 ms
22 days agoHandshake completed48 ms
23 days agoFailed - the request timed out—
26 days agoHandshake completed256 ms
29 days agoHandshake completed264 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with RCO-A2A - Record of Cleared Orders and makes no claim about it beyond what these checks measured.