agenttru.st

RCO Records — Record of Cleared Orders bronze

mcp.rco-records.ai

“RCO-10060 defines a signed receipt for a cleared read of a listed issuer's record. The receipt identifies the subject, the jurisdiction, the clearance rule, the stated time of the read and the hash of the signed answer supplied, and links that event into a verifiable receipt chain. The RCO door signs receipts under its own key; the producing node separately signs its content under the record key. A consumer verifies the receipt, matches the answer hash and verifies the record, and so holds attributable evidence of both the content and the read. RCO preserves the record of the read without holding the content or judging its truth. Receipt v1: {v, id, seq, writer, caller, subject, subject_type, market, rule_version, cleared_at, answer_hash, prev_hash, hash, sig, kid}. Tools: write_receipt (writer credential), verify_receipt (public), list_receipts, get_statement and issue_auditor_key (the firm's own key).

a2a https://mcp.rco-records.ai/mcp talk to it https://mcp.rco-records.ai/.well-known/agent-card.json its card
Checked 6d ago pushNotifications, stateTransitionHistory, streaming

we checked this    the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate
Issued by Google Trust Services domain-validated
Valid until 28 Jan 2027 as of our check on 8 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.
Control of the hostname was checked; nothing about who operates it.
Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.
Names on this certificate (3)

rco-records.ai, mcp.rco-records.ai, *.mcp.rco-records.ai.

Connection
TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 8 Nov 2026. What this means
DANE / TLSA
Not verified (TLSA query returned RCodeNameError)
Discovery
Well-known document
AI use policy
Search: yesAI input: yesAI training: yes
What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents
Publishes /llms.txt — “RCO Records — Record of Cleared Orders” a curated map of the site's content for language models
Fetched from this host during verification. Neither document is how this agent was discovered.
First seen
31 Oct 2026
View verification details
Assurance
bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols
A2A verified by handshake or card fetch, not merely advertised
Hosted in
? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked
6d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of mcp.rco-records.ai controls every word below.

write_receipt

Write one chained, signed v1 receipt for a cleared read (bearer token per writer); returns the receipt.

receiptwriteauthenticated

verify_receipt

Return one receipt by id (rco:… or a v0 dec_…) with the verification result and the key that checks it. Public.

receiptverifypublic

list_receipts

A customer key's own receipts, by seq or date range (RCO Register).

registercustomer-key

get_statement

A signed monthly or on-demand statement of a customer key's slice (RCO Register).

registerstatementcustomer-key

issue_auditor_key

A read-only auditor sub-key on a customer key's own slice.

registerauditor

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider
Allooloo Technologies Corp. — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol
a2a
Version
2.6.6
Auth schemes
customer none writer
Card completeness
complete all eight fields required by a2a.proto v1.0
View all card details
Capabilities
pushNotifications stateTransitionHistory streaming
Agent card
https://mcp.rco-records.ai/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.