Skip to main content
Glama

Server Details

Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
Repository
nexus-mcp-infra/x402-receipt-verifier
GitHub Stars
0
Server Listing
x402-receipt-verifier
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 2 tools

Disambiguation5/5

The two tools target clearly distinct functions: one checks aggregate payer spend/delivery health, while the other audits a single payment and returns a signed receipt. Their descriptions are specific enough that an agent should not confuse them.

Naming Consistency4/5

Both tool names are snake_case and descriptive, though payer_spend_health is a noun phrase while verify_payment_receipt uses a verb-object form. The minor stylistic deviation does not hurt readability.

Tool Count4/5

Two tools is slightly below the typical 3-15 range, but it is appropriate for a narrow read-only receipt verification domain. Each tool covers a distinct core use case without seeming padded.

Completeness4/5

The server covers the main verification workflows: validating one payment and summarizing payer-level delivery health. Batch verification or broader receipt-log queries would be useful additions, but the core domain is not left with a dead end.

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
      A
      quality
      B
      maintenance
      Seals each payment an AI agent makes (x402, Stripe, cards, etc) as a signed record with the company's own key: the agent declares the purchase before paying, checks it against its limits, and records the settlement after. Anyone can verify the records without relying on Luca.
      10
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Signed delivery claims for x402 capacity trades (GPU-hours, storage, API credits, bandwidth). After a payment settles, the paying agent leaves a plain, cryptographically signed record of what was delivered, so a future buyer can check a sellers past history before paying again.
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      On-chain delivery receipts for x402 AI-agent payments on Solana: anchors SHA-256 digests of delivered content to a PDA after settlement; buyers verify proof of delivery offline with zero trust in the seller. Live MCP endpoint + npm bridge.
      3
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.