# RCO Records - Record of Cleared Orders (remote · mcp.rco-records.ai)

The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.rco-records.ai`: 65/100 (this document), [markdown](https://verifymcp.io/servers/allooloo-rco-records/mcp.md), [page](https://verifymcp.io/servers/allooloo-rco-records/mcp)

## Channel facts

- Endpoint: `https://mcp.rco-records.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.3.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 803 tokens (~160/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 47% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RCO Records - Record of Cleared Orders MCP server?

RCO Records - Record of Cleared Orders is a hosted endpoint at https://mcp.rco-records.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http allooloo-rco-records 'https://mcp.rco-records.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "allooloo-rco-records": {
      "url": "https://mcp.rco-records.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "allooloo-rco-records": {
      "type": "http",
      "url": "https://mcp.rco-records.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.allooloo-rco-records]
url = "https://mcp.rco-records.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allooloo-rco-records": {
      "type": "remote",
      "url": "https://mcp.rco-records.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add allooloo-rco-records --url 'https://mcp.rco-records.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  allooloo-rco-records:
    url: "https://mcp.rco-records.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "allooloo-rco-records": {
      "Transport": "http",
      "Url": "https://mcp.rco-records.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add allooloo-rco-records -t streamable-http -u 'https://mcp.rco-records.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "allooloo-rco-records": {
      "type": "http",
      "url": "https://mcp.rco-records.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 65, +1)

- [functional] Server version: 2.6.0 → 2.6.1

### 2026-11-03 (score 64, 0)

- [functional] Server version: 2.5.2 → 2.6.0

### 2026-11-02 (score 64, 0)

- [functional] Server version: 2.4.1 → 2.5.2

### 2026-11-01 (score 64, +1)

- [functional] Server version: 2.3.1 → 2.4.1

### 2026-10-31 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 144 → 160
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 2.3.0 → 2.3.1

### 2026-10-30 (score 63)

First indexed and scored.

## MCP tools (5)

### `write_receipt` (~258 tokens)

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.

Input parameters:

- `answer_hash` (string): sha256:<hex> of the canonical answer bytes the agent received
- `caller` (string): who asked, when the gate knows it: x402:<wallet address>; stored only as its sha256
- `caller_key` (string): the customer key the reader presented to the gate (RCO-Key); the door checks it and stores sha256("key:" + key id) as caller
- `cleared_at` (string): RFC 3339 UTC; stored to the second; the door's clock when absent
- `market` (string): ISO country or exchange code of the read
- `rule_version` (string, required): the rule set and version the gate cleared under
- `subject` (string, required): what was read: the identifier (an ISIN, LEI, GTIN, ticker, record id …)
- `subject_type` (string, required): isin | lei | gtin | ticker | cmr | … (open list)

### `verify_receipt` (~69 tokens)

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.

Input parameters:

- `id` (string, required): rco:… or dec_…

### `list_receipts` (~115 tokens)

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.

Input parameters:

- `after_seq` (integer)
- `from` (string)
- `from_seq` (integer)
- `limit` (integer)
- `to` (string)
- `to_seq` (integer)

### `get_statement` (~93 tokens)

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>.

Input parameters:

- `from` (string)
- `month` (string)
- `to` (string)

### `issue_auditor_key` (~55 tokens)

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.

Input parameters:

- `name` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/allooloo-rco-records/mcp#diagnostics

## Score history

- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 64
- 2026-10-31: 63
- 2026-10-30: 63

## Common questions

### What is the RCO Records - Record of Cleared Orders MCP server?

RCO Records - Record of Cleared Orders is an MCP server listed in the public MCP registry as io.github.allooloo/rco-records. The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id. This page covers its hosted endpoint (https://mcp.rco-records.ai/mcp).

### Is the RCO Records - Record of Cleared Orders MCP server safe to use?

RCO Records - Record of Cleared Orders scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the RCO Records - Record of Cleared Orders MCP server expose?

RCO Records - Record of Cleared Orders exposes 5 tools: write_receipt, verify_receipt, list_receipts, get_statement, issue_auditor_key. Their descriptions and schemas cost roughly 590 tokens of context every time the server is loaded.

### Does the RCO Records - Record of Cleared Orders MCP server require authentication?

No. We connected to RCO Records - Record of Cleared Orders without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RCO Records - Record of Cleared Orders MCP server still maintained?

RCO Records - Record of Cleared Orders is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.rco-records.ai/mcp
- Repository: https://github.com/allooloo/rco-records
- Website: https://rco-records.ai/
- Changelog RSS feed: https://verifymcp.io/servers/allooloo-rco-records/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/allooloo-rco-records/mcp.json
- HTML version of this page: https://verifymcp.io/servers/allooloo-rco-records/mcp