Lumière PayCheck

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Check any x402 endpoint before your AI agent pays it: trust grade, verdict, and hijack checks.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Lumière PayCheck": {
      "url": "https://lumierepaycheck.org/mcp?plans=1",
      "transport": "streamable-http"
    }
  }
}

Measured tools (6)

• check_endpoint read-only

  Get the trust verdict for one x402 endpoint: score (0-100), grade (A-F), and verdict (proceed, caution, avoid, free, or insufficient_data), plus uptime, delivery-test status, payout-wallet incidents, and how many independent buyers stand behind the seller's buyer wallets (we count customers, not wallets). Use it when you're deciding whether an endpoint is trustworthy at all, before you have a price quote. When you already have the 402 quote (amount and payTo) and are about to pay, use check_payment instead: it runs this same check and also verifies the price and wallet. To discover good endpoints rather than check a known one, use top_endpoints. Read-only and free; reflects monitoring every 30 minutes and real test payments, so a brand-new endpoint may return insufficient_data. Endpoints not in the catalog return monitored: false. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md

  Parameters:

  • url (required) — string — Full URL of the x402 endpoint including path, exactly as the agent will call it, e.g. https://api.example.com/v1/price.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_payment read-only

  Decide whether a specific x402 payment should go through: returns allow true/false with reasons. Checks the endpoint's trust verdict, that the amount is within your cap and not above the monitored price, and that the payTo wallet matches the one we've observed (catches swapped or hijacked wallets). Optionally (minOrganicShare) it also requires that enough of the seller's volume comes from independent buyers. Intended for right before a payment, with the amount, payTo, and network from the endpoint's 402 quote; allow is true only when every rule passes. Use check_endpoint instead if you only want an endpoint's grade without a quote in hand. Read-only and free; it doesn't make or block the payment itself. When allow is false, the reasons list explains why. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md

  Parameters:

  • url (required) — string — Full URL of the x402 endpoint you are about to pay, including path
  • payTo — string — Wallet address from the endpoint's 402 quote
  • amount — string — Amount about to be paid, atomic units (USDC has 6 decimals: 10000 = $0.01)
  • network — string — Network from the quote, e.g. eip155:8453
  • hasAccess — boolean — true if you have your own account, API key or sign-in with this seller. For endpoints that need the seller's sign-in on top of x402, allowCaution/requireVerified then don't block (we couldn't confirm delivery only because we can't sign in).
  • maxAmount — string — Your hard cap for this payment in atomic units (USDC: 1000000 = $1). Payments above it are denied.
  • allowCaution — boolean — false = deny endpoints with a caution verdict too, not just avoid (default true)
  • priceTolerance — number — Optional, 0-0.5 (default 0.02 = 2%): how far above the endpoint's recent prices still counts as the same price, for sellers whose price drifts (pegged to BTC, gas or FX). Bigger jumps are denied as overcharges.
  • minOrganicShare — number — Optional, 0-1: deny sellers where less than this share of 30-day volume comes from independent buyers (e.g. 0.5). Not applied to sellers whose buyers haven't been reviewed yet.
  • requireVerified — boolean — true = only allow endpoints that delivered on a real test payment (default false)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• report_outcome

  After paying an x402 endpoint, report whether you got what you paid for. Free, optional, and open to every agent: send the receipt from a Lumière PayCheck allow decision (paid plans), or the endpoint url plus the payment's transaction hash (anyone; we verify the payment on-chain, Base or Solana, within 24 hours). Answer the short questions in answers: gotResponse, matchedListing (yes/partly/no), charged (as_quoted/more/twice), dataUsable (yes/unsure/no), wouldPayAgain. Reports never change a grade by themselves: confirmations from independent buyers move the endpoint up our paid-test queue, and serious problems (nothing came back, charged more or twice) trigger a re-test; only our own paid test changes the grade. One report per payment; the seller's own wallet can't report on itself.

  Parameters:

  • tx — string — The payment's transaction hash (Base 0x...) or Solana signature
  • url — string — The endpoint you paid (with tx, when you have no receipt)
  • answers — object
  • outcome — string — Optional shortcut instead of answers: delivered = usable; problem = error, empty, wrong or overcharged
  • receipt — string — The receipt from a Lumière PayCheck 'allow' decision (paid plans). Or send url + tx instead.
  • problems — array — Short descriptions, e.g. 'missing field price', 'HTTP 500'
  • httpStatus — integer — HTTP status the endpoint returned after payment, e.g. 200 or 500

  Hints: read-only no · destructive no · idempotent yes · open-world yes

• top_endpoints read-only

  List the x402 endpoints that are currently safest to pay (verdict proceed or caution, no payout-wallet incidents), best first, with score, grade, verdict, and whether a real test payment was delivered. Use it to discover reliable endpoints or pick between providers. To evaluate one specific endpoint use check_endpoint; to approve a payment use check_payment. Read-only and free; rankings update as monitoring runs (every 30 minutes).

  Parameters:

  • limit — integer — How many endpoints to return, 1-50 (default 10)

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• catalog_stats read-only

  Get an overview of the whole monitored x402 catalog: how many endpoints are monitored, how many fall into each verdict (proceed, caution, avoid, free, insufficient_data), and when scores were last computed. Use it for context or reporting, for example to tell a user how much of the x402 ecosystem passes checks. It says nothing about any single endpoint: use check_endpoint for one endpoint, top_endpoints for a ranked list, or check_payment before paying. Read-only, free, no parameters.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• get_full_report read-only

  Get instructions for buying the detailed paid report on one x402 endpoint (score breakdown, current price quote, wallet and price history, test-payment results). Returns the report URL, price, and network; it doesn't buy the report itself. The report is an x402 endpoint that your agent pays with any x402 client. Use it only when the free check_endpoint result isn't enough and the user wants the full history. The response also lists the other paid x402 checks (wallet risk, batch grades, watch alerts), paid the same way. Endpoints we don't monitor return 404 on the report URL and are never charged. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md

  Parameters:

  • url (required) — string — Full URL of the x402 endpoint you want the paid report for, including path

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.