Lumière PayCheck
io.github.Book0fEli/paycheckVersion 1.10.0Check x402 endpoints before your AI agent pays: grades, payment checks, refunds, receipts.
Status
Responds801 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:36 UTC
- Latency
- 801 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://lumierepaycheck.org/mcp?plans=1Responds801 msNo sign-in
Claude Code
claude mcp add --transport http paycheck 'https://lumierepaycheck.org/mcp?plans=1'Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: paycheck
Remote MCP server URL: https://lumierepaycheck.org/mcp?plans=1Cursor
{
"mcpServers": {
"paycheck": {
"url": "https://lumierepaycheck.org/mcp?plans=1"
}
}
}VS Code
code --add-mcp '{"name":"paycheck","type":"http","url":"https://lumierepaycheck.org/mcp?plans=1"}'Streamable HTTP
npm: lumiere-paycheck-mcp 1.3.0Package only
npm (npx)
claude mcp add paycheck -- npx -y lumiere-paycheck-mcp@1.3.0Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
10 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
catalog_statsGet 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. Endpoints from a seller listing thousands of near-identical endpoints are counted once as bulk_listing until each has its own grade. 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. | No | Yes | Yes | No |
check_endpointGet 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 and are checked automatically: if one answers a valid x402 payment quote it joins the catalog within about 10 minutes (see intake). A retest field appears while a failed paid test awaits its re-test (the grade changes only if that fails too). API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md | No | Yes | Yes | No |
check_paymentDecide 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. pauseDuringRetest: true also holds payments while a failed paid test awaits its re-test. API docs: https://github.com/Book0fEli/lumiere-paycheck/blob/main/docs/api.md | No | Yes | Yes | No |
get_full_reportGet 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 | No | Yes | Yes | No |
list_sellersList the sellers behind the monitored x402 endpoints, grouped by domain, with each seller's endpoint count, verdict mix (proceed, caution, avoid, free, insufficient_data, bulk_listing), passing and paid-tested counts, and best grade. Use it to find which providers have trustworthy endpoints, search a provider by domain, or see who has endpoints to avoid. Open one seller's endpoints with seller_endpoints; for a single endpoint use check_endpoint. Read-only and free; the same data as lumierepaycheck.org/sellers, refreshed every few minutes. | No | Yes | Yes | No |
paid_test_receiptsGet the signed receipts for our real test payments to one x402 endpoint: the exact payment terms we paid and the response we got (as SHA-256 hashes), amount quoted and paid, payout wallet, HTTP status, result and time, signed with our published Ed25519 key. Use it when a user or agent wants evidence behind a grade instead of the grade alone; check_endpoint gives the grade itself. The tester wallet and transaction appear only after that test wallet is retired (until then a hash commits to them). Read-only and free; receipts exist for tests since Nov 7, 2026. | No | Yes | Yes | No |
reliability_reportGet the live x402 reliability numbers from our own paid tests over the last 30 days: how many endpoints delivered once paid, how often payments didn't go through, how many bad calls still charged the buyer and how many were refunded, why paid calls fail, what calls cost, and the sellers that refund failed calls. Includes the same numbers from about 30 days earlier when available. Use it to answer questions about x402 reliability as a whole or which sellers refund; for one endpoint use check_endpoint, for one seller seller_endpoints. Read-only and free; recomputed every 6 hours. The same data is at lumierepaycheck.org/reliability. | No | Yes | Yes | No |
report_outcomeAfter 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. | No | No | Yes | Yes |
seller_endpointsList one seller's monitored x402 endpoints with each one's grade, score, verdict, 7-day uptime, median response time, whether a real test payment was delivered, and how many checks it's based on, plus the seller's counts per verdict and its refund record (how many of our failed paid calls it refunded in the last 30 days). Use it after list_sellers to pick the best endpoint from a provider, or to see which of a seller's endpoints to avoid. For the full reasons behind one endpoint's grade use check_endpoint. Read-only and free; 50 endpoints per page at most. | No | Yes | Yes | No |
top_endpointsList 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). | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 11, 2026
- Updated
- Nov 11, 2026
- Categories (suggested)
- Finance and paymentsE-commerceSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared