Remote MCP · Endpoint

RCO Records - Record of Cleared Orders MCP server

No. RCO Records - Record of Cleared Orders answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.allooloo/rco-records
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
39 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 10 checks
Described by its publisher as
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
Listing
From the official MCP registry (active).
Recent checks of RCO Records - Record of Cleared Orders
CheckedResultHandshake
2 days agoHandshake completed39 ms
6 days agoHandshake completed50 ms
16 days agoHandshake completed92 ms
17 days agoHandshake completed195 ms
18 days agoHandshake completed104 ms
19 days agoHandshake completed66 ms
21 days agoHandshake completed84 ms
21 days agoHandshake completed76 ms
22 days agoHandshake completed360 ms
23 days agoHandshake completed121 ms

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

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 Records - Record of Cleared Orders and makes no claim about it beyond what these checks measured.