Listed from the MCP registry; nobody on Odel publishes it.

MCP server: One MCP server.

Receiptchain

@cloudcorprecordsMCP server · External

Agent receipts audit reads: verify signed provenance receipts and list an agent's receipt chain.

Fraud & scam detectionv0.1.0MITTypeScript
Freeno charge per call

Runs on your machine from its package; the steps are below.

What it does

  1. Reads
  2. Writes
  3. High impact

At most: only reads or looks up information.

What it costs

Free

Odel charges nothing per call. The publisher may charge for its own service.

Runs locally over stdio

This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).

npm@reneturcios/receiptchainv0.1.0

Run

npx -y @reneturcios/receiptchain

MCP client config

{
  "mcpServers": {
    "receiptchain": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/receiptchain"
      ]
    }
  }
}
Dockerghcr.io/cloudcorprecords/receiptchain:0.1.0

Run

docker run -i --rm ghcr.io/cloudcorprecords/receiptchain:0.1.0

MCP client config

{
  "mcpServers": {
    "receiptchain": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/cloudcorprecords/receiptchain:0.1.0"
      ]
    }
  }
}
README4 min read

Check an agent's receipts before you trust its story. receiptchain is a local forwarding client for the hosted agent-receipts MCP service: it answers tools/list locally from the captured tool definitions and forwards every call to the service, returning the answers exactly as the service sends them back.

Agents that act in the world leave a trail of signed provenance receipts, chained together per agent. This package covers the two free audit reads over that trail: verify a single receipt — by its id, or by handing over the full receipt object for an offline-style check of its content hash, id commitment and ed25519 signature — and pull the whole receipt hash-chain for an agent, newest first, to audit everything that agent has attested. Nothing is verified, stored or cached locally — the package is a pipe to the checker, not the checker itself.

Labelled subset

The captured upstream surface has 3 tools; this rebuild builds 2 of them.

  • verify_receipt — Verify a receipt by id, or by passing the full receipt object. The service recomputes the content hash, confirms the id commits to the body, and checks the ed25519 signature, then returns the verification checks plus the provenance record (action, agent, input/output hashes, timestamp, chain position). Neither id nor receipt is required by the captured schema.
  • list_receipts — List the receipt hash-chain for an agent, newest first, with id, action, timestamp, sequence, hashes and a verify URL for each entry. agent_id is required; limit caps the page (default 25, max 100).

Omitted: issue_receipt, the tool that mints a new signed receipt. Its captured description prices it at $0.01 USDC per call via x402, and this rebuild never originates per-call crypto payments, so the tool is not registered, not listed and not a CLI command. The two reads above stand on their own: a receipt issued anywhere can be verified here, and any existing agent chain can be audited, without the issuing tool.

Install and run

As an MCP server via npm:

bash
npx -y @reneturcios/receiptchain mcp

MCP client configuration:

json
{
  "mcpServers": {
    "receiptchain": {
      "command": "npx",
      "args": ["-y", "@reneturcios/receiptchain", "mcp"]
    }
  }
}

As a container:

bash
docker run -i ghcr.io/cloudcorprecords/receiptchain
docker run --rm ghcr.io/cloudcorprecords/receiptchain list_receipts '{"agent_id":"<agent>"}'

CLI

One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:

bash
receiptchain verify_receipt '{"id":"rcpt_..."}'
receiptchain list_receipts '{"agent_id":"<agent>","limit":10}'
receiptchain --version

Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.

Configuration

  • AGENTRECEIPTS_MCP_URL — Overrides the upstream endpoint. The default is the pinned hosted endpoint, https://agent-receipts.dropwatchhq.com/mcp. (The override variable is a reconstruction added by this rebuild.)

The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.

Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with receiptchain error:.

How forwarding works

The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.

Development

bash
npm install
npm run build   # tsc -> dist/ (dist/cli.js is the bin)
npm test        # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev     # run the CLI from source

The test suite checks the served tool list against the captured surface (both tools, deep-equal, in order, with no titles invented and no required key added to verify_receipt), asserts the omitted issue_receipt tool is absent at registry, MCP and CLI level, exercises the session handshake and its reuse, verifies that no Authorization header is ever sent, and verifies that arguments go upstream untouched and results come back untouched.

License

MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.

Similar modules

Browse Fraud & scam detection