ReceiptRail

io.github.xka0085-bytePublished by GitHub account xka0085-bytev0.3.0Updated Oct 24, 2026

Read-only on-chain receipt check for x402 payments; confirm settlement before trusting a tx.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that issues and verifies on-chain Solana receipts for x402 payments, anchoring content digests and settlement references.

What you can do
  • Issue a receipt anchoring a SHA-256 digest of delivered content plus an x402 settlement reference on Solana, paying 0.001 USDC via x402
  • Verify a receipt against live Solana state, checking PDA ownership and digest match
  • Fetch full receipt details such as digests, checks, outcome, amount, buyer, seller, timestamp and PDA
  • Look receipts up by receipt_id or by x402_payment_ref
When to use it
Useful when an assistant handles x402 payments and needs to confirm that a transaction actually settled before trusting delivered content, or when you want a publicly verifiable record tying content to a payment.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. Issuing a receipt requires an x402 payment of 0.001 USDC on Solana, so a funded wallet capable of producing an x402 payment signature is needed. Verification and lookup are read-only and free.
Before you install
Issuing a receipt spends 0.001 USDC per call and involves a Solana payment signature; without one the server returns a payment challenge. Receipts are written permanently and publicly on-chain, so the anchored digest and settlement reference become visible to anyone. Verification and lookup are read-only.

Installation

In SourceWeft

  1. Open ReceiptRail in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.xka0085-byte%2Freceiptrail/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "receiptrail": {
      "type": "http",
      "url": "https://agenttoll-receipts.app.workbuddy.host/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

issue_receipt

Issue delivery receipt

Anchor a SHA-256 digest of delivered content plus the x402 settlement reference on Solana. Returns a permanent, publicly verifiable receipt (poll until outcome === "settled"). Costs 0.001 USDC via x402; if x402_payment_signature is omitted, returns the payment challenge instead (pay 0.001 USDC to the service address, then call again with the payment tx signature).

Parametersbuyersellerx402_payment_refrequireddeliverable_digestrequiredx402_payment_signature

verify_receipt

Verify delivery receipt

Verify an AgentToll receipt against live Solana state: PDA owner must be the AgentToll program and the stored digest must match the receipt. Look up by receipt_id, or by x402_payment_ref (always works — the receipt lives on-chain). Read-only, no cost.

Parametersreceipt_idpayment_ref

get_receipt

Get receipt details

Fetch full receipt details: digests, checks, outcome, amount, buyer, seller, timestamp, PDA. Look up by receipt_id, or by x402_payment_ref (always works — the receipt lives on-chain). Read-only, no cost.

Parametersreceipt_idpayment_ref

Version history

3
  1. v0.3.0LatestSep 29, 2026
  2. v0.2.1Sep 18, 2026
  3. v0.2.0Sep 17, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.