Skip to main content
Glama

RCO Records - Record of Cleared Orders

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
allooloo/rco-records
GitHub Stars
0
Server Listing
RCO Records
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct role: aggregated signed statements, individual receipt listing, public receipt verification, receipt writing, and auditor key issuance. The boundaries between get_statement and list_receipts are made explicit by the descriptions (signed aggregate vs. raw receipt rows), so an agent can confidently select the right tool.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: get_statement, issue_auditor_key, list_receipts, verify_receipt, write_receipt. There are no naming style deviations or ambiguous shorthand.

Tool Count5/5

Five tools are well-scoped for a record-of-cleared-orders service: read side (statements, receipts), write side (receipts), verification, and delegated auditor access. Each tool earns its place without bloat.

Completeness4/5

The surface covers the core lifecycle: writing receipts, listing one's own receipts, obtaining signed statements, public verification, and issuing auditor sub-keys. Minor gaps exist around key revocation/rotation and perhaps richer administrative operations, but core agent workflows are well covered.

Available Tools

5 tools
get_statementAInspect

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 .

Inputs: to, from, month.

issue_auditor_keyAInspect

Issue a read-only sub-key on your own slice for your auditor (list_receipts and get_statement only). Authorization: Bearer . The key value is returned once.

Inputs: name.

list_receiptsA
Read-onlyIdempotent
Inspect

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 . Refuses without a key.

Inputs: to, from, limit, to_seq, +2 more.

verify_receiptA
Read-onlyIdempotent
Inspect

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.

Inputs: id (required).

write_receiptA
Idempotent
Inspect

Write one v1 receipt for a read a gate has cleared. Authenticated: Authorization: Bearer . Idempotent on (writer, subject, subject_type, market, rule_version, cleared_at, answer_hash). Returns the receipt.

Inputs: subject (required), rule_version (required), subject_type (required), caller, +4 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables verifying signed provenance receipts by ID or full receipt object and listing an agent's receipt hash-chain newest first for auditing.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Cryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.
      -
    • A
      license
      A
      quality
      D
      maintenance
      Every agent action is recorded in a SHA-256 hash chain. Prove to clients that your agent did what it said it did. Record, query, verify, and export agent activity.
      3
      37 npm
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      The accountability layer for AI agents — a named human's signed yes before an agent does anything irreversible (payment, record change, deploy), then an offline-verifiable Trust Receipt. Apache-2.0, formally verified.
      3
      550
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.