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.
Available components
Last scanned (21 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 47% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
- Server version: 2.6.0 → 2.6.1 functional
- 3 Nov 26 0
- Server version: 2.5.2 → 2.6.0 functional
- 2 Nov 26 0
- Server version: 2.4.1 → 2.5.2 functional
- 1 Nov 26 +1
- Server version: 2.3.1 → 2.4.1 functional
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 144 → 160 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 2.3.0 → 2.3.1 functional
- 30 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.rco-records.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rco-records.ai | CN=WE1,O=Google Trust Services,C=US | 29 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 6ee4cb20cb0e68780e78adc271c7135d |
| SANs: rco-records.ai, mcp.rco-records.ai, *.mcp.rco-records.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.rco-records.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| rco-records.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.rco-records.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.rco-records.ai/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_statement ~93
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>.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | – |
| month | string | – | – |
| to | string | – | – |
No output schema declared.
No examples provided.
issue_auditor_key ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
No output schema declared.
No examples provided.
list_receipts ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after_seq | integer | – | – |
| from | string | – | – |
| from_seq | integer | – | – |
| limit | integer | – | – |
| to | string | – | – |
| to_seq | integer | – | – |
No output schema declared.
No examples provided.
verify_receipt ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | rco:… or dec_… |
No output schema declared.
No examples provided.
write_receipt ~258
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | the rule set and version the gate cleared under |
| subject | string | yes | what was read: the identifier (an ISIN, LEI, GTIN, ticker, record id …) |
| subject_type | string | yes | isin | lei | gtin | ticker | cmr | … (open list) |
No output schema declared.
No examples provided.
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.
remote · mcp.rco-records.ai
claude mcp add --transport http allooloo-rco-records 'https://mcp.rco-records.ai/mcp'
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.