Skip to main content
Glama
xka0085-byte

ReceiptRail — x402 Delivery Receipts on Solana

by xka0085-byte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ReceiptRail — x402 Delivery Receipts on Solana

  • x402-mcp by x402node

    x402-mcpofficial

    x402node
    A
    license
    C
    quality
    F
    maintenance
    MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
    100
    35 npm
    1
    MIT

Related Servers

  • solinkify-mcp

    Zenidp
    A
    license
    A
    quality
    A
    maintenance
    Agentic payments on Solana: an agent can pay x402 / HTTP 402 paywalls in USDC, hold a pre-paid balance or a subscription, and buy datasets or settle store checkouts. All 15 tools run behind fail-closed spending caps ($1 per payment, $10 per day by default), and settlement is non-custodial through a program-owned escrow that releases 99% to the creator.
    18
    81 npm
    MIT

  • zkVerify

    zkarchitect
    A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to fetch and independently verify on-chain data such as account balances and contract code hashes using Merkle proofs and ECDSA signatures, with x402 payment integration.
    3
    MIT

  • agenticpay

    agenticpay-dev
    A
    license
    B
    quality
    B
    maintenance
    agenticpay lets MCP server developers monetize tools via per-call USDC micropayments on Solana, using the x402 protocol. Each tool declares a price; agents pay via signed Solana transactions; settlement happens on-chain in ~1.5–2 seconds.
    1
    3
    MIT

  • LedgerProof LAIN

    vsdawkins-creator
    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.
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: issuing, verifying, and fetching receipts. There is no overlap between them, making selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (issue_receipt, verify_receipt, get_receipt), making the API predictable and easy to navigate.

Tool Count5/5

Three tools is ideal for a focused receipt service. Each tool covers a distinct need, and the count is proportionate to the domain without redundancy or excess.

Completeness4/5

The core lifecycle (create, verify, fetch) is fully covered. A minor gap is the lack of a listing/search tool, but lookups by ID or payment reference suffice for common use cases.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources